DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=QlW8bCXdu/8Vh0ZVqijHF/AQEu1n/EXVpt8nAHVXJkErZSuFPe/6q
	p6ZD60U41vC8j0Dlv7VNXNB6WnfXGaGsGQla9WHN63y4Tsg4oBavl/I/ZE1/Mr1o
	ZhNzIviRajcFipQm+IeUnNLunGMVToiLI5nPYZJ/6Tou55UvDzL2tU=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 25 Apr 2014 21:16:04 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: rm -f behavior
Message-ID: <20140425191604.GA18226@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <5358260B.90807@obj-sys.com> <20140424142304.GT2339@calimero.vinschen.de> <53592F15.4040309@obj-sys.com> <20140424163624.GU2339@calimero.vinschen.de> <20140425121614.GB5666@calimero.vinschen.de> <535A6FF9.90004@obj-sys.com> <20140425145036.GE5666@calimero.vinschen.de> <535A7F9B.5020804@obj-sys.com> <20140425154702.GH5666@calimero.vinschen.de> <535AA56F.40501@obj-sys.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="pWyiEgJYm5f9v55/"
Content-Disposition: inline
In-Reply-To: <535AA56F.40501@obj-sys.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

--pWyiEgJYm5f9v55/
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Apr 25 14:11, Douglas Coup wrote:
> On 4/25/2014 11:47 AM, Corinna Vinschen wrote:
> >On Apr 25 11:30, Douglas Coup wrote:
> >>I downloaded the x86/cygwin-inst-20140425.tar.xz file.  I assume all
> >>I need to do is run tar xvf against this file?  From the output it
> >>certainly looked like it installed the files.
> >No.  Just download the DLL and only install the DLL in place of the old
> >DLL.  Installing the tar inst file under Cygwin doesn't effectively
> >replace the Cygwin DLL.  You should exit all(!) Cygwin processes, mopve
> >the release DLL out of the way, and move the new DLL in place.
> Good shooting, Corinna.  The problem has gone away with the new DLL.

Good to know.  Can you please try something else?  I'm wondering if
that's not a problem analogue of the one described in
http://support.microsoft.com/kb/948252.

The "fix" from that KB applied to your case:

- Revert to the release Cygwin DLL.

- Delete the .blf files and the .regtrans-ms files from your
  %Windir%\System32\SMI\Store\Machine folder.=20

- Try the failing rm -f scenario again.

Does that fix the problem, too?  If not, I'm back to blaming Perforce.


Thanks,
Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--pWyiEgJYm5f9v55/
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTWrR0AAoJEPU2Bp2uRE+grtwP/3jOa57pAU7ncuJaPc+SnHDW
2QAt11itn9Ly7FdOEHsCxNCy47FKwyAepsk4S5FBQ9W3UTB0PA028FH/TnoS4lx+
m/OlAh5J1zWIWQHP/JLRJoTfil7Uq8PLHyLyIT/bHZD6AMqSFYf/nfkmojTDHDTl
IYZbqtMevH2yNvB9xtJ1E4C75ZNE/SYYzMiVnrS+Zt9W+Hwz/hYffJT4NlEUEbyp
0yPy8SQIt5KhjqftQ1Ejzbp52JLQWIX25dnYOfRJYBFVKuafkB6MyNnr71EuKXOZ
CGbP7lQJH2wfRyoUpQjQ6yI3DZ4dsgOVpR88InpR7npi+KvZcMhzchA/DIB9Q6e9
bhGUYVAvTw48CAk+FhwJw2Gl3UBCzaJ1clq5Xf6DiKpgOjnbbA2SGc+oQ0h4Tup9
jVQZ8URAJnGUuIx1lpmgGVQhLtJ4iglZc2xK//WsYg0yfEJzErKPX6MP3v6bVl39
TMd8Ptd79tWM2abHCWp7cw01PmzR8EE3KlkSC6bZ5C3UbCiC7TbmjJgYgLZUb5HS
l1daG3L8I44yq6DDkZfCls8XgCulc2XDyDJzT20TAZoAIVDe39yxXmY3RzqFB29p
GuGToaaaJIBNOQDjJcJ97wr1R+r+AK1OfNiOO75y3pMTKN2c8UmPYMDkNpKzylxG
1JcvHBrUoIoiyNGGGB+w
=5fMZ
-----END PGP SIGNATURE-----

--pWyiEgJYm5f9v55/--