bug#21760: timeout: Feature Request: --verbose ==> output if timeout

On 27/11/17 07:18, Bernhard Voelker wrote: > [sending again, because the first try came back with some unclear > error message, and the message didn't show up on the ML so far.] > > On 11/24/2017 02:48 AM, Pádraig Brady wrote: >> Pushed with those improvements. > > Sorr

bug#29421: bug in command "tr"

tag 29421 notabug close 29421 stop On 23/11/17 17:01, wangjian wrote: > Hi there, I think this is a bug > > mkdir empty_foler > cd empty_foler > touch a > echo "abc" | tr [:blank:] + # you will get “+bc” as output, instead of “abc” > touch b > echo "abc" | tr [:blank:] # you will get “bbc” as

bug#21760: timeout: Feature Request: --verbose ==> output if timeout

On 23/11/17 15:38, Jim Meyering wrote: > On Thu, Nov 23, 2017 at 2:35 PM, Pádraig Brady <p...@draigbrady.com> wrote: > ... >>> So I'm leaning towards supporting --verbose which would output something >>> like: >>> >>> timeout: aborting command 'b

bug#21760: timeout: Feature Request: --verbose ==> output if timeout

On 03/10/17 23:36, Pádraig Brady wrote: > On 02/10/17 07:04, Ian Jackson wrote: >> I have to say that I find this bug thread quite perplexing. >> >> It is completely normal for a GNU/Unix command line utility to print a >> message to stderr in error cases. Almo

bug#29259: tail does not seek to the end of block device

On 12/11/17 22:21, Pádraig Brady wrote: > On 12/11/17 21:52, Paul Eggert wrote: >> Why doesn't lseek work for this? > > Good call, it probably would. > Something like the following is more acceptable > since it adds very little complexity: Full patch attached with tests. c

bug#29259: tail does not seek to the end of block device

On 12/11/17 21:52, Paul Eggert wrote: > Why doesn't lseek work for this? Good call, it probably would. Something like the following is more acceptable since it adds very little complexity: diff --git a/src/tail.c b/src/tail.c index 1c7418d..a10470b 100644 --- a/src/tail.c +++ b/src/tail.c @@

bug#29259: tail does not seek to the end of block device

On 11/11/17 12:08, David Durham wrote: > sudo tail -c 1024 /dev/sda2 | hd the entire /dev/sda2 device rather than > seeking to the end. This takes a very long time with large disks. Deltik > gives a nice explanation here - >

bug#29167: Acknowledgement (tests/ls/readdir-mountpoint-inode.sh is unstable and should require root privileges)

On 06/11/17 04:06, Thomas Deutschmann wrote: > Hi, > > here's a better fix (from Sebastian Kühn via > https://bugs.gentoo.org/353164): > > diff --git a/tests/ls/readdir-mountpoint-inode.sh > b/tests/ls/readdir-mountpoint-inode.sh > index b4ca9e46e..5270df079 100755 > ---

bug#29038: df hangs on fifos/named pipes

On 29/10/17 23:16, Paul Eggert wrote: > Pádraig Brady wrote: > >> I suppose we could stat() and if that succeeds && !fifo, only then call >> open() ? >> Patch to do that is attached. > > Better is to use open with O_NONBLOCK, as this avoids interpreting

bug#29038: df hangs on fifos/named pipes

On 28/10/17 00:18, Stephane Chazelas wrote: > test case: > >mkfifo p >df p > > That hangs, unless you make "p" non-readable or some other process > has the fifo open in write mode. > > The reason is that df tries to open the fifo in read-only mode, > according to comments in the source

bug#29022: tail: unrecognized file system type 0x794c7630 for...

close 29022 stop On 26/10/17 16:42, Gustavo Frederico wrote: > tail: unrecognized file system type 0x794c7630 for > '/u01/app/oracle/diag/tnslsnr/e7bd4e34ce20/listener/alert/log.xml'. please > report this to bug-coreutils@gnu.org. reverting to polling Already fixed (in coreutils 8.25).

bug#29044: sort --debug results improvement

On 29/10/17 11:40, 積丹尼 Dan Jacobson wrote: > < P.S., Yes indeed I had LC_COLLATE=C so maybe --debug should mention > < where in the environment it made it choices from too. > > Ah, like you said > > $ LC_ALL=en_CA.UTF-8 sort --debug < /dev/null > sort: using ‘en_CA.UTF-8’ sorting rules > >

bug#29055: A little bug in bash to win10

close 29055 stop On 29/10/17 08:56, Allan Jensen wrote: > When i use the instruction tail -f filename > it stops after 10 lines and givs error message ( in Danish ) > > tail:ukendt filsystemtype ox53464846 for ´ALL_2017_10.TXT´. > rapporter venlig dette til bug-coreutils@gnu.org. går over til

bug#28991: df: wrong output when a FS masks another one

On 25/10/17 07:57, Stephane Chazelas wrote: > Test case: > > /tmp$ mkdir -p 1/2 > /tmp$ sudo mount -o size=1M -t tmpfs x 1/2 > /tmp$ sudo mount -o size=2M -t tmpfs y 1 > /tmp$ mkdir 1/2 > /tmp$ df -h 1/2 > Filesystem Size Used Avail Use% Mounted on > x 2.0M 0 2.0M 0%

bug#28989: stat(1) man page should reference statfs(2) in addition to stat(2)

On 25/10/17 03:57, Vincent Lefevre wrote: > According to strace, statfs() is used when the --file-system is used. > > The stat(1) man page has: > > SEE ALSO >stat(2) > > It should have: > > SEE ALSO >stat(2), statfs(2) Pushed in your name at:

bug#28985: expand --tabs transposes expansions in output, does other unexpected things

tag 28985 notabug close 28985 stop On 24/10/17 19:21, Chris King-Parra wrote: > Package: coreutils > Version: 8.28 > > Hi there, > > I was reading the info pages for ``expand`` this afternoon and came across the > > ``--tabs`` option. To my understanding, you supply it

bug#28859: Segmentation fault with NULL pointer dereference in 'stty'

On 16/10/17 10:49, Jim Meyering wrote: > On Mon, Oct 16, 2017 at 2:30 AM, Pádraig Brady <p...@draigbrady.com> wrote: >> On 15/10/17 18:07, Jaeseung Choi wrote: >>> Dear GNU team, >>> >>> While testing coreutils for a research purpose, we found the f

bug#28859: Segmentation fault with NULL pointer dereference in 'stty'

On 15/10/17 18:07, Jaeseung Choi wrote: > Dear GNU team, > > While testing coreutils for a research purpose, we found the following > crash in 'stty'. Running stty with the command-line "stty eol -F AA" > raises a crash as below. We did not change any terminal setting, and > believe the bug is

bug#28860: Segmentation fault with out-of-bound read in 'b2sum'

On 15/10/17 18:04, Jaeseung Choi wrote: > Dear GNU team, > > While testing coreutils for a research purpose, we found the following > segfault in 'b2sum'. Running b2sum with --check option, and simply > providing a string "BLAKE2" with no trailing character raises the > crash as below. Wow

bug#28846: Maybe a bug in "sort (GNU coreutils) 8.4" report

forcemerge 28846 28847 tag 28846 notabug close 28846 stop On 15/10/17 01:03, Tree Big wrote: > Dear coreutils : > I am a Research and Development Engineer in IT. I met a situation when I > use “sort” command in Linux shell which could be a bug for the "sort" > command. So I hope you read this

bug#28763: docbug (stat -t): missing field names in docs(manpage) for 'stat -t'

On 11/10/17 13:39, Bernhard Voelker wrote: > + > + printf (_("\n\ > +--terse without SELinux is equivalent to the following FORMAT:\n\ > +%s\ > +--terse with SELinux enabled is equivalent to the following FORMAT:\n\ > +%s\ > +"), fmt_terse_regular, fmt_terse_selinux); > +

bug#21760: timeout: Feature Request: --verbose ==> output if timeout

On 02/10/17 07:04, Ian Jackson wrote: > I have to say that I find this bug thread quite perplexing. > > It is completely normal for a GNU/Unix command line utility to print a > message to stderr in error cases. Almost every program that exits > nonzero prints a message to stderr. > > The normal

bug#28574: cross compilnng, man pages

On 03/10/17 13:51, Manuel A. Fernandez Montecelo wrote: > Thanks for taking a look into this, I think that it's a good idea. > > In the case that somehow help2man can still end up being used after > applying this, I think that Eleanor's patch (or an equivalent) is > still worth considering,

bug#28574: cross compilnng, man pages

On 23/09/17 20:18, Peter Bohning wrote: > Cross compiling for aarch64 from amd64 > > Is there no way to disable the man pages in configure options? Thanks. > > https://lists.gnu.org/archive/html/coreutils/2014-11/msg0.html I've seen this issue in various places now (CC'd). We should

bug#28582: Coreutils 'make check' failure due to expr change

On 24/09/17 09:48, Paul Eggert wrote: > I have the following in my environment: > > LC_ALL=en_US.utf8 > LC_COLLATE=en_US.UTF-8 > LC_CTYPE=en_US.UTF-8 > LC_MESSAGES=en_US.UTF-8 > > When I run 'make check' for bleeding-edge Coreutils, I get a failure due to > recent changes in expr.

bug#28506: coreutils 8.28 test suite hangs on APFS filesystem

On 22/09/17 20:07, Pádraig Brady wrote: > Is is a wait or a cpu spin? > Could you use the equivalent of strace on your platform to see what's > happening? Offlist Jack sent a profile showing /usr/bin/FILE was waiting on input. That was the result of a silly typo in the script, which the

bug#28506: coreutils 8.28 test suite hangs on APFS filesystem

On 21/09/17 17:23, Jack Howarth wrote: > On Thu, Sep 21, 2017 at 1:20 AM, Pádraig Brady <p...@draigbrady.com> wrote: > >> On 18/09/17 18:07, Jack Howarth wrote: >>> On Mon, Sep 18, 2017 at 7:40 PM, Jim Meyering <j...@meyering.net> wrote: >>> >>

bug#28506: coreutils 8.28 test suite hangs on APFS filesystem

On 20/09/17 23:02, Jim Meyering wrote: > On Wed, Sep 20, 2017 at 10:20 PM, Pádraig Brady <p...@draigbrady.com> wrote: >> On 18/09/17 18:07, Jack Howarth wrote: >>> On Mon, Sep 18, 2017 at 7:40 PM, Jim Meyering <j...@meyering.net> wrote: >>> >>>

bug#28506: coreutils 8.28 test suite hangs on APFS filesystem

On 18/09/17 18:07, Jack Howarth wrote: > On Mon, Sep 18, 2017 at 7:40 PM, Jim Meyering wrote: > >> On Mon, Sep 18, 2017 at 4:26 PM, Jack Howarth >> wrote: >>> On Mon, Sep 18, 2017 at 5:08 PM, Jim Meyering wrote: >> ...

bug#28507: shred 8.28 renames files only once

On 18/09/17 16:02, pengu1n wrote: > Hello. > > [coreutils 8.27] > > $ touch test > $ shred -vu test > > shred: test: removing > shred: test: renamed to > shred: : renamed to 000 > shred: 000: renamed to 00 > shred: 00: renamed to 0 > shred: test: removed > > [coreutils 8.28] > > $

bug#28461: erreurs

On 15/09/17 20:44, Jim Meyering wrote: > On Fri, Sep 15, 2017 at 8:37 PM, Pádraig Brady <p...@draigbrady.com> wrote: > ... >> That's a good improvement! > > Indeed! > >> >> I'd change: >> >> s/missing more parameters after/missing parameter

bug#28461: erreurs

On 14/09/17 23:41, Assaf Gordon wrote: > Hello, > > On 2017-09-14 11:45 PM, Bernhard Voelker wrote: >>> On 2017-09-14 11:43 AM, Eric Mariaud wrote: eric@Eric-Xub:~/Bureau$ expr 2 * 3 expr: erreur de syntaxe >> >> Well, we could try to improve the error diagnostics. >> >> WDYT? > > Very

bug#28432: dd doesn't warn about partial read on final call to iread

On 12/09/17 08:51, Barry Handelman wrote: > The iread function in dd.c issues a warning if the previous read was short, > suggesting that you use iflag=fullblock > > However, the warning is issued when the previous call to iread was partial, > so if only the final read was short then no warning

bug#28417: ptx does not terminate when matching a zero length sentence regex

On 13/09/17 14:40, Bernhard Voelker wrote: > On 09/11/2017 05:04 PM, Julian Büning wrote: >> observed behavior: >> >> $ echo | ptx -S $ & >> [1] 1000 >> $ jobs >> [1]+ Running echo | ptx -S $ & >> >> expected behavior: >> >> $ echo | ptx -S $ & >> [1] 1000 >> [1]+ Done

bug#28290: Fwd: tail: unrecognized file system type 0x794c7630

On 29/08/17 22:51, Olov Pettersson wrote: > Hi, I got this in tail > > tail: unrecognized file system type 0x794c7630 for >> '/var/log/bucardo/log.bucardo'. please report this to >> bug-coreutils@gnu.org. reverting to polling Already handled in newer versions. thanks

bug#24541: runcon tty hijacking via TIOCSTI ioctl

On 29/09/16 08:15, Bernhard Voelker wrote: > On 09/26/2016 05:53 PM, Paul Eggert wrote: >>> "I don't think we need to fix this for runcon, as it isn't as >>> sandboxing tool like sandbox, and the loss of job control would likely >>> be much more noticeable for runcon." >> >> Thanks, closing the

bug#28054: coreutils 8.27 test failure on x86_64-foxkit-linux-musl

On 17/08/17 21:55, A. Wilcox wrote: > On 13/08/17 11:22, Jim Meyering wrote: >> On Sun, Aug 13, 2017 at 1:07 AM, Pádraig Brady <p...@draigbrady.com> >> wrote: >>> On 11/08/17 11:49, A. Wilcox wrote: >>> >>>> FAIL: tests/misc/csplit-io-

bug#28054: coreutils 8.27 test failure on x86_64-foxkit-linux-musl

On 13/08/17 09:22, Jim Meyering wrote: > On Sun, Aug 13, 2017 at 1:07 AM, Pádraig Brady <p...@draigbrady.com> wrote: >> On 11/08/17 11:49, A. Wilcox wrote: >> >>> FAIL: tests/misc/csplit-io-err >>> == >> This was due to

bug#28082: bash: /bin/rm: Argument list too long

tag 28082 notabug close 28082 stop On 13/08/17 14:35, Jonny Grant wrote: > Hello > > Can this be resolved please? Seems a shame in 2017 on a machine with > 16GB of ram I suffer this. Each filename is around 40 bytes. > > Roughly 60,000 files > > So total strings around 2.4 MBytes. Quite a

bug#28054: coreutils 8.27 test failure on x86_64-foxkit-linux-musl

On 11/08/17 11:49, A. Wilcox wrote: > FAIL: tests/misc/csplit-io-err > == This was due to an inconsistency in the errors output by seq. A fix for that buglet is attached. > FAIL: tests/misc/printf-surprise > Depending on exit 141

bug#27864: [request] safety to prevent `rm -rf ~`

On 28/07/17 09:28, R0b0t1 wrote: > I recently had a script create a file named "~" when I passed it a > value for an installation directory. Without thinking the next command > I typed was the one in the title. Luckily this was not my main > computer and was a virtual machine. > > It does not

bug#27640: Bug-report

On 10/07/17 00:46, Wolfgang F. Muthmann wrote: > FAIL: test-getlogin > === > > test-getlogin.c:92: assertion 'strcmp (pwd->pw_name, buf) == 0' failed > FAIL test-getlogin (exit status: 134) Forwarding to gnulib thanks, Pádraig

bug#27531: Coreutils 8.27 bug report

On 29/06/17 06:32, Bernardo Lopes Almeida de Oliveira wrote: > Dear all, > > Please find attached the test-suite.log. The date false failure is already fixed I think. The seq failure though is due to your system not behaving like: $ src/seq inf inf | head -n2 inf inf What architecture

bug#26779: expr length

On 27/06/17 18:41, Assaf Gordon wrote: > Hi, > > Attached work-in-progress for expr/multibyte, > hopefully fixing all (most?) of the coding style issues > (Internal conversion to wide strings not yet implemented). > > Comments welcomed, > - assaf > Excellent work. This looks to have

bug#27488: du -tX -t-Y won't exclude or select an interval of SIZE

On 25/06/17 11:08, f0rhum wrote: > I know man clearly states "exclude entries smaller than SIZE if > positive, or entries greater than..." > I don't know if it is a restriction in my 8.21, but only the last -t > option in my command line applies. > If not, maybe a feature could allow this

bug#27478: reporting bug fir tail command

unarchive 23273 forcemerge 23273 27478 close 27478 stop On 24/06/17 12:42, sai sasanka wrote: > Hello, > > When I ran " tail -Fn0 tail.sh" I got the following output, "tail: > unrecognized file system type 0x53464846 for ‘tail.sh’. please report this > to bug-coreutils@gnu.org. reverting to

bug#27420: Self Destruct - Self Erase of All Data On SD Card Using Shred,

tag 27420 notabug close 27420 stop On 18/06/17 00:22, John Shearing wrote: > favorite > > > I will be using a raspberry pi as an air-gapped computer to make

bug#27368: Minor concern: Confusing tail warning

On 17/06/17 14:30, Pádraig Brady wrote: > On 17/06/17 07:35, Jim Meyering wrote: >> In this new function, please move the declaration of "i" into the for-loop: >> >> +static bool >> +any_non_regular (const struct File_spec *f, size_t n_files) >>

bug#27368: Minor concern: Confusing tail warning

On 17/06/17 07:35, Jim Meyering wrote: > On Sat, Jun 17, 2017 at 1:32 AM, Pádraig Brady <p...@draigbrady.com> wrote: > ... >> Two proposed patches for this are attached. > > Nice fixes. Thank you! > > In the NEWS addition: > >tail -f will now exi

bug#27368: Minor concern: Confusing tail warning

On 15/06/17 02:40, Pádraig Brady wrote: > On 14/06/17 16:03, Charlie Hagedorn wrote: >> Hi! >> >> Thank you for maintaining such useful and reliable tools. >> >> Today I came across an unexpected warning in tail. The warning is intended >> to handle this cas

bug#27368: Minor concern: Confusing tail warning

On 14/06/17 16:03, Charlie Hagedorn wrote: > Hi! > > Thank you for maintaining such useful and reliable tools. > > Today I came across an unexpected warning in tail. The warning is intended > to handle this case: > > [:~]$ tail -f > tail: warning: following standard input indefinitely is

bug#27276: Bug in using Tail command

tag 27276 notabug close 27276 stop On 07/06/17 07:31, Deepak Cp wrote: > Hi team, > > I am getting following error while using "tail -f": > > tail: unrecognized file system type 0x794c7630 for ‘sslstrip.log’. please > report this to bug-coreutils@gnu.org. reverting to polling > > The linux

bug#27240: inconsistent and confusing output from 'ln' vs. 'cp': can this be fixed?

On 04/06/17 22:07, Paul Eggert wrote: > Pádraig Brady wrote: >> Well => is for hardlinks, and both -> and => were used >> to distinguish the operations (in v5.92-191-g24ce72f) > > As I understand it, part of the motivation is consistency with 'ls': > > $

bug#27240: inconsistent and confusing output from 'ln' vs. 'cp': can this be fixed?

On 04/06/17 14:12, L A Walsh wrote: > > Needing to hardlink some files from tree1 to tree2, I > had them in a script and @first used: > "cp -lv": > >> cp -lv src/a dst/a > 'src/a' -> 'dst/a' > > Later, I thought to use 'ln -v' for a different tree: > >> ln -v src/a dst/a > 'dst/a' =>

bug#27136: info coreutils

On 29/05/17 14:06, kalle wrote: > hello, > I think it is not obvious for everyone how to deal with Standard Input in the > `cat'-command. I took some time to figure out, that Ctrl-d aborts it. and > just now I realized, that EOF the first time acts to terminate a so called > "record" (I got

bug#27129: split adding zeroes to suffix

tag 27129 notabug close 27129 stop On 29/05/17 02:18, thomas kaeding wrote: > This has happened twice to me, for two different files, > with the same size. This file is called "20170528". > > -rw-r--r-- 1 kaeding kaeding 4700176384 May 28 16:00 20170528 > > split -b 4710 -d 20170528

bug#27128: fold -b wants no immediate space, otherwise mistakes number as filename

tag 27128 notabug close 27128 stop On 29/05/17 08:42, davidpbrown wrote: > coreutils v 8.25-2ubuntu2 > > fold -b error wanting no space before the number, inconsistent with > expectation and -w > > > Error: > > $ echo "abcdefghijklm" | fold -b 6 > fold: 6: No such file or directory > > >

bug#27109: man unlink problem

On 28/05/17 01:54, Jonny Grant wrote: > Hello > > I noticed a problem in the "man unlink" page. > > The OPTIONS section is missing, and the Options are listed in the > DESCRIPTION section. Could the OPTIONS section be added? > > Thank you, Jonny I presume you're comparing with rm(1)? Though

bug#26991: New quoting takes up unnecessary space

On 19/05/17 07:48, L A Walsh wrote: > > > The new format uses extra spacing on columns where it isn't needed -- > but the extra space isn't enough to handle the 1 file that was quoted > (needs 5 extra columns). Where does it get '3' (and why doesn't it use > 2?)? Yes one can construct edge

bug#26971: mv -v output ordering looks impossible

On 17/05/17 22:46, 積丹尼 Dan Jacobson wrote: > PB> So this is working across file systems > Yes. >>> '/home/jidanni/jidanni.org/location/grow/programs' -> '/tmp/programs' > This says to me "I, the mv command, have just moved A to B. > > PB> create dir /tmp/programs > If that (create B) is what it

bug#26971: mv -v output ordering looks impossible

On 17/05/17 21:19, 積丹尼 Dan Jacobson wrote: > I do > mv -v /home/jidanni/jidanni.org/location/grow/programs /tmp So this is working across file systems > and see > '/home/jidanni/jidanni.org/location/grow/programs' -> '/tmp/programs' create dir /tmp/programs >

bug#26783: Discrepancy with uptime added as part of "[PATCH] Document uptime."

On 11/05/17 06:40, Prateek saxena wrote: > Hi Pádraig, > > Thanks for replying. > > When we can expect the fix. > > Can we use the attached patch as workaround for time been. whether it > would be sufficient. Your patch is now applied at:

bug#26869: bug-coreutils@gnu.org

On 10/05/17 13:14, Marshall Onsrud wrote: > I am running tail on a text file in a Centos 7 Docker on top of CoreOS. > > I see this message whenever I tail this file: > > tail: unrecognized file system type 0x794c7630 for > \u2018sda_written_locally.txt\u2019. please report this to >

bug#26779: expr length

On 09/05/17 00:04, Assaf Gordon wrote: > Hello, > >> On May 4, 2017, at 11:43, Pádraig Brady <p...@draigbrady.com> wrote: >> >> On 04/05/17 02:59, Андрей Воронов wrote: >>> I have the bug in expr utility when it perform operation of the >>> c

bug#26783: Discrepancy with uptime added as part of "[PATCH] Document uptime."

On 04/05/17 23:03, Prateek saxena wrote: > Hi, > > We found some discrepancy with uptime utility of coreutils package. > > In my system using coreutils package with version 8.26, uptime output prints > PM/AM for 24 hour time format. > > Logs: >

bug#26779: expr length

On 04/05/17 02:59, Андрей Воронов wrote: > Hello, > > I have the bug in expr utility when it perform operation of the > calculating length of the string in my multi-byte encoding ru_RU.UTF-8. > When I run: "expr length Привет" > it return me the number 12. > But in the russian word "Hello" the

bug#26762: [PATCH] doc: Fixed typo in timeout man page

On 03/05/17 04:37, Jaak Ristioja wrote: > * man/timeout.x: Correct spelling of "currently". > --- > man/timeout.x | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/man/timeout.x b/man/timeout.x > index cefa1228e..ddb309251 100644 > --- a/man/timeout.x > +++ b/man/timeout.x

bug#26766: Bug found while using 'tail' in a Docker container

On 03/05/17 13:57, Brian Drawert wrote: > The program 'tail' just reported a bug, and requested that I send in a bug > report. This is the line: > > tail: unrecognized file system type 0x794c7630 for 'stderr.log'. please > report this to bug-coreutils@gnu.org. reverting to polling > > I

bug#26727: Plain ls (from coreutils git master local build) sometimes emit leading spaces at output lines

tag 26727 notabug close 26727 stop On 01/05/17 02:17, Shlomi Fish wrote: > On Mageia x86-64 6 and fedora 26 x86-64, I am getting this with an ls > inovcation with ls from coreutils git master commit > d91e912343ab04b37d011b5c8a7c0723edc35e3d : > > shlomif@telaviv1:~$

bug#26709: Tests failing.

On 29/04/17 01:37, Григорий Резников wrote: > > I've tried to improve tests coverage, so I've built and ran tests using > following commands: > > ./configure CFLAGS="-g -fprofile-arcs -ftest-coverage" > make -j8 > sudo make check -j8 > > After that I got FAIL on tests/mv/sticky-to-xpart and

bug#26621: hint for translators is missing from POT file, but is opaque anyhow

On 23/04/17 08:17, Benno Schulenberg wrote: > > Commit 2dab6cd3c2e18eb574b24e54fba86a33c80b6a27 changed > the progress messages for dd, but in doing so separated > the instruction/hint for translators from the call to > ngettext(). For xgettext to pick up such comments, the > comment must end of

bug#26631: tr: extra operand ‘\\\\’

On 23/04/17 10:39, 積丹尼 Dan Jacobson wrote: > $ tr -s x -d '\\' > tr: extra operand ‘’ > Try 'tr --help' for more information. > > I only gave '\\'. That's a result of the quoting used, the default mode add backslashes for some characters (including backslash). Now you could argue that input

bug#26545: shred: buffer overlap, some data not wiped

On 17/04/17 11:53, Bogdan wrote: > Hi. > > I believe I've found a bug in shred.c, function fillpattern(): there > is code that says: > > for (i = 3; i < size / 2; i *= 2) > memcpy (r + i, r, i); > if (i < size) > memcpy (r + i, r, size - i); > > The problem occurs for specific

bug#26519: Documentation for cut --fields=field-list giving faulty info on awk

On 14/04/17 09:24, Bo Rydberg wrote: > As seen at > https://www.gnu.org/software/coreutils/manual/html_node/cut-invocation.html, > the section for ‘-f field-list’ > ‘--fields=field-list’ hints at some examples of using awk. The second example > is wrong. it states: > awk '{print $NF-1}' # print

bug#26363: [PATCH] tail: 'tail -F dir/file' reverts to polling mode if 'dir' is removed

Pushed with some NEWS and test tweaks at: http://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=ba5fe2d Marking this as done. thanks! Pádraig.

bug#26364: [PATCH] Handle possible NULL return value of tzalloc.

On 04/04/17 13:04, Tobias Stoeckmann wrote: > The function tzalloc of gnulib can return NULL. It uses malloc() > internally and forwards its possible NULL value to the caller. > > As other gnulib functions rely on that behaviour, it cannot be simply > exchanged with an error-calling malloc

bug#26363: [PATCH] tail: 'tail -F dir/file' reverts to polling mode if 'dir' is removed

On 04/04/17 09:47, Sebastian Kisela wrote: > * src/tail.c (tail_forever_inotify): Add the IN_DELETE_SELF flag when > creating watch for the parent directory. After the parent directory > is removed, an event is caught and then we switch from inotify to > polling mode. Till now, inotify has

bug#26324: Tail does not recognize .log file type

On 31/03/17 08:26, Kevin Bedard wrote: > Hello. When I execute a ‘tail -f ‘ on my product’s log file (text based > file), I get the error below, however, the file contents is still displayed > and updated in real time. > > > > *tail: unrecognized file system type 0xf15f083d for 'aerolink.log'.

bug#26318: csplit

tag 26318 notabug close 26318 stop Murray sent an update privately indicating it wasn't a csplit issue.

bug#26311: dd support for POSIX_FADV_NOREUSE etc.

On 30/03/17 10:55, Paul Eggert wrote: > On 03/30/2017 09:30 AM, Pádraig Brady wrote: >> Yes maybe, though the low level meanings of these flags are >> a bit confusing and I'm not sure how consistent they are over kernel versions > > Nor I. Still, 'dd' to some extent is suppo

bug#26311: dd support for POSIX_FADV_NOREUSE etc.

On 30/03/17 08:42, Paul Eggert wrote: > The 'dd' command has some complicated logic for iflag=nocache and > oflag=nocache, which I don't entirely understand but expect is in there > for good reason. I suggest that 'dd' also have simpler logic for direct > usage of posix_fadvise options. For

bug#26253: tests/misc/cut-huge-range.sh fails on arm-linux-gnueabihf

On 27/03/17 02:18, Ludovic Courtès wrote: > Hi Pádraig, > > Pádraig Brady <p...@draigbrady.com> skribis: > >> On 26/03/17 06:41, Ludovic Courtès wrote: > > [...] > >>> Part of the reason, I think, is that ‘vm’ is computed by simply running >>&

bug#26263: sha256sum does not correctly parse file with PGP message header (coreutils 8.26)

On 26/03/17 03:09, Toby Kelsey wrote: > I notice sha256sum does not correctly parse a file with a PGP header. Here is > a script log: > toby@toby-pc:/tmp/test$ sha256sum -c hashes.txt > > sha256sum: ' monero-win-x64-v0.10.3.0.zip': No such file or directory > monero-win-x64-v0.10.3.0.zip:

bug#26253: tests/misc/cut-huge-range.sh fails on arm-linux-gnueabihf

On 26/03/17 06:41, Ludovic Courtès wrote: > Hi Pádraig, > > We found that ‘tests/misc/cut-huge-range.sh’ would fail on our ARMv7 > GNU/Linux machines: > > https://bugs.gnu.org/26253 > > (I noticed there’s a thinko in the patch I used for Guix: ‘getconf > PAGESIZE’ returns bytes whereas

bug#26101: Counterproductive calculation order in date

On 15/03/17 05:44, Eric Blake wrote: > On 03/15/2017 07:23 AM, Ulf Zibis wrote: > >> >> A more simple example without touch: >> $ date +%F >> 2017-03-15 >> $ date -d "-20 day" +%F >> 2017-02-23 >> $ date -d "-20 day -2 month" +%F >> 2016-12-26 >> $ date -d "-2 month -20 day" +%F >> 2016-12-26 >>

bug#26081: --date=STRING error that started midnight 3/12

On 13/03/17 05:17, Eric Blake wrote: > tag 26081 notabug > thanks > > On 03/13/2017 12:09 AM, Fevzi Karavelioglu wrote: >> Hello, I started getting an error with the following command: >> >> $> date --date="02:05 tomorrow" +%s >> *date: invalid date `02:05 tomorrow'* >> >> It appears any time 2

bug#26044: coreutils-8.27 fails to build

On 11/03/17 09:12, J Rogowsky wrote: > On 2017.03.11, at 00:11:03, Pádraig Brady wrote: > >> On 09/03/17 23:22, Pádraig Brady wrote: >>>> BTW, I had only one test FAIL in "make check": tests/misc/sort- >>>> debug- >>>> keys >>

bug#26044: coreutils-8.27 fails to build

On 09/03/17 23:22, Pádraig Brady wrote: >> BTW, I had only one test FAIL in "make check": tests/misc/sort-debug- >> keys >> Is this related to the above? > I'm guessing that "failure" might be locale related. > Could you attach the tests/test-suite.l

bug#26044: coreutils-8.27 fails to build

On 10/03/17 12:19, Mihai Moldovan wrote: > We (naturally) also hit that in MacPorts. > > Downstream bug report: https://trac.macports.org/ticket/53764 > > I've fixed it for our package by manually inserting the renameat gnulib > module. > > I assume that your change to bootstrap.conf also

bug#26044: coreutils-8.27 fails to build

On 09/03/17 22:08, J Rogowsky wrote: > coreutils-8.27 fails to build. > > function renameat, found in src/force-link.c, is not found on my > system, which is an iBook G4 running OSX 10.5.8. > Therefore the link step fails, citing the linker cannot find _renameat. Drats. It looks like the

bug#25999: SHA1SUM: please switch to sha1dc to warn of attempted hash collision attacks

On 06/03/17 07:16, Henrique de Moraes Holschuh wrote: > This is a feature request, in light of the "shattered" attack against > SHA-1[1] published by Google. > > A drop-in replacement for sha1 exists, based on the concept of > counter-cryptanalysis[2]. This drop-in replacement can detect when

bug#26002: [patch] md5sum --digest-only

On 05/03/17 23:55, Michael Vogt wrote: > Hi, > > this is a bit of a RFC (anlong with a patch). I would like to have an > option in md5sum (and friends) that displays only the digest without > the filename. The use-case is mostly package maintainer scripts. They > often need the md5sum to e.g.

bug#25870: give an example to show what lines join -a and -v are talking about

forcemerge 25870 25871 close 25870 stop On 27/02/17 20:17, Assaf Gordon wrote: > >> On Feb 27, 2017, at 16:02, Assaf Gordon wrote: >> [...] >> >> I've added all combinations to the 'unpaired lines' section, >> and also added the examples from your website to a new section

bug#25870: give an example to show what lines join -a and -v are talking about

On 27/02/17 20:17, Assaf Gordon wrote: > >> On Feb 27, 2017, at 16:02, Assaf Gordon wrote: >> [...] >> >> I've added all combinations to the 'unpaired lines' section, >> and also added the examples from your website to a new section "Set >> operations on files". >> >>

bug#25870: give an example to show what lines join -a and -v are talking about

On 26/02/17 23:32, Assaf Gordon wrote: > Hello Dan, >> On Feb 25, 2017, at 08:20, 積丹尼 Dan Jacobson wrote: >> [...] >> And in fact give an example to show what lines -a and -v are talking about! >> > > Good idea. > Here's a rough draft. I like how the options are now

bug#25540: notice issue in expand -- doesn't allow for expressing tabsize value in tabstop(s)

On 26/01/17 03:27, Reuti wrote: > >> Am 26.01.2017 um 12:04 schrieb Pádraig Brady <p...@draigbrady.com>: >> >> On 26/01/17 10:26, Reuti wrote: >>> >>>> Am 26.01.2017 um 05:29 schrieb L A Walsh <coreut...@tlinx.org>: >>>> >&g

bug#25832: split (v 8.25) with numeric suffixes beyond 89

On 21/02/17 20:01, Assaf Gordon wrote: > >> On Feb 21, 2017, at 22:32, Pádraig Brady <p...@draigbrady.com> wrote: >> >> This was discussed at http://bugs.gnu.org/20874 > > Missed that - sorry. I should've looked through the archives first... > >> I

bug#25378: cp does not preserve SElinx context of sub folder

On 20/02/17 23:18, Bernhard Voelker wrote: > Hi Padraig, > > only some minor remarks from my side. > > On 02/21/2017 04:11 AM, Pádraig Brady wrote: >> From d17ca013f3aadcf697663830fa9ec34cba551f66 Mon Sep 17 00:00:00 2001 >> From: =?UTF-8?q?P=C3=A1draig=20Brady?= &l

bug#25378: cp does not preserve SElinx context of sub folder

On 20/02/17 20:46, Paul Eggert wrote: > Does 'mkdir -Z --parents' need a similar patch? Already handled. > > Minor points: > > Please don't use 'extern' in front of function definitions. Just decls. > > The usual style in .h files is to say "extern type function (args);" rather > than > to

bug#25378: cp does not preserve SElinx context of sub folder

On 06/01/17 00:19, HE Henry wrote: > Hi coreutils team, > > When using cp with --parents options, the SELinux context of sub folders are > not preserved. > > Example as below: > > 1. Before using cp: > [root@oame0 etc]# pwd > /etc > [root@oame0 etc]# ls -Z selinux/ > -rw-r--r--. root root

<    2   3   4   5   6   7   8   9   10   11   >