bug#34488: Add sort --limit, or document workarounds for sort|head error messages

2019-02-15 Thread Paul Eggert
On 2/15/19 7:49 AM, 積丹尼 Dan Jacobson wrote: Well the user thinks "hey I cut short 5 lines, 45 lines, 495 lines, and then one I got a job at a big company and cut short 4995 lines and got this error message just when the boss was looking." I'm afraid I'll have to disagree on this one. This is a

bug#34488: Add sort --limit, or document workarounds for sort|head error messages

2019-02-15 Thread Eric Blake
On 2/15/19 3:40 PM, Assaf Gordon wrote: > Helo, > > On 2019-02-15 8:20 a.m., Eric Blake wrote: >> On 2/15/19 8:43 AM, 積丹尼 Dan Jacobson wrote: >>> sort: write failed: 'standard output': Broken pipe >>> sort: write error > [...] >> Perhaps coreutils should teach 'env' a command-line option to forcef

bug#34488: Add sort --limit, or document workarounds for sort|head error messages

2019-02-15 Thread Assaf Gordon
Helo, On 2019-02-15 8:20 a.m., Eric Blake wrote: On 2/15/19 8:43 AM, 積丹尼 Dan Jacobson wrote: sort: write failed: 'standard output': Broken pipe sort: write error [...] Perhaps coreutils should teach 'env' a command-line option to forcefully reset SIGPIPE back to default behavior [...] If we

bug#33468: A bug with yes and --help

2019-02-15 Thread Eric Blake
On 2/15/19 12:32 PM, Assaf Gordon wrote: > Attached updated patches, with tests. It's easier to review patches when they are attached inline without compression (then I don't have to decompress and copy from my editor back into my email), but I can cope with your .gz attachments. > > comments w

bug#33468: A bug with yes and --help

2019-02-15 Thread Assaf Gordon
Hello Eric and all, Thanks for the quick and detailed review. I've amended all the issues you mentioned. On 2019-02-13 8:20 p.m., Eric Blake wrote: 15 files changed, 46 insertions(+), 141 deletions(-) Nice diffstat. These are of course Bernhard's improvements, I just did the testing (and

bug#34487:

2019-02-15 Thread Ricky Tigg
That's was just a *live image* that was required, The equivalent of the present CD/DVD's ISO was then *debian-live-9.7.0-amd64-gnome.iso*.

bug#34475: Mention even more worries for test -a

2019-02-15 Thread 積丹尼 Dan Jacobson
By the way https://lists.gnu.org/archive/html/bug-bash/2019-02/msg00052.html says "... contradictory description in the coreutils info document."

bug#34488: Add sort --limit, or document workarounds for sort|head error messages

2019-02-15 Thread 積丹尼 Dan Jacobson
> "EB" == Eric Blake writes: >> And no fair saying "just save the output" (could be big) "into a file >> first, and do head(1) or sed(1) on that." EB> If you have an app that exits noisily on write failures to an early-exit EB> pipe, your solutions are to quit ignoring SIGPIPE, or to change

bug#34490: console the user that his -n in sort --debug -n was seen

2019-02-15 Thread 積丹尼 Dan Jacobson
Can you please have assure the user in that message it makes that it has indeed seen his -n/--numeric-sort. $ sort --debug sort: using simple byte comparison $ sort --debug --numeric-sort sort: using simple byte comparison unchanged. User gets nervous. sort (GNU coreutils)

bug#34488: Add sort --limit, or document workarounds for sort|head error messages

2019-02-15 Thread 積丹尼 Dan Jacobson
> "AG" == Assaf Gordon writes: AG> The errors are not "random" - they happen because you explicitly AG> cut short the output of a program. Well the user thinks "hey I cut short 5 lines, 45 lines, 495 lines, and then one I got a job at a big company and cut short 4995 lines and got this error

bug#34488: Add sort --limit, or document workarounds for sort|head error messages

2019-02-15 Thread Assaf Gordon
severity 34488 wishlist retitle 34488 doc: sort: expand on "broken pipe" (SIGPIPE) behavior stop Hello, On 2019-02-15 7:43 a.m., 積丹尼 Dan Jacobson wrote: Things start out cheery, but quickly get ugly, $ for i in 9 99 999 9; do seq $i|sort -n|sed 5q|wc -l; done 5 5 5 5 sort: write faile

bug#34488: Add sort --limit, or document workarounds for sort|head error messages

2019-02-15 Thread Eric Blake
On 2/15/19 8:43 AM, 積丹尼 Dan Jacobson wrote: > Things start out cheery, but quickly get ugly, > > $ for i in 9 99 999 9; do seq $i|sort -n|sed 5q|wc -l; done > 5 > 5 > 5 > 5 > sort: write failed: 'standard output': Broken pipe > sort: write error > 5 > sort: write failed: 'standard output'

bug#34475: Mention even more worries for test -a

2019-02-15 Thread Assaf Gordon
severity 34475 wishlist retitle 34475 doc: test: expand on -a/-o usage stop Hello, On 2019-02-13 6:00 p.m., 積丹尼 Dan Jacobson wrote: First, on the test(1) man page, at [...]> Say instead [...] I'm marking this as "wishlist" item, patches always welcomed. -assaf

bug#34487: dd (coreutils) 8.30 – A written ISO image cannot not be booted from BIOS

2019-02-15 Thread Assaf Gordon
tags 34487 notabug close 34487 stop Hello, On 2019-02-15 5:02 a.m., Ricky Tigg wrote: Hi. An ISO image cannot not be booted from BIOS [...] # dd if=debian-9.7.0-amd64-DVD-3.iso of=/dev/sdc A CD/DVD image is not the same as a hard drive. The internal structure differs, and one can not be c

bug#34488: Add sort --limit, or document workarounds for sort|head error messages

2019-02-15 Thread 積丹尼 Dan Jacobson
Things start out cheery, but quickly get ugly, $ for i in 9 99 999 9; do seq $i|sort -n|sed 5q|wc -l; done 5 5 5 5 sort: write failed: 'standard output': Broken pipe sort: write error 5 sort: write failed: 'standard output': Broken pipe sort: write error Therefore, kindly add a sort --li

bug#34487: dd (coreutils) 8.30 – A written ISO image cannot not be booted from BIOS

2019-02-15 Thread Ricky Tigg
Hi. An ISO image cannot not be booted from BIOS Initial device state: # parted /dev/sdc unit s print free Model: (...) (scsi) Disk /dev/sdc: 15638480s Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End SizeType File system Flags