Opened 9 years ago
Last modified 9 years ago
#47556 new defect
coreutils @8.23_1 Calling gcp -al fails on symbolic links
| Reported by: | thomas.baigneres@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.3 |
| Keywords: | Cc: | kurthindenburg (Kurt Hindenburg) | |
| Port: | coreutils |
Description
OS X 10.10.3
Xcode Version 6.3.1 (6D1002)
Consider the following directory hierarchy:
$ ls -lR total 0 drwxr-xr-x 4 tbaigner group 136 Apr 24 13:51 source ./source: total 16 -rw-r--r-- 1 tbaigner group 0 Apr 24 13:50 file.txt lrwxr-xr-x 1 tbaigner group 8 Apr 24 13:51 symbolic-link-to-file -> file.txt
Trying to copy the source directory with the options -a (archive) and -l (hard link files instead of copying) fails when using the @8.23_1 version of coreutils:
$ gcp -al source destination gcp: cannot create hard link 'destination/symbolic-link-to-file' to 'source/symbolic-link-to-file': Operation not supported
Trying to do the same with the @8.22_0 version of coreutils works as expected :
$ sudo port activate coreutils @8.22_0 $ gcp -al source destination $ ls -lR total 0 drwxr-xr-x 4 user group 136 Apr 24 13:51 destination drwxr-xr-x 4 user group 136 Apr 24 13:51 source ./destination: total 16 -rw-r--r-- 2 user group 0 Apr 24 13:50 file.txt lrwxr-xr-x 1 user group 8 Apr 24 13:51 symbolic-link-to-file -> file.txt ./source: total 16 -rw-r--r-- 2 user group 0 Apr 24 13:50 file.txt lrwxr-xr-x 1 user group 8 Apr 24 13:51 symbolic-link-to-file -> file.txt
Searching the internet suggests that the culprit might be the linkat() function, which exists but does not work as expected by coreutils.
Change History (5)
comment:1 follow-up: 2 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 9 years ago by thomas.baigneres@…
Replying to ryandesign@…:
This doesn't sound like a MacPorts-specific problem. You should report it to the developers of coreutils so that they can fix it and release a new version. When they do, we'll update the port in MacPorts.
Ok, sorry for posting at the wrong place. I just reported this issue to developers of coreutils.
This doesn't sound like a MacPorts-specific problem. You should report it to the developers of coreutils so that they can fix it and release a new version. When they do, we'll update the port in MacPorts.