bug#58050: [INSTALLED] rm: fix diagnostics on I/O error

2022-09-25 Thread Pádraig Brady
On 25/09/2022 00:37, Paul Eggert wrote: I ran into this problem when attempting to recursively remove a directory in a filesystem on flaky hardware. Although the underlying readdir syscall failed with errno == EIO, rm issued no diagnostic about the I/O error. This looks good. How about the

bug#13028: inplace

2022-09-12 Thread Pádraig Brady
On 12/09/2022 09:07, Reuben Thomas wrote: On Mon, 16 May 2016 at 15:42, Pádraig Brady mailto:p...@draigbrady.com>> wrote: I just don't have the time at present to complete this. I did implement ACID file replacement using POSIX APIs a while ago in: https://github.com/

bug#33123: [PATCH] ls: --color: honor separate sequences for extension cases

2022-09-04 Thread Pádraig Brady
On 10/05/2022 15:21, Pádraig Brady wrote: On 10/05/2022 09:45, Mikael Magnusson wrote: Hi, In bug #9086 [1] there was a lot of good discussion about case insensitive matching for dircolors. This was all then summarily ignored in [2] which made the behaviour unconditional. This breaks coloring

bug#57237: b2sum does not support '-a' options found at https://www.blake2.net/

2022-08-16 Thread Pádraig Brady
On 16/08/2022 04:15, Robert E. Novak wrote: as a result, the Gnu version does not support blake2s (for smaller digests) and blakes2bp for higher performance on multicore systems. Yes, I know about Blake3, but there are many reasons to support older hash algorithms. The real problem is that you

bug#57132: bug report

2022-08-11 Thread Pádraig Brady
tag 57132 notabug close 57132 stop On 11/08/2022 04:05, lingzhiyuan (袁凌志) wrote: # tail -f log_error.log tail: unrecognized file system type 0x794c7630 for ‘log_error.log’. please report this to bug-coreutils@gnu.org. reverting to polling [cid:image001.jpg@01D8AD72.4C974A50] This was

bug#55401: date man page

2022-07-24 Thread Pádraig Brady
On 14/05/2022 01:42, Pádraig Brady wrote: On 13/05/2022 20:10, t0th wrote: Man page of date command should make explicit that -d and -r options are mutually exclusive. Right. More accurately, we might have a sentence to say that: "All options to specify the date to display are mut

bug#56710: ls vs. stat display of st_size

