bug#62572: cp --no-clobber behavior has changed

2023-12-17 Thread Michael Stone
On Sun, Dec 17, 2023 at 12:34:11AM -0800, Paul Eggert wrote: On 2023-12-16 13:46, Bernhard Voelker wrote: Whether the implementation is race-prone or not is an internal thing. I wasn't referring to the internal implementation. I was referring to cp users. With the newer Coreutils (FreeBSD)

bug#62572: cp --no-clobber behavior has changed

2023-12-17 Thread Dominique Martinet
Paul Eggert wrote on Fri, Dec 15, 2023 at 11:21:06AM -0800: > The cat is to some extent out of the bag. Unless one insists on (FreeBSD | > coreutils 9.2-9.4), or insist on coreutils 7.1-9.1, one should not rely on > cp -n failing or silently succeeding when the destination already exists. > This

bug#62572: cp --no-clobber behavior has changed

2023-12-17 Thread Pádraig Brady
On 16/12/2023 21:46, Bernhard Voelker wrote: On 12/15/23 21:13, Michael Stone wrote: On Fri, Dec 15, 2023 at 11:21:06AM -0800, Paul Eggert wrote: Stlll, Pádraig gave a reasonable summary of why the change was made, To clarify my summary a little, there I said that -n now _immediately_ fails.

bug#62572: cp --no-clobber behavior has changed

2023-12-17 Thread Paul Eggert
On 2023-12-16 13:46, Bernhard Voelker wrote: Whether the implementation is race-prone or not is an internal thing. I wasn't referring to the internal implementation. I was referring to cp users. With the newer Coreutils (FreeBSD) behavior, you can reliably write a script to do something if