bug#30534: cp - Possible bugs when not preserving mode (explicit) and when copying special files

2018-02-19 Thread Pádraig Brady
On 19/02/18 02:22, Declercq Laurent wrote: > I think that I did found at least two bugs in cp(1) command when the > --no-preserve=mode option is involved and when copying special file. I > describe each of them below. > > 1. Mode set on special files seem to be wrong: > > Original file to

bug#29617: `seq 1 --help' doesn't give help

2018-02-19 Thread chadweisman
On 2/19/2018 at 8:35 PM, "Pádraig Brady" wrote: > >On 18/02/18 10:41, chadweis...@nym.hush.com wrote: >> >>> On 12/08/2017 11:38 AM, Eric B wrote: Hello, I am using coreutils version 8.27 on Fedora, and I don't see >this fixed in 8.28's NEWS.

bug#29617: `seq 1 --help' doesn't give help

2018-02-19 Thread Pádraig Brady
On 18/02/18 10:41, chadweis...@nym.hush.com wrote: > >> On 12/08/2017 11:38 AM, Eric B wrote: >>> Hello, >>> >>> I am using coreutils version 8.27 on Fedora, and I don't see this fixed in >>> 8.28's NEWS. >>> >>> $ seq 1 --help >>> seq: invalid floating point argument: ‘--help’ >>> Try 'seq

bug#30534: cp - Possible bugs when not preserving mode (explicit) and when copying special files

2018-02-19 Thread Declercq Laurent
I think that I did found at least two bugs in cp(1) command when the --no-preserve=mode option is involved and when copying special file. I describe each of them below. 1. Mode set on special files seem to be wrong: Original file to copy: prw-rw-rw- 1 root staff 0 févr. 18 18:59 spfile cp(1)