public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: cygport dropping  *.exe links
Date: Wed, 24 Sep 2014 03:35:00 -0000	[thread overview]
Message-ID: <54223951.3040801@redhat.com> (raw)
In-Reply-To: <20140815151619.GK28562@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]

On 08/15/2014 09:16 AM, Corinna Vinschen wrote:

Sorry for taking more than a month to get to the bottom of this one.
But I have good news:

>> $ touch a.exe
>> $ ln -s a.exe b.exe
>>  $ ls -l
>> total 1
>> -rw-r--r-- 1 marco Administrators 0 Aug 15 16:41 a.exe
>> lrwxrwxrwx 1 marco Administrators 5 Aug 15 16:41 b.exe -> a.exe
>>
>> $ mv b.exe b
>> $ ls -l
>> total 0
>> -rw-r--r-- 1 marco Administrators 0 Aug 15 16:41 a.exe
> 
> Looks like a bug in coreutils 8.23.  This works fine in coreutils-8.15.

Actually, this was an intentional upstream change made by coreutils
8.16, but which has a negative effect on cygwin .exe magic.  The real
reason for the change is this upstream testcase:

$ ln -s nowhere a
$ ln a b
$ mv a b
$ ls [ab]
b

In coreutils 8.15, this mistakenly errored out instead of deleting 'a'.
 But the upstream fix for this needs additional cygwin magic to realize
that when 'b' and 'b.exe' are both symlinks and have the same inode,
then it is the same as a case change, and NOT a case of hard link
renames.  I'm cooking up the patch now.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]

  parent reply	other threads:[~2014-09-24  3:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15 11:26 Marco Atzeri
2014-08-15 14:47 ` Marco Atzeri
2014-08-15 15:16   ` Corinna Vinschen
2014-08-15 17:02     ` Eric Blake
2014-09-01  8:52       ` Marco Atzeri
2014-09-24  3:35     ` Eric Blake [this message]
2014-10-08 12:55       ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54223951.3040801@redhat.com \
    --to=eblake@redhat.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).