GNU bug report logs -
#73875
cp: there isn't even an option to quit on errors
Previous Next
To reply to this bug, email your comments to 73875 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-coreutils <at> gnu.org
:
bug#73875
; Package
coreutils
.
(Sat, 19 Oct 2024 07:47:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Dan Jacobson <jidanni <at> jidanni.org>
:
New bug report received and forwarded. Copy sent to
bug-coreutils <at> gnu.org
.
(Sat, 19 Oct 2024 07:47:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
$ cp -a /usr/share/doc/qpdf/manual-html/ ~/Downloads/
cp: cannot create symbolic link '/home/jidanni/Downloads/manual-html/_static/css/badge_only.css': Permission denied
cp: cannot create symbolic link '/home/jidanni/Downloads/manual-html/_static/css/theme.css': Permission denied....
It just keeps rolling on. No way to quit except ^C.
$ cp --version
cp (GNU coreutils) 9.4
Information forwarded
to
bug-coreutils <at> gnu.org
:
bug#73875
; Package
coreutils
.
(Sun, 20 Oct 2024 13:07:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 73875 <at> debbugs.gnu.org (full text, mbox):
On 19/10/2024 08:45, Dan Jacobson wrote:
> $ cp -a /usr/share/doc/qpdf/manual-html/ ~/Downloads/
> cp: cannot create symbolic link '/home/jidanni/Downloads/manual-html/_static/css/badge_only.css': Permission denied
> cp: cannot create symbolic link '/home/jidanni/Downloads/manual-html/_static/css/theme.css': Permission denied....
>
> It just keeps rolling on. No way to quit except ^C.
>
> $ cp --version
> cp (GNU coreutils) 9.4
Well POSIX states that cp should continue upon failure to create a symlink.
An exit early option may be useful.
I don't see such an option with rsync either though, so I'm not sure how generally useful it is.
cheers,
Pádraig
Information forwarded
to
bug-coreutils <at> gnu.org
:
bug#73875
; Package
coreutils
.
(Sun, 20 Oct 2024 14:23:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 73875 <at> debbugs.gnu.org (full text, mbox):
Well OK, it is creating an unusable copy, and probably doesn't
even return an error to the calling shell.
So Makefiles using it will go on to the next step... with the final
result being missing files, discovered just minutes away from the boss's
big ceremony...
>>>>> "PB" == Pádraig Brady <P <at> draigBrady.com> writes:
PB> Well POSIX states that cp should continue upon failure to create a symlink.
PB> An exit early option may be useful.
PB> I don't see such an option with rsync either though, so I'm not sure how generally useful it is.
OK, I'll tell them to add it to rsync too.
Information forwarded
to
bug-coreutils <at> gnu.org
:
bug#73875
; Package
coreutils
.
(Sun, 20 Oct 2024 17:49:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 73875 <at> debbugs.gnu.org (full text, mbox):
On 20/10/2024 15:21, Dan Jacobson wrote:
> Well OK, it is creating an unusable copy, and probably doesn't
> even return an error to the calling shell.
>
> So Makefiles using it will go on to the next step... with the final
> result being missing files, discovered just minutes away from the boss's
> big ceremony...
Any error is propagated to the exit status,
so one can always determine if any part of the copy fails.
cheers,
Pádraig.
Information forwarded
to
bug-coreutils <at> gnu.org
:
bug#73875
; Package
coreutils
.
(Fri, 25 Oct 2024 22:33:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 73875 <at> debbugs.gnu.org (full text, mbox):
Even if it does exit 1,
it doesn't stop at the first sign of damage.
Sort of like "Mom's going to find out anyway, so we might as well eat
even more cookies."
P.S., I made https://github.com/RsyncProject/rsync/issues/654
This bug report was last modified 294 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.