On Fri, 2023-03-31 at 22:53 +0200, Sven Joachim wrote: > Or complain on upstream > bug #62572[1] and ask for a revert of the '-n' exit failure if the > destination exists.
Well -n isn't POSIX. But in strictly speaking their change seems even POSIX compliant to me as that says for both tools: > The following exit values shall be returned: > 0 > All input files were [copied/moved] successfully. > >0 > An error occurred. and one could argue that this ain't the case with -n if the destination already exists. It's however open to debate whether --no-clobber would have fallen into that spirit. OTOH, e.g. GNU coreutil cp's info page says in at least 9.1: >An exit status of zero indicates success, and a nonzero value >indicates failure. So with that in mind they seem to break their own "promise" with that change. Anyway,... I have no strong opinions on that matter. In any case, I don't think Debian should do anything else than upstream/other-distros in that particular point. Cheers, Chris.