2022-07-24 Thread Pádraig Brady
On 24/07/2022 17:18, Paul Eggert wrote: On 7/24/22 01:48, Pádraig Brady wrote: Well ls(1) was explicitly changed to assuming only positive, citing POSIX (though I can't see it in POSIX myself): https://github.com/coreutils/coreutils/commit/67ba4ac01 I vaguely recall being involved

bug#56710: ls vs. stat display of st_size

2022-07-24 Thread Pádraig Brady
On 23/07/2022 21:07, Paul Eggert wrote: On 7/23/22 05:17, Pádraig Brady wrote: BTW I see we've code in cache_fstatat() that assumes st_size can't have such large values, which contradicts a bit. Good catch. I installed the first attached patch. > This is only a real considerat

bug#56710: ls vs. stat display of st_size

2022-07-23 Thread Pádraig Brady
On 22/07/2022 21:52, Paul Eggert wrote: Thanks for reporting that. I installed the attached. Playing devil's advocate, this takes the stance that st_size should always be treated as unsigned (given that stat(1) is a lower level util than ls(1)). This is only a real consideration for virtual

bug#56520: Security vulnerabilities at coreutils version for CentOS 7.9

2022-07-12 Thread Pádraig Brady
On 12/07/2022 13:43, Meirav Rath via GNU coreutils Bug Reports wrote: Hello, My name is Meirav Rath, I'm a software developer and security champion at Imperva. As part of our effort to map security risks in our products I've been scanning our 3rd party rpms for vulnerabilities. It looks like

bug#56391: `cp --reflink=always` creates empty file on failure

2022-07-07 Thread Pádraig Brady
forcemerge 56391 56392 close 56391 stop On 06/07/2022 20:48, Paul Eggert wrote: On 7/6/22 06:17, Pádraig Brady wrote: This will usually work, but there are cases where this may lose data, as previously discussed at: https://bugzilla.redhat.com/show_bug.cgi?id=921708 http://lists.gnu.org

bug#56391: `cp --reflink=always` creates empty file on failure

2022-07-06 Thread Pádraig Brady
On 05/07/2022 16:04, Paul Eggert wrote: Thanks for reporting that. I installed the attached patch. This will usually work, but there are cases where this may lose data, as previously discussed at: https://bugzilla.redhat.com/show_bug.cgi?id=921708

bug#55748: df: wrong column is checked in condition in total-verify.sh

2022-06-01 Thread Pádraig Brady
tag 55748 notabug close 55748 stop On 01/06/2022 09:01, Daniel Hofstetter wrote: Hi, While looking at https://github.com/coreutils/coreutils/blob/master/tests/df/total-verify.sh I noticed the following lines and I think "$5" in the last line (line 38 in the source code) should be "$6" because

bug#55724: cp --reflink=always failing when --reflink=auto reflinks successfully on OpenZFS

2022-05-30 Thread Pádraig Brady
On 30/05/2022 10:13, Rich wrote: Hi! So, OpenZFS is adding reflink support Soon(tm), including across filesystems on a pool, which is nice. Unfortunately, Linux's VFS returns EXDEV for trying FICLONE or FICLONERANGE (but not copy_file_range) cross-filesystem before you ever ask the

bug#55622: Bug in sort with keys and reverse, and version-sort and reverse

2022-05-25 Thread Pádraig Brady
On 25/05/2022 03:00, Larry Ploetz wrote: I think I've found a bug in sort (git branch master). The --reverse flag seems to be ignored when --keys are supplied. larryp-MBP:bin larry$ ./sort --version sort (GNU coreutils) 9.1.17-a351f Copyright (C) 2022 Free Software Foundation,

bug#55401: date man page

2022-05-13 Thread Pádraig Brady
On 13/05/2022 20:10, t0th wrote: Man page of date command should make explicit that -d and -r options are mutually exclusive. Right. More accurately, we might have a sentence to say that: "All options to specify the date to display are mutually exclusive. I.e.: --date, --file, --reference,

bug#33123: ls: add case-sensitive --color option

2022-05-10 Thread Pádraig Brady
On 10/05/2022 09:45, Mikael Magnusson wrote: Hi, In bug #9086 [1] there was a lot of good discussion about case insensitive matching for dircolors. This was all then summarily ignored in [2] which made the behaviour unconditional. This breaks coloring of uppercase files that should have a

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

2022-05-09 Thread Pádraig Brady
On 08/05/2022 21:19, Christoph Anton Mitterer wrote: Hey. Is this still being considered? Yes it still does make sense, especially as sha1 becomes less popular over time, in which case the extra processing would matter less. thanks, Pádraig

bug#55325: (sha|md5)*sum on UNIX should default to binary mode

2022-05-09 Thread Pádraig Brady
tag 55325 wontfix close 55325 stop On 08/05/2022 21:18, Christoph Anton Mitterer wrote: Hey. Since on UNIX/Linux it is effectively always binary mode, shouldn't the (sha|md5)*sum tools default to that, and especially also generate output with the "*" flag set? Well they do default to binary

bug#55304: build: INSTALL file is missing from .tar.gz snapshots

2022-05-07 Thread Pádraig Brady
tag 55304 notabug close 55304 stop On 07/05/2022 20:10, dg1727 via GNU coreutils Bug Reports wrote: In the following snapshot: http://git.savannah.gnu.org/cgit/coreutils.git/snapshot/coreutils-9.1.tar.gz ... the file README says the following a few paragraphs from the top: If this file came

bug#55261: file:// links geneated by --hyperlink

2022-05-05 Thread Pádraig Brady
On 04/05/2022 14:27, Stephen Eglen wrote: hi, With ls (GNU coreutils) 9.0 if I generate a hyperlink e.g.: $ ls --hyperlink /etc/anacrontab it generates the following filename (after removing the markup) file://light/etc/anacrontab where 'light' is the name of my laptop (running arch linux).

bug#55212: GNU Linux "sort -g" can hang indefinitely when run on standard input if NaNs are involved

2022-05-02 Thread Pádraig Brady
On 02/05/2022 07:03, Paul Eggert wrote: Thanks for the bug report. This bug is entertaining, as it comes from GCC now being so smart that it optimizes away a memset that cleared padding bits. We added the memset in coreutils 8.14 (2011) to try to fix the sort -g infinite loop bug (introduced in

bug#55183: date

2022-04-29 Thread Pádraig Brady
tag 55183 notabug close 55183 stop On 29/04/2022 13:59, danilopereira82--- via GNU coreutils Bug Reports wrote: %r has a space at the end that makes me insanely angry fix it What's happening is there is no "am_pm" item defined for your locale. Running this with a locale that does define it,

bug#55023: Issue with CP empty folder after y2038 on 32-bits Kernel

2022-04-29 Thread Pádraig Brady
On 29/04/2022 00:56, Paul Eggert wrote: On 4/27/22 09:42, Pádraig Brady wrote: Marking this as done in the coreutils bug tracker, now that this is being tracked in glibc. This could also be worked around Gnulib for the benefit of 32-bit apps running with unpatched glibc 2.34 and 2.35

bug#55023: Issue with CP empty folder after y2038 on 32-bits Kernel

2022-04-27 Thread Pádraig Brady
Marking this as done in the coreutils bug tracker, now that this is being tracked in glibc. thank you! On 27/04/2022 13:46, Adhemerval Zanella wrote: On 21/04/2022 14:36, Pádraig Brady wrote: That suggests the kernel (statx) returns fine, but glibc's fstatat64 is returning the EOVERFLOW

bug#55029: Simple backup swaps source and destination files

2022-04-23 Thread Pádraig Brady
On 21/04/2022 03:53, Paul Eggert wrote: On 4/19/22 16:05, Steve Ward wrote: When doing mv or cp with --backup=simple, if an existing file in DIRECTORY has the same name as SOURCE, the files appear to be swapped instead of an in-place backup of the original file in DIRECTORY being made. Thanks

bug#55023: Issue with CP empty folder after y2038 on 32-bits Kernel

2022-04-21 Thread Pádraig Brady
On 21/04/2022 18:41, Adhemerval Zanella wrote: On 21/04/2022 12:25, Pádraig Brady wrote: On 21/04/2022 15:53, Arnaud Panaïotis wrote: On 21/04/2022 14:36, Pádraig Brady wrote: On 19/04/2022 16:01, Arnaud Panaïotis wrote: On 19/04/2022 16:00, Pádraig Brady wrote: On 19/04/2022 08:47

bug#55023: Issue with CP empty folder after y2038 on 32-bits Kernel

2022-04-21 Thread Pádraig Brady
On 21/04/2022 15:53, Arnaud Panaïotis wrote: On 21/04/2022 14:36, Pádraig Brady wrote: On 19/04/2022 16:01, Arnaud Panaïotis wrote: On 19/04/2022 16:00, Pádraig Brady wrote: On 19/04/2022 08:47, Arnaud Panaïotis wrote: Hello, I did not received any feedback from this request right now

bug#55023: Issue with CP empty folder after y2038 on 32-bits Kernel

2022-04-21 Thread Pádraig Brady
On 19/04/2022 16:01, Arnaud Panaïotis wrote: On 19/04/2022 16:00, Pádraig Brady wrote: On 19/04/2022 08:47, Arnaud Panaïotis wrote: Hello, I did not received any feedback from this request right now. Have you made any progress on this subject ? Please let me know the progress

bug#55023: Issue with CP empty folder after y2038 on 32-bits Kernel

2022-04-19 Thread Pádraig Brady
On 19/04/2022 08:47, Arnaud Panaïotis wrote: Hello, I did not received any feedback from this request right now. Have you made any progress on this subject ? Please let me know the progress for this, or contact me for additional information if needed. I'd like to have a ticket link to follow

bug#50889: Please improve the documentation for install --compare (-C)

2022-04-09 Thread Pádraig Brady
On 29/09/2021 12:09, Ian Cross via GNU coreutils Bug Reports wrote: Hi, A while back a request was made to improve the documentation of the `install --compare` cmd: https://lists.gnu.org/archive/html/bug-coreutils/2009-09/msg00029.html It seems the wording in `coreutils.texi` has been updated

bug#54521: [PATCH] dircolors: colorize backup files with bright black

2022-04-03 Thread Pádraig Brady
On 23/03/2022 23:53, Pádraig Brady wrote: On 22/03/2022 18:24, Ville Skyttä wrote: Useful as it makes them stand out less than non-backup files. --- src/dircolors.hin | 19 +++ 1 file changed, 19 insertions(+) diff --git a/src/dircolors.hin b/src/dircolors.hin index

bug#54681: timeout: Program called by timeout cannot interact with tty stdin when timeout is called by exec()

2022-04-02 Thread Pádraig Brady
tag 54681 notabug close 54681 stop On 02/04/2022 11:22, Zhaofeng Yang wrote: Hi GNU Team, I found that program called by timeout cannot interact with tty stdin when timeout is called by exec(). A simplest example is `timeout 10 timeout 5 cat`. cat cannot read input from tty stdin. I also

bug#54625: Why do I need to specify `-o auto` for join's `-e` option to work?

2022-03-29 Thread Pádraig Brady
On 29/03/2022 09:07, Iago-lito wrote: Hello,     This is a follow-up to this (yet) unanswered post on SE U: https://unix.stackexchange.com/q/696259/87656, which I'm cross-posting here. Don't hesitate to fire if it's the wrong place. With the following two simple files: |a.txt| |1 a 2 b 5 c

bug#54521: [PATCH] dircolors: colorize backup files with bright black

2022-03-23 Thread Pádraig Brady
On 22/03/2022 18:24, Ville Skyttä wrote: Useful as it makes them stand out less than non-backup files. --- src/dircolors.hin | 19 +++ 1 file changed, 19 insertions(+) diff --git a/src/dircolors.hin b/src/dircolors.hin index 673835201..6dc5a2d74 100644 --- a/src/dircolors.hin

bug#54388: printf doesn't handle multi-byte values

2022-03-18 Thread Pádraig Brady
On 18/03/2022 14:59, Pádraig Brady wrote: The attached should fix this up. The following should make this more efficient for the normal unibyte case, as one can't have NUL chars in any multi-byte encodings. - if (MB_CUR_MAX >

bug#54388: printf doesn't handle multi-byte values

2022-03-18 Thread Pádraig Brady
On 14/03/2022 15:38, Pádraig Brady wrote: On 14/03/2022 03:27, Christoph Anton Mitterer wrote: Hey Pádraig. I just wanted to ask, whether the following could be a bug in printf: POSIX says[0], that e.g.: printf '%d\n' \"3 should give the numeric value of the char

bug#54388: printf doesn't handle multi-byte values

2022-03-14 Thread Pádraig Brady
On 14/03/2022 03:27, Christoph Anton Mitterer wrote: Hey Pádraig. I just wanted to ask, whether the following could be a bug in printf: POSIX says[0], that e.g.: printf '%d\n' \"3 should give the numeric value of the character, and that "in a locale with multi-byte characters, the value of

bug#54338: enhancement (documentation): explain permission tests in "test"

2022-03-11 Thread Pádraig Brady
On 11/03/2022 10:42, Ulrich Windl wrote: I noticed that "test -r file" returns success when called as root for a file with these permissions: "--w---" (see also https://stackoverflow.com/q/71435657/6607497) The documentation simply states: ‘-r FILE’ True if FILE exists and read

bug#54287: [PATCH] Fix stat command triggering automount.

2022-03-07 Thread Pádraig Brady
New stat patch attached to apply AT_NO_AUTOMOUNT unless --cached=never is specified. See https://bugs.gnu.org/54286 for more general discussion. Marking this as done. cheers, PádraigFrom 3fddd0f4eb0eb9b47294f951195233e1c5f12e72 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?P=C3=A1draig=20Brady?=

bug#54286: [PATCH] Fix ls -l triggering automounts.

2022-03-07 Thread Pádraig Brady
Updated patch for ls attached as per discussion. Added a NEWS entry.From e4c7fccc0c057a772b6be3f002003ba005cc89d7 Mon Sep 17 00:00:00 2001 From: Rohan Sable Date: Mon, 7 Mar 2022 14:14:13 + Subject: [PATCH] ls: avoid triggering automounts statx() has different defaults wrt automounting

bug#54286: [PATCH] fcntl-h: add AT_NO_AUTOMOUNT

2022-03-07 Thread Pádraig Brady
/ChangeLog @@ -1,3 +1,9 @@ +2022-03-07 Pádraig Brady + + fcntl-h: add AT_NO_AUTOMOUNT + * lib/fcntl.in.h: Define AT_NO_AUTOMOUNT to 0 where not defined. + This is available on Linux since 2.6.38. + 2022-03-01 Paul Eggert Create lib/Makefile.am after gnulib-comp.m4 diff

bug#54286: [PATCH] Fix ls -l triggering automounts.

2022-03-07 Thread Pádraig Brady
On 07/03/2022 07:54, Rohan Sable wrote: Running ls -l on a path that has autofs mounts, triggers a mount or in case of unmountable shares, triggers errors : ~~~ [root@rsablerhel85 mnt2]# ll ls: cannot access 'testshare2': No such file or directory < Error total 0 drwxrwxrwx. 3 1000 1000

bug#54189: [PATCH] dircolors: add hterm

2022-02-27 Thread Pádraig Brady
On 27/02/2022 21:08, Mike Frysinger wrote: * src/dircolors.hin: Add hterm*. --- src/dircolors.hin | 1 + 1 file changed, 1 insertion(+) diff --git a/src/dircolors.hin b/src/dircolors.hin index 673835201311..fa01192bf7e5 100644 --- a/src/dircolors.hin +++ b/src/dircolors.hin @@ -23,6 +23,7 @@

bug#45648: `dd` seek/skip which way is up?

2022-02-24 Thread Pádraig Brady
On 22/02/2022 17:12, Paul Eggert wrote: On 1/4/21 20:08, Paul Eggert wrote: On 1/4/21 7:44 PM, Bela Lubkin wrote: TLDR: *huge* existing presence of 'iseek' and 'oseek'; most OSes document them as pure synonyms for 'skip' and 'seek'. Thanks for doing all that research. It's compelling, and I

bug#54124: fmt inserts garbage in certain cases?

2022-02-23 Thread Pádraig Brady
On 23/02/2022 17:55, Pádraig Brady wrote: I think isspace(x85) returning true on macOS is a bug, Bug is a bit of a strong word here. A digression into why 0x85 is being treated specially here. Note Cyrillic kha "х" is encoded in UTF-8 as: $ printf '\u0445' | od -tx1 000 d1

bug#54124: fmt inserts garbage in certain cases?

2022-02-23 Thread Pádraig Brady
On 23/02/2022 10:58, JD wrote: Hi! I have fmt from coreutils 8.32.1 installed via MacPorts. If I run the following command: `echo х х х х х х х х х х х х х х х х х х х х х х х х х х | gfmt -sw 10` (which is just echoing 26 Cyrillic 'х' ('kha') letters), I get the following results:

bug#54112: dd seek_bytes etc. is confusing

2022-02-22 Thread Pádraig Brady
On 22/02/2022 17:03, Paul Eggert wrote: While looking into Bug#45648 I noticed that the GNU extensions count_bytes, seek_bytes, and skip_bytes are confusing, and the proposed fix to bug#45648 would make them even more confusing. To fix this confusion, we should deprecate these options, and

bug#53977: Improve markup in man pages

2022-02-14 Thread Pádraig Brady
On 14/02/2022 13:52, Mario Blättermann wrote: Hello Pádraig, Am Mo., 14. Feb. 2022 um 13:15 Uhr schrieb Pádraig Brady : On 13/02/2022 13:19, Mario Blättermann wrote: Hello, the SEE ALSO sections in the man pages contain links which will be pulled in from *.x files by help2man. While

bug#53977: Improve markup in man pages

2022-02-14 Thread Pádraig Brady
On 13/02/2022 13:19, Mario Blättermann wrote: Hello, the SEE ALSO sections in the man pages contain links which will be pulled in from *.x files by help2man. While help2man evaluates the Groff markup from --help and --version output, it doesn't bother with the markup in the *.x files. See the

bug#49239: Unexpected results with sort -V

2022-02-13 Thread Pádraig Brady
On 13/02/2022 05:31, Paul Eggert wrote: On 6/28/21 10:54, Kamil Dudka wrote: You are right. The matching algorithm was not implemented correctly and the patch you attached fixes it. I looked into Bug#49239 and found some more places where the documentation disagreed with the code. I

bug#53631: coreutils id(1) incorrect behavior

2022-02-12 Thread Pádraig Brady
On 04/02/2022 22:59, Paul Eggert wrote: Thanks for the bug report. I installed the attached patch, which I hope fixes things for you, and am boldly closing the bug report. This fix depends on the latest lib/userspec.c from Gnulib; see .

bug#53946: Errors in man pages of GNU_coreutils

2022-02-12 Thread Pádraig Brady
On 12/02/2022 05:57, Helge Kreutzmann wrote: Dear coreutils maintainer, the manpage-l10n project maintains a large number of translations of man pages both from a large variety of sources (including coreutils) as well for a large variety of target languages. During their work translators notice

bug#53574: csplit: help document: +/- is not required before OFFSET

2022-01-27 Thread Pádraig Brady
On 27/01/2022 07:28, Jun-T wrote: 'csplit --help' (and 'man csplit') says: A line OFFSET is a required '+' or '-' followed by a positive integer. But I think the '+' or '-' is optional, not required. 'info csplit' just says: The optional OFFSET is an integer I think this is correct

bug#53400: base64: decode Base64URL

2022-01-21 Thread Pádraig Brady
On 20/01/2022 21:31, Sergey Ponomarev wrote: Package: coreutils Currently the base64 util can't parse base64 url safe. RFC 3548 Base 64 Encoding with URL and Filename Safe Alphabet https://datatracker.ietf.org/doc/html/rfc3548#page-6 But basically this is the same encoding: just two symbols

bug#53262: chmod 9.0 failing, where 8.29 succeeds - but no error message

2022-01-15 Thread Pádraig Brady
On 15/01/2022 01:09, Paul Eggert wrote: Thanks for reporting that. This is a duplicate of bug#50784[1], which was fixed[2] in September. Perhaps we should generate a new Coreutils soon, since this bug has been reported three times now. [1]: https://bugs.gnu.org/50784 [2]:

bug#53025: Encouragement to go back to *dis*abled quotation marks in ls output as *default* behavior

2022-01-05 Thread Pádraig Brady
On 05/01/2022 08:44, Joerg M. Sigle wrote: Dear coreutils developers Thank you very much for your efferts in trying to provide and maintain fine tools that help millions or billions of users every day. I'm one who appreciates that (and I try to do something similar as well). Still, sometimes

bug#52800: [PATCH] maint: fix prctl arguments

2021-12-26 Thread Pádraig Brady
On 26/12/2021 05:17, Max Filippov wrote: When configured with --enable-single-binary tools issue incorrect prctl: prctl(PR_SET_KEEPCAPS, 1071091381) = -1 EINVAL (Invalid argument) PR_SET_MM_ARG_START is not a prctl 'option' parameter, it's 'arg2' parameter for the option PR_SET_MM. It

bug#52343: Sentry kafka bug

2021-12-08 Thread Pádraig Brady
tag 52343 notabug close 52343 stop On 07/12/2021 03:13, 许慧良 wrote: tail: unrecognized file system type 0x794c7630 for ‘kafkaServer-gc.log.0.current’. please report this to bug-coreutils@gnu.org. reverting to polling 2021-12-07T03:03:51Z [relay_server::endpoints::common] ERROR: error handling

bug#52077: tail: a case where -n is not taken as implicit

2021-11-24 Thread Pádraig Brady
tag 52077 notabug close 52077 stop On 24/11/2021 07:38, Shehu Dikko wrote: Package: coreutils Version: 9.0 Do please take a look at this example: % printf '%s\n' just three lines | tee >f1 f2 % tail -n1 f1 lines % tail -n1 f* ==> f1 <== lines ==> f2 <== lines % tail -1 f1 lines % tail -1 f*

bug#51857: cross-filesystem copying broken on macOS with coreutils >= 9.0

2021-11-15 Thread Pádraig Brady
On 15/11/2021 18:37, Sudhip Nashi via GNU coreutils Bug Reports wrote: On Nov 15, 2021, at 11:33, Paul Eggert wrote: Is the source file on a ZFS file system by any chance? See my lseek comment below. On 11/15/21 07:48, Cameron Katri via GNU coreutils Bug Reports wrote:

bug#51857: cross-filesystem copying broken on macOS with coreutils >= 9.0

2021-11-15 Thread Pádraig Brady
On 15/11/2021 04:02, Sudhip Nashi via GNU coreutils Bug Reports wrote: Hello, Cross-filesystem copying seems to have been broken in the latest coreutils release on macOS. Running a command like ‘cp /usr/bin/clear /tmp/test’ appears to return successfully, but if one analyzes /tmp/test, it’s

bug#51793: FAIL: tests/misc/env-signal-handler

2021-11-13 Thread Pádraig Brady
On 13/11/2021 09:46, Andreas Schwab wrote: On Nov 12 2021, Pádraig Brady wrote: I've never seen this, and I can't see the race. There is an obvious race: if env needs more than .1 seconds to set the SIGINT handler. Indeed. That fits the pattern where we need a certain delay to pass. So we

bug#51793: FAIL: tests/misc/env-signal-handler

2021-11-12 Thread Pádraig Brady
On 12/11/2021 19:25, Andreas Schwab wrote: --- exp-err6 2021-11-11 22:58:04.360716802 + +++ err6 2021-11-11 22:58:04.752716821 + @@ -1,2 +1 @@ timeout: sending signal INT to command 'env' -timeout: sending signal KILL to command 'env' The above is for the previous command not

bug#51792: coreutils - csplit - feature request

2021-11-12 Thread Pádraig Brady
On 12/11/2021 17:05, Rodolfo Aramayo wrote: Dear Coreutils Maintainers, First, thank you for your work. I use coreutils daily both for my research and teaching. It is a great set of tools. Second, I recently needed to extract Coding Sequences information from a GenBank file. GenBank files are

bug#51433: cp 9.0 sometimes fails with SEEK_DATA/SEEK_HOLE

2021-11-03 Thread Pádraig Brady
On 27/10/2021 11:00, Janne Heß wrote: Hi everyone, I packaged coreutils 9.0 for NixOS and we found breakages that seemed to be very random during builds of packages that use the updated coreutils in their build process. It's really hard to tell the main cause but it seems like the issues are

bug#51569: tail -f reports unrecognized file system type

2021-11-02 Thread Pádraig Brady
tag 51569 notabug close 51569 stop On 02/11/2021 16:01, Tom Barringer wrote: Received this error: tail: unrecognized file system type 0x53464846 for ‘ads0.exp’. please report this to bug-coreutils@gnu.org. reverting to polling Environment: Win10 with all updates Using Windows Subsystem for

bug#51433: cp 9.0 sometimes fails with SEEK_DATA/SEEK_HOLE

2021-11-01 Thread Pádraig Brady
On 01/11/2021 05:52, Paul Eggert wrote: On 10/31/21 09:13, Pádraig Brady wrote: The attached uses statfs()->f_type which is usually available, to avoid using SEEK_DATA on ZFS.  This should be fairly lightweight I think, and only used for files that might be sparse. Couldn't we be even laz

bug#51011: [PATCH] sort: --debug: add warnings about radix and grouping chars

2021-10-31 Thread Pádraig Brady
On 11/10/2021 02:54, Pádraig Brady wrote: On 11/10/2021 00:34, Paul Eggert wrote: The warnings look good, except that this one:   $ printf '1.0\n0.9\n' | sort -s -k1,1g --debug   sort: numbers use ‘.’ as a decimal point in this locale   0.9   ___   1.0   ___ seems overkill

bug#51433: cp 9.0 sometimes fails with SEEK_DATA/SEEK_HOLE

2021-10-31 Thread Pádraig Brady
On 30/10/2021 03:04, Paul Eggert wrote: On 10/28/21 13:59, Pádraig Brady wrote: I wonder after getting a SEEK_DATA ENXIO, might we correlate we really are at end of file by checking SEEK_HOLE also returns ENXIO? Wouldn't SEEK_HOLE return the current offset, instead of ENXIO

bug#51433: cp 9.0 sometimes fails with SEEK_DATA/SEEK_HOLE

2021-10-31 Thread Pádraig Brady
On 28/10/2021 20:11, Paul Eggert wrote: On 10/28/21 06:54, Pádraig Brady wrote: Further debugging from Nix folks suggest ZFS was in consideration always, as invalid artifacts were written to a central cache from ZFS backed hosts. So we should at least change the comment in the patch to only

bug#51433: cp 9.0 sometimes fails with SEEK_DATA/SEEK_HOLE

2021-10-30 Thread Pádraig Brady
On 30/10/2021 02:24, Paul Eggert wrote: On 10/28/21 12:11, Paul Eggert wrote: Wait - lseek returns a number less than -1?! We could easily check for that FreeBSD bug, perhaps as an independent patch; this shouldn't require any extra syscalls. I installed the attached patch to do this. This

bug#51345:

2021-10-29 Thread Pádraig Brady
On 28/10/2021 22:59, Sworddragon wrote: Despite I'm not using Linux as main system anymore and wanted to avoid getting into too much work I found some time to do some tests as this issue bugs me just too much. You could try running the following immediately after, to see if it also returns

bug#51345:

2021-10-29 Thread Pádraig Brady
On 28/10/2021 22:59, Sworddragon wrote: Despite I'm not using Linux as main system anymore and wanted to avoid getting into too much work I found some time to do some tests as this issue bugs me just too much. You could try running the following immediately after, to see if it also returns

bug#51433: cp 9.0 sometimes fails with SEEK_DATA/SEEK_HOLE

2021-10-28 Thread Pádraig Brady
On 28/10/2021 20:11, Paul Eggert wrote: On 10/28/21 06:54, Pádraig Brady wrote: Further debugging from Nix folks suggest ZFS was in consideration always, as invalid artifacts were written to a central cache from ZFS backed hosts. So we should at least change the comment in the patch to only

bug#51433: cp 9.0 sometimes fails with SEEK_DATA/SEEK_HOLE

2021-10-28 Thread Pádraig Brady
On 28/10/2021 08:56, Paul Eggert wrote: On 10/27/21 03:00, Janne Heß wrote: Building another package (peertube) on x86_64-linux on ext4 also fails with strange errors in the test suite, something about "Error: The service is no longer running". This does not happen when the mentioned

bug#51433: cp 9.0 sometimes fails with SEEK_DATA/SEEK_HOLE

2021-10-27 Thread Pádraig Brady
On 27/10/2021 11:00, Janne Heß wrote: Hi everyone, I packaged coreutils 9.0 for NixOS and we found breakages that seemed to be very random during builds of packages that use the updated coreutils in their build process. It's really hard to tell the main cause but it seems like the issues are

bug#51345: dd with conv=fsync sometimes returns when its writes are still cached

2021-10-23 Thread Pádraig Brady
On 23/10/2021 09:18, Sworddragon wrote: On Knoppix 9.1 with the Linux Kernel 5.10.10-64 x86_64 and GNU Coreutils 8.32 I wanted to overwrite my USB Thumb Drive a few times with random data via "dd if=/dev/random of=/dev/sdb bs=1M conv=fsync". While it usually takes ~2+ minutes to perform this

bug#51311: [PATCH] echo: update --help to document edge cases

2021-10-22 Thread Pádraig Brady
On 21/10/2021 21:54, Bernhard Voelker wrote: On 10/21/21 15:14, Florent Flament wrote: Pádraig Brady writes: +NOTE: printf(1) is a preferred alternative, with more standard option handling.\ I believe that it misses the point. It is still not clear that the echo command doesn't behave

bug#51311: [PATCH] echo: update --help to document edge cases

2021-10-21 Thread Pádraig Brady
On 20/10/2021 22:50, Florent Flament wrote: * src/echo.c (usage): Document edge cases when displaying arbitrary strings with the echo command. --- src/echo.c | 8 1 file changed, 8 insertions(+) diff --git a/src/echo.c b/src/echo.c index 18513398a..73b44660b 100644 --- a/src/echo.c

bug#51128: timeout --kill-after=0 seems to not send a kill 0s after the initial signal

2021-10-12 Thread Pádraig Brady
On 12/10/2021 02:21, Christoph Anton Mitterer wrote: Hey. One more thing on this, since I've just read through: https://www.gnu.org/software/coreutils/manual/html_node/timeout-invocation.html#timeout-invocation That does IMO *not* document the behaviour: --kill-after=duration says: This

bug#51135: timeout: --foreground causes exit status 124, even if KILL was used

2021-10-12 Thread Pádraig Brady
On 12/10/2021 02:55, Christoph Anton Mitterer wrote: Thinking again about this: Don't you think one looses quite something if, with --foreground, one cannot differ (via the exit status) between a timeout that allowed the program to clean up and one (when KILLing) that didn't? Even if the KILL

bug#51135: timeout: --foreground causes exit status 124, even if KILL was used

2021-10-11 Thread Pádraig Brady
On 11/10/2021 22:11, Christoph Anton Mitterer wrote: On Mon, 2021-10-11 at 22:04 +0100, Pádraig Brady wrote: +However if the @option{--foreground} option is specified then +@command{timeout} will not send any signals to its own process, +and so it will exit with one of the other exit status

bug#51135: timeout: --foreground causes exit status 124, even if KILL was used

2021-10-11 Thread Pádraig Brady
On 11/10/2021 19:01, Christoph Anton Mitterer wrote: Hey. This time I've also checked the 9.0 documentation (hopefully I wasn't just too blind). I noticed that whenever --foreground is used, timeout exits with a 124 status (instead of the documented 128+9) regardless of whether the KILL is

bug#51128: timeout --kill-after=0 seems to not send a kill 0s after the initial signal

2021-10-11 Thread Pádraig Brady
On 11/10/2021 16:59, Christoph Anton Mitterer wrote: On Mon, 2021-10-11 at 16:49 +0100, Pádraig Brady wrote: Well that wouldn't be that useful functionality, as why not just send a single kill signal in that case. Well with the same argumentation one could say that timeout 0 command doesn’t

bug#51128: timeout --kill-after=0 seems to not send a kill 0s after the initial signal

2021-10-11 Thread Pádraig Brady
tag 51128 notabug close 51128 stop On 11/10/2021 02:28, Christoph Anton Mitterer wrote: Hey. The timeout(1) manpage says: -k, --kill-after=DURATION also send a KILL signal if COMMAND is still running this long after the initial signal was sent My naive

bug#51011: [PATCH] sort: --debug: add warnings about radix and grouping chars

2021-10-10 Thread Pádraig Brady
On 11/10/2021 00:34, Paul Eggert wrote: The warnings look good, except that this one:   $ printf '1.0\n0.9\n' | sort -s -k1,1g --debug   sort: numbers use ‘.’ as a decimal point in this locale   0.9   ___   1.0   ___ seems overkill if we're in the C locale. Also, shouldn't

bug#51011: [PATCH] sort: --debug: add warnings about radix and grouping chars

2021-10-10 Thread Pádraig Brady
On 10/10/2021 22:20, Bernhard Voelker wrote: On 10/10/21 19:57, Pádraig Brady wrote: sort: numbers use ‘.’ as a decimal point in this locale What about adding the hint to that message that this an "ambiguity warning"? sort: ambiguity warning: numbers use ‘.’ as a dec

bug#51011: [PATCH] sort: --debug: add warnings about radix and grouping chars

2021-10-10 Thread Pádraig Brady
On 09/10/2021 23:29, Paul Eggert wrote: On 10/9/21 5:00 AM, Pádraig Brady wrote: On 09/10/2021 04:48, Paul Eggert wrote: 'sort' could determine the group sizes from the locale, and reject digit strings that are formatted improperly according to the group-size rules. (Not that I plan to write

bug#51011: [GNU sort] Numerical sort with delimiter may be broken (bug)

2021-10-09 Thread Pádraig Brady
On 09/10/2021 04:48, Paul Eggert wrote: On 10/8/21 7:32 PM, Pádraig Brady wrote: it's not a thousands separator, rather a grouping character, and groups can be in 2, 3, 4, and even 5. Sure, but 'sort' could determine the group sizes from the locale, and reject digit strings that are formatted

bug#51011: [GNU sort] Numerical sort with delimiter may be broken (bug)

2021-10-08 Thread Pádraig Brady
On 08/10/2021 21:48, Paul Eggert wrote: On 10/8/21 6:37 AM, Pádraig Brady wrote: The difference here is due to ',' being treated as a thousands sep, not a decimal point. Oh, thanks. Of course! I should have figured that out myself. It is unfortunate that "," is treated as a

bug#51011: [GNU sort] Numerical sort with delimiter may be broken (bug)

2021-10-08 Thread Pádraig Brady
On 04/10/2021 21:01, Paul Eggert wrote: On 10/4/21 08:58, Pádraig Brady wrote: The --debug option points out the issue:   $ printf '%s\n' 1,a 0,9 | sort --debug -nk1 -t ,   sort: key 1 is numeric and spans multiple fields   1,a   _   ___   0,9   ___   ___ As Juncheng points

bug#51011: [GNU sort] Numerical sort with delimiter may be broken (bug)

2021-10-04 Thread Pádraig Brady
tag 51011 notabug close 51011 stop On 04/10/2021 15:36, Juncheng Yang wrote: Hi coreutils developers, I have encountered a bug in GNU sort in which sort produces incorrect results when numerical sort with delimiters. For example, sort -nk1 -t , file cannot sort the a file with the

bug#50972: src/ls.c fails to build when __GNUC_PREREQ is not defined (e.g., OpenBSD)

2021-10-03 Thread Pádraig Brady
On 03/10/2021 03:07, Paul Eggert wrote: On 10/2/21 7:44 AM, Brian Callahan wrote: Once this fix is done, the rest of coreutils-9.0 builds and works OK. Thanks for letting us know, as it's been a while since I tried building coreutils on OpenBSD. I just now tried it on OpenBSD 6.9 and found

bug#50940: how df utility displays sizes - GB vs GiB

2021-10-01 Thread Pádraig Brady
On 01/10/2021 14:28, Danie de Jager wrote: Hi, The output from df -h and df -H is always G or M. Depending on who sends me usage stats I have to ask how the command was run to make sure I calculate usage correctly. Systems like Amazon EC2 use the explicit GiB suffix. Making it easier to know

bug#50797: Question about whether Korean translation can be applied into version 9.0 or not

2021-09-25 Thread Pádraig Brady
On 25/09/2021 07:45, Seong-ho Cho wrote: Many thanks in advance, I have submitted a brand-new Korean translation via translationproject.org and I also sent before for version 8.31.90 lately. our translation team did not manage the translation of coreutils before, due to huge changes of

bug#50791: Recursive chmod exit status in coreutils-9.0

2021-09-25 Thread Pádraig Brady
On 25/09/2021 07:07, Chris Webb wrote: Thanks for the analysis and patch. I've already pushed a very similar patch at: https://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=e8b56ebd5 Many thanks! With the above fix, do we also need something like @@ -300,7 +300,7 @@ process_file (FTS

bug#50791: Recursive chmod exit status in coreutils-9.0

2021-09-24 Thread Pádraig Brady
forcemerge 50791 50784 stop On 24/09/2021 22:16, Chris Webb wrote: Since bbb19b, chmod has started returning EXIT_FAILURE after skipping a symlink during a recursive change. This affects chmod in the newly released coreutils-9.0 vs the previous coreutils-8.32 and older versions: # mkdir t

bug#50784: coreutils 9.0 sometimes gets spurious failures in chmod -R

2021-09-24 Thread Pádraig Brady
On 24/09/2021 22:42, Daniel Schepler wrote: On Fri, Sep 24, 2021 at 1:02 PM Pádraig Brady wrote: Could you try with the following untested diff: Tested equivalent patch is attached. Yes, with chmod-fix-symlink-exit.patch applied and the resulting packages installed for testing, the issue

bug#50784: coreutils 9.0 sometimes gets spurious failures in chmod -R

2021-09-24 Thread Pádraig Brady
On 24/09/2021 20:29, Pádraig Brady wrote: On 24/09/2021 19:21, Daniel Schepler wrote: After I upgraded my system (locally built) to coreutils 9.0, I noticed that my lightly modified sbuild started getting build failures when it tries to run "chmod -R g+w /<>" (as root) in

  1   2   3   4   5   6   7   8   9   10   >