bug#75916: Making ls(1)'s --format clearer

2025-01-28 Thread Pádraig Brady
On 28/01/2025 20:00, Samuel Thibault wrote: Hello, ls(1) says this about --format: --format=WORD across -x, commas -m, horizontal -x, long -l, single-column -1, verbose -l, vertical -C It was not clear at all for my students (and not for me either, actually), that it's the wo

bug#75763: is the "note " particle in sort.c needed?

2025-01-22 Thread Pádraig Brady
On 22/01/2025 15:31, Benno Schulenberg wrote: Hi, In src/sort.c there is this piece of code: error (0, 0, _("%snumbers use %s as a decimal point in this locale"), tab == decimal_point ? "" : _("note "), quote (((char []) {decimal_point, 0}))

bug#75649: dd: report base 1024 for bytes per second

2025-01-21 Thread Pádraig Brady
On 18/01/2025 14:17, Chris Ely wrote: Hello, human options would be better if it included base 1024 by default, the code can turn that bit off where it doesn't want it (the si transfer status value, should be the only place). I'm not sure about that. Generally data transfer rates (network, usb

bug#75616: rm-readdir-fail test fails on Alpine Linux

2025-01-16 Thread Pádraig Brady
On 16/01/2025 22:26, Bruno Haible via GNU coreutils Bug Reports wrote: Testing a current coreutils with a current gnulib on Alpine Linux 3.20, I see 1 test failure: FAIL: tests/rm/rm-readdir-fail Find attached the log file. Is that with the latest snapshot? I.e. https://www.pixelbeat.org/cu/c

bug#75613: tail-c test fails on CentOS 6

2025-01-16 Thread Pádraig Brady
On 16/01/2025 21:16, Paul Eggert wrote: On 2025-01-16 13:11, Pádraig Brady wrote: I propose we at least adjust the test to skip failures on older kernels, as in the attached. Thanks, that looks good to me too. Pushed. Marking this as done. cheers, Pádraig

bug#75614: Fix FTBFS on CentOS 8 and CentOS 8 Stream

2025-01-16 Thread Pádraig Brady
On 16/01/2025 21:14, Bruno Haible via GNU coreutils Bug Reports wrote: Testing a current coreutils with a current gnulib on CentOS 8 and CentOS 8 Stream, I see the same compilation error on both: CC src/libcksum_avx512_a-cksum_avx512.o ../src/cksum_avx512.c: In function 'cksum_avx512':

bug#75613: tail-c test fails on CentOS 6

2025-01-16 Thread Pádraig Brady
On 16/01/2025 20:19, Paul Eggert wrote: On 2025-01-16 11:50, Bruno Haible via GNU coreutils Bug Reports wrote: $ src/timeout --verbose 1 src/tail -c 4096 /dev/urandom timeout: sending signal TERM to command 'src/tail' $ echo $? 124 Wikipedia[1] says that CentOS versions through

bug#75604: bootstrap ignores --copy option

2025-01-16 Thread Pádraig Brady
On 16/01/2025 15:15, Pádraig Brady wrote: On 16/01/2025 14:48, Bruno Haible via GNU coreutils Bug Reports wrote: Hi, I want to test a current coreutils from git with clang's UBSAN. For this, I need to apply a patch to lib/linebuffer.c and lib/mpsort.c locally. For this, it is not suitab

bug#75604: bootstrap ignores --copy option

2025-01-16 Thread Pádraig Brady
On 16/01/2025 14:48, Bruno Haible via GNU coreutils Bug Reports wrote: Hi, I want to test a current coreutils from git with clang's UBSAN. For this, I need to apply a patch to lib/linebuffer.c and lib/mpsort.c locally. For this, it is not suitable if 'bootstrap' creates these files as symbolic l

bug#75532: [PATCH 0/1] Proposed new feature for the shred command

2025-01-13 Thread Pádraig Brady
tag 75532 notabug close 75532 stop details below... On 12/01/2025 18:50, TheJostler wrote: From: Josjuar Lister Hello Coreutils team, My name is Josjuar Lister, I am a 28 year old free-lance software developer from the United Kingdom. My main work though is System Administration and Securit

bug#74692: ls -la unexpected output on NFS shares, possibly due to listxattr in gnulib

2025-01-11 Thread Pádraig Brady
On 11/01/2025 13:44, Pádraig Brady wrote: On 11/01/2025 08:37, Paul Eggert wrote: On 2025-01-10 06:48, Pádraig Brady wrote: With the previously discussed ls patch included, we also suppress the error (while indicating the obtainable security context): $ src/ls -l /mnt/nfs total 0 --w

bug#74692: ls -la unexpected output on NFS shares, possibly due to listxattr in gnulib

2025-01-11 Thread Pádraig Brady
On 11/01/2025 08:37, Paul Eggert wrote: On 2025-01-10 06:48, Pádraig Brady wrote: With the previously discussed ls patch included, we also suppress the error (while indicating the obtainable security context): $ src/ls -l /mnt/nfs total 0 --w---. 1 padraig padraig 0 Jan  8 20:42 file I&#x

bug#74692: ls -la unexpected output on NFS shares, possibly due to listxattr in gnulib

2025-01-10 Thread Pádraig Brady
On 10/01/2025 04:46, Paul Eggert wrote: On 2025-01-09 05:29, Pádraig Brady wrote: over NFS with unreadable files you can GET the security.selinux xattr, but you can't LIST any xattrs: Ouch again Also there was a change since coreutils v9.5 where we don't call the GET, Ye

bug#74692: ls -la unexpected output on NFS shares, possibly due to listxattr in gnulib

2025-01-09 Thread Pádraig Brady
I've CC'd linux-nfs in case anyone there has some insight as to why listxattr() is more restrictive on NFS than locally, returning EACCES for files without read access. Details below... On 09/01/2025 04:55, Paul Eggert wrote: Thanks, but is this part of the change needed? + else if (f->acl_ty

bug#74692: ls -la unexpected output on NFS shares, possibly due to listxattr in gnulib

2025-01-08 Thread Pádraig Brady
On 08/01/2025 19:41, Paul Eggert wrote: On 2025-01-08 06:24, Pádraig Brady wrote: The EACCES is returned from both llistxattr and listxattr. Is flistxattr the same? You need read permission to get xattrs on local or nfs. Isn't it more complicated than that, for local file systems? H

bug#74692: ls -la unexpected output on NFS shares, possibly due to listxattr in gnulib

2025-01-08 Thread Pádraig Brady
On 05/12/2024 21:56, Paul Eggert wrote: On 2024-12-04 09:10, Ioanna Alifieraki wrote: When ls -la is run on NFS shares, get_aclinfo() in gnulib is eventually invoked. This calls listxattr, which, as expected, returns -1 and sets errno when the user lacks permissions for a directory. That's not

bug#70887: In coreutils 9.5, "cp" command does not honor "--interactive" option

2025-01-06 Thread Pádraig Brady
On 12/05/2024 21:31, Pádraig Brady wrote: On 12/05/2024 16:06, Paul Eggert wrote: On 2024-05-12 04:49, Pádraig Brady wrote: @@ -1151,7 +1151,8 @@ main (int argc, char **argv) { /* Default cp operation. */ x.update = false

bug#75011: Problem with libstdbuf.so

2024-12-21 Thread Pádraig Brady
tag 75011 notabug close 75011 stop On 20/12/2024 10:11, Emiliano Ezequiel Parenti wrote: I mean there is a problem with libstdbuf.so, because operating systems put that file in the libexec folder, and that folder should only contain executables, not libraries. I would like this to change, for s

bug#74428: tests/printf/printf-cov failure on macOS

2024-12-06 Thread Pádraig Brady
On 06/12/2024 07:13, Bernhard Voelker wrote: On 11/19/24 19:31, Pádraig Brady wrote: OK I've adjusted our test to use \u00032 instead, The bug report was talking about Macos only, but now I'm seeing this failure also on openSUSE for Leap 16.0 on x86_64 [1] and aarch64 [2]. Using

bug#74653: tail --follow=name doesn't exit when using inotify and the file is moved

2024-12-05 Thread Pádraig Brady
On 04/12/2024 11:55, Pádraig Brady wrote: On 02/12/2024 16:19, Göran Uddeborg wrote: When using "tail --follow=name", but without "--retry", on a file supporting inotify, the command doesn't finish if the file is moved to a new name. Repeat this way on a local filesyst

bug#74653: tail --follow=name doesn't exit when using inotify and the file is moved

2024-12-04 Thread Pádraig Brady
On 02/12/2024 16:19, Göran Uddeborg wrote: When using "tail --follow=name", but without "--retry", on a file supporting inotify, the command doesn't finish if the file is moved to a new name. Repeat this way on a local filesystem: echo apa > apa tail --follow=name apa & mv apa be

bug#74503: Test issues in "make check"

2024-11-26 Thread Pádraig Brady
On 26/11/2024 04:27, Gordon Steemson wrote: Hello again, On Nov 24, 2024, at 5:10 AM, Pádraig Brady wrote: On 24/11/2024 05:34, Gordon Steemson wrote: Setup: [...] I should also have added that the tests were running under the latest Bash 5.2.37 rather than the stock Bash 3.2, though

bug#74503: Test issues in "make check"

2024-11-24 Thread Pádraig Brady
On 24/11/2024 05:34, Gordon Steemson wrote: Setup: Coreutils package, v. 9.5; Power Mac G5 running OS 10.5.8 (Darwin 9.8.0). When running `make check`, I noticed the following two problems. - tests/ls/dired.sh can’t cope with the underlying file system stealthily applying normalization to th

bug#74427: tests/printf/printf-indexed failure on macOS

2024-11-20 Thread Pádraig Brady
On 19/11/2024 16:47, Paul Eggert wrote: On 2024-11-19 07:10, Pádraig Brady wrote: I've not got access to a macos system to test currently, but the attached should address this. That patch addresses only the empty string, not other strings that cannot be converted (e.g., a string consisti

bug#74428: tests/printf/printf-cov failure on macOS

2024-11-20 Thread Pádraig Brady
On 19/11/2024 04:41, Grisha Levit wrote: The u4 and U8 tests in tests/printf/printf-cov.pl fail on macOS 15: u4... printf: test u4: stdout mismatch, comparing u4.1 (expected) and u4.O (actual) *** u4.1Mon Nov 18 23:30:03 2024 --- u4.OMon Nov 18 23:30:03 2024 *** *** 1

bug#74427: tests/printf/printf-indexed failure on macOS

2024-11-19 Thread Pádraig Brady
On 19/11/2024 20:02, Paul Eggert wrote: On 2024-11-19 09:53, Pádraig Brady wrote: Do we really want to treat NUL and NULL strings differently?   $ src/printf '%d\n'   0   $ src/printf '%d\n' ''   printf: ‘’: expected a numeric value   0 Both behaviors

bug#74427: tests/printf/printf-indexed failure on macOS

2024-11-19 Thread Pádraig Brady
On 19/11/2024 21:48, Paul Eggert wrote: On 2024-11-19 12:28, Pádraig Brady wrote: But one could consider an empty argument as completely converted? No, because POSIX says the argument must be a C integer constant, and empty strings are not C integer constants. Similar reasoning applies for

bug#74427: tests/printf/printf-indexed failure on macOS

2024-11-19 Thread Pádraig Brady
On 19/11/2024 20:02, Paul Eggert wrote: On 2024-11-19 09:53, Pádraig Brady wrote: Do we really want to treat NUL and NULL strings differently?   $ src/printf '%d\n'   0   $ src/printf '%d\n' ''   printf: ‘’: expected a numeric value   0 Both behaviors

bug#74428: tests/printf/printf-cov failure on macOS

2024-11-19 Thread Pádraig Brady
On 19/11/2024 17:34, Bruno Haible wrote: Pádraig Brady wrote: I would prefer to bypass the ASCII case if CODE >= 0 && CODE < 128. However is that generally correct? Yes, at least for CODE >= 32 && CODE < 128 it is correct. This can be seen from the list of supporte

bug#74428: tests/printf/printf-cov failure on macOS

2024-11-19 Thread Pádraig Brady
On 19/11/2024 16:08, Bruno Haible wrote: Pádraig Brady wrote: On your macos 15 system, iconv() of 0x30 is failing to convert from utf8 to C, and the fallback in unicodeio.c is outputting the \u0030. Now I don't have access to macos to see exactly why that iconv() is failing, The macOS

bug#74427: tests/printf/printf-indexed failure on macOS

2024-11-19 Thread Pádraig Brady
On 19/11/2024 04:38, Grisha Levit wrote: See the following two chunks from the test suite log on macOS 15: + printf_check ' 0 1 ' '%100$*d %s %s %s\n' 4 1 + cat + shift + env printf '%100$*d %s %s %s\n' 4 1 printf: '': Invalid argument + fail=1 + printf_check_err 'printf: '\''A'\'': expected

bug#73418: ls (GNU coreutils) 9.4 is extremely slower than ls (GNU coreutils) 8.32 listing files on a cifs mounted share

2024-11-11 Thread Pádraig Brady
On 11/11/2024 16:47, Paul Eggert wrote: On 2024-11-10 05:48, Pádraig Brady wrote: BTW I've pushed a tweak to gnulib to avoid a -Werror=unused-variable issue with --disable-acl Thanks, I installed the attached further patch, since the res5t of the file uses MAYBE_UNUSED. Thanks for al

bug#73418: ls (GNU coreutils) 9.4 is extremely slower than ls (GNU coreutils) 8.32 listing files on a cifs mounted share

2024-11-10 Thread Pádraig Brady
On 10/11/2024 00:57, Paul Eggert wrote: On 2024-11-09 09:16, Pádraig Brady wrote:     $ src/ls -lZ INSTALL     lrwxrwxrwx 1 padraig padraig ? ... This is still an issue here. Oh, thanks for reminding me. That's a Gnulib bug, fixed here: https://lists.gnu.org/r/bug-gnulib/2024-11/msg

bug#73418: ls (GNU coreutils) 9.4 is extremely slower than ls (GNU coreutils) 8.32 listing files on a cifs mounted share

2024-11-09 Thread Pádraig Brady
On 03/10/2024 15:28, Pádraig Brady wrote: On 03/10/2024 07:39, Paul Eggert wrote: On 2024-10-02 15:14, Pádraig Brady wrote: I notice that tests/ls/getxattr-speedup.sh is failing now, which I've not looked into yet. I'm not seeing that after the changes I committed this evening.

bug#74107: Spurious ".IP" macros in a few coreutils 9.5 man pages

2024-10-30 Thread Pádraig Brady
On 30/10/2024 14:14, Glenn Golden wrote: A few man pages from coreutils 9.5 seem to have spurious ".IP" troff macros in several places. Noticed in tail.1, timeout.1. Not present in cat.1, df.1, du.1, ls.1, rm.1, tr.1. Did not check others. See attached screenshots of rendered pages for tail an

bug#74106: Find Bug in split util

2024-10-30 Thread Pádraig Brady
tag 74106 notabug close 74106 stop On 30/10/2024 11:33, Andrey S wrote: Hello! I've used split util to devide a 220G file into files of 1G size. I've used option '-d' like shown below. *split* -b 1G -d big-file.zip big-file.zip.part_ After part number 89 I've got part number 9000 and it goes w

bug#74103: Characters order in tr affects results

2024-10-30 Thread Pádraig Brady
tag 74103 notabug close 74103 stop On 30/10/2024 09:42, Jakub Filipiuk wrote: Hi I stumble upon situation, when characters order in tr affects it result. For example: $ echo "some: 123 fa-ncy string, " | tr -d ',-:' some fancy string When colon is moved before hyphen, result is correct $ ec

bug#73875: cp: there isn't even an option to quit on errors

2024-10-20 Thread Pádraig Brady
On 20/10/2024 15:21, Dan Jacobson wrote: Well OK, it is creating an unusable copy, and probably doesn't even return an error to the calling shell. So Makefiles using it will go on to the next step... with the final result being missing files, discovered just minutes away from the boss's big cere

bug#73875: cp: there isn't even an option to quit on errors

2024-10-20 Thread Pádraig Brady
On 19/10/2024 08:45, Dan Jacobson wrote: $ cp -a /usr/share/doc/qpdf/manual-html/ ~/Downloads/ cp: cannot create symbolic link '/home/jidanni/Downloads/manual-html/_static/css/badge_only.css': Permission denied cp: cannot create symbolic link '/home/jidanni/Downloads/manual-html/_static/css/th

bug#73784: [PATCH] cp: new option --nocache-source

2024-10-13 Thread Pádraig Brady
On 13/10/2024 05:56, Masatake YAMATO wrote: When copying files, the system data cache are consumed, the system data cache is utilized for both the source and destination files. In scenarios such as creating backup files for old, unused files, it is clear to users that these files will not be need

bug#73772: [PATCH] cp,mv: align the descriptions of long options

2024-10-12 Thread Pádraig Brady
On 12/10/2024 17:28, Masatake YAMATO wrote: * src/cp.c (usage): Adjust white spaces for --update. * src/mv.c (usage): Ditto. --- src/cp.c | 2 +- src/mv.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/cp.c b/src/cp.c index 1c4fd5c20..127b5603f 100644 --- a/src/cp.

bug#73418: ls (GNU coreutils) 9.4 is extremely slower than ls (GNU coreutils) 8.32 listing files on a cifs mounted share

2024-10-06 Thread Pádraig Brady
On 06/10/2024 18:53, Bernhard Voelker wrote: On 10/3/24 08:04, Paul Eggert wrote: I installed the attached (plus some other refactorings) to do that. I don't see test-suite failures anymore, thanks. > [PATCH] ls: tune indicator_name This change makes 'check-ls-dircolors' and therefore 'dis

bug#73418: ls (GNU coreutils) 9.4 is extremely slower than ls (GNU coreutils) 8.32 listing files on a cifs mounted share

2024-10-03 Thread Pádraig Brady
On 03/10/2024 07:39, Paul Eggert wrote: On 2024-10-02 15:14, Pádraig Brady wrote: I notice that tests/ls/getxattr-speedup.sh is failing now, which I've not looked into yet. I'm not seeing that after the changes I committed this evening. If you can still reproduce it please let u

bug#73418: ls (GNU coreutils) 9.4 is extremely slower than ls (GNU coreutils) 8.32 listing files on a cifs mounted share

2024-10-02 Thread Pádraig Brady
On 30/09/2024 06:24, Paul Eggert wrote: Looking at the current coreutils source, I noticed that 'ls' called getxattr when it didn't need to. I installed the attached patch to fix some of the issue; more could be done and perhaps I'll find the time. Among other things this patch should cause GNU l

bug#73418: ls (GNU coreutils) 9.4 is extremely slower than ls (GNU coreutils) 8.32 listing files on a cifs mounted share

2024-10-02 Thread Pádraig Brady
On 30/09/2024 09:26, Bernhard Voelker wrote: On 9/30/24 7:24 AM, Paul Eggert wrote: I installed the attached patch to fix some of the issue There's a new test failure for a require_root_ test here: FAIL: tests/ls/capability = That should be fixed by the attached. th

bug#73510: Questions on date command.

2024-09-27 Thread Pádraig Brady
On 27/09/2024 08:18, Benjamin Vargin via GNU coreutils Bug Reports wrote: Hello, First of all, I would like to thank you for all the works accomplished by your teams !! I'm currently implementing functions in bash which are using the command "date". I have noticed something strange when I real

bug#73474: Bug in factor utility of coreutils

2024-09-25 Thread Pádraig Brady
On 25/09/2024 20:55, Paul Eggert wrote: On 2024-09-25 08:14, Pádraig Brady wrote: It seems better to move the checks within the macro to avoid any future issues. I've also applied the same check to rsh2 in the attached. That patch doesn't suffice (nor does Artem's) because t

bug#73474: Bug in factor utility of coreutils

2024-09-25 Thread Pádraig Brady
On 25/09/2024 11:26, Артем Насонов wrote: To whom it may concern, I’m writing to let you know that I found an issue by fuzzing in coreutils in *factor* utility and want to report it. Here are some details: 1. Host architecture: Host it Debian x86_64 architecture 2. factor version: factor (GNU c

bug#72914: Issues in man pages of GNU Coreutils

2024-09-23 Thread Pádraig Brady
On 31/08/2024 12:19, 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#73418: ls (GNU coreutils) 9.4 is extremely slower than ls (GNU coreutils) 8.32 listing files on a cifs mounted share

2024-09-22 Thread Pádraig Brady
On 22/09/2024 07:21, Gian Domenico Bonazzoli wrote: Hi all, During an upgrade from Ubuntu 22.04 to Ubuntu 24.04 we discovered that "ls (GNU coreutils) 9.4" is extremely slower than "ls (GNU coreutils) 8.32" listing files on a cifs mounted share. Facts to help you in troubleshooting the problem.

bug#73068: printf: please implement POSIX:2024 argument reordering

2024-09-13 Thread Pádraig Brady
On 13/09/2024 13:55, Pádraig Brady wrote: On 12/09/2024 20:33, Paul Eggert wrote: On 2024-09-12 12:03, Pádraig Brady wrote: This is tricky enough, that we should be as restrictive as possible here, so I may resort to strspn(f, "0123456789") to parse instead. I'll think a bit

bug#73068: printf: please implement POSIX:2024 argument reordering

2024-09-13 Thread Pádraig Brady
On 12/09/2024 20:33, Paul Eggert wrote: On 2024-09-12 12:03, Pádraig Brady wrote: This is tricky enough, that we should be as restrictive as possible here, so I may resort to strspn(f, "0123456789") to parse instead. I'll think a bit about it. The code's also assuming

bug#73068: printf: please implement POSIX:2024 argument reordering

2024-09-12 Thread Pádraig Brady
On 12/09/2024 18:40, Collin Funk wrote: Hi Pádraig, Pádraig Brady writes: I'll apply the attached sometime tomorrow. Marking this as done. Patch looks good, thanks. One small comment, though. +#define GET_CURR_ARG(POS)

bug#73068: printf: please implement POSIX:2024 argument reordering

2024-09-12 Thread Pádraig Brady
On 12/09/2024 18:06, Bruno Haible wrote: Pádraig Brady wrote: I'll apply the attached sometime tomorrow. Nice! Thank you. There seems to be a typo in the unit test, though: It defines a shell function 'printf_checki_err' but the function it then invokes is 'printf_che

bug#73068: printf: please implement POSIX:2024 argument reordering

2024-09-12 Thread Pádraig Brady
On 09/09/2024 19:30, Pádraig Brady wrote: On 06/09/2024 15:06, Bruno Haible wrote: Hi, POSIX:2024 specifies that printf(1) should support numbered conversion specifications: https://pubs.opengroup.org/onlinepubs/9799919799/utilities/printf.html https://austingroupbugs.net/view.php?id=1592

bug#73194: ls command converts utf-8 character into escape sequences

2024-09-12 Thread Pádraig Brady
On 12/09/2024 11:16, Simon Wolfe wrote: I have one file name that uses Unicode character U+318DF, which is in the tertiary pane, more precisely CJK Unified Ideographs Extension H. touch 𱣟 ls returns: ''$'\360\261\243\237' Extension H was introduced in Unicode 15.0 in 2022. I also notice tha

bug#73068: printf: please implement POSIX:2024 argument reordering

2024-09-09 Thread Pádraig Brady
On 06/09/2024 15:06, Bruno Haible wrote: Hi, POSIX:2024 specifies that printf(1) should support numbered conversion specifications: https://pubs.opengroup.org/onlinepubs/9799919799/utilities/printf.html https://austingroupbugs.net/view.php?id=1592 Could this support please be added to GNU coreu

bug#72842: Compile error due to lto warning on Arch Linux -Werror=maybe-uninitialized

2024-08-28 Thread Pádraig Brady
--git a/ChangeLog b/ChangeLog index 8a7f812b67..fdcc79134e 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,11 @@ +2024-08-28 Pádraig Brady + + avoid GCC -Wmaybe-uninitialized false positives with LTO + Avoids false warnings with GCC 14.2.1 with -flto + + * lib/canonicalize.c: Initialize

bug#72770: stat: filesystem ID regression in 9.5 with musl libc

2024-08-23 Thread Pádraig Brady
On 23/08/2024 12:39, Natanael Copa wrote: On Fri, 23 Aug 2024 11:41:28 +0100 Pádraig Brady wrote: On 23/08/2024 08:14, Natanael Copa wrote: With coreutils 9.5 stat -f -c %i returns wrong value with musl libc. $ docker run --rm -it -v /tmp:/tmp alpine:3.20 sh -c "apk add --quiet core

bug#72770: stat: filesystem ID regression in 9.5 with musl libc

2024-08-23 Thread Pádraig Brady
On 23/08/2024 08:14, Natanael Copa wrote: With coreutils 9.5 stat -f -c %i returns wrong value with musl libc. $ docker run --rm -it -v /tmp:/tmp alpine:3.20 sh -c "apk add --quiet coreutils && stat --version && stat -f -c %i /tmp && busybox stat -f -c %i /tmp" stat (GNU coreutils) 9.5 Copyrigh

bug#72707: install: need_copy (for "-C") should use stat instead of lstat

2024-08-19 Thread Pádraig Brady
On 19/08/2024 03:44, Frank Heckenbach wrote: install dereferences symlinks given as sources (and I think that's good). The "-C" option, however, uses lstat rather than stat in need_copy and returns true if !S_ISREG. So the (dereferenced) file will always be copied despite "-C". Even worse, sinc

bug#72617: sort -n loses lines.

2024-08-14 Thread Pádraig Brady
On 14/08/2024 11:04, Simon B wrote: Hi Pádraig I am largely satisfied by your great explanation, I am still confused why lines go "missing" though. Even if the dot is being interpreted, it still should not lose the line containing 172.169.6.164 This is actually well explained in the onlin

bug#72617: sort -n loses lines.

2024-08-14 Thread Pádraig Brady
tag 72617 notabug close 72617 stop On 14/08/2024 09:43, Simon B wrote: Hallo, The output of my grep command is: # grep -i "sshd" /root/access.report | egrep -o '(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0- 9][0-9]?)\.(25[0-5]|

bug#72567: printf: Incorrect description of "%b"

2024-08-11 Thread Pádraig Brady
forcemerge 72567 72568 close 72567 stop On 11/08/2024 04:05, Keith Thompson wrote: There are three different descriptions of the printf(1) "%b" format: - printf --help - man printf.1 - info coreutils printf As of release 9.5 and the latest version in git (Thu 2024-08-08 c5725c8c4), the first t

bug#72446: [PATCH] stat: Fix memleak

2024-08-03 Thread Pádraig Brady
tag 72446 notabug close 72446 stop On 03/08/2024 17:10, Dmitry Chestnykh wrote: format and format2 strings are allocated by `malloc()` inside `xasprintf` so the memory should be freed * src/stat.c: Call `free()` on `format` and `format2` --- src/stat.c | 2 ++ 1 file changed, 2 insertions(+)

bug#72232: "make dist" is not reproducible

2024-07-21 Thread Pádraig Brady
On 21/07/2024 18:58, Paul Eggert wrote: On 2024-07-21 10:44, Pádraig Brady wrote: We can just rely on the timestamp of the .tarball-version to support reproducible _tarballs_. Although this makes the distributed file contents reproducible, the tarballs themselves are still not reproducible

bug#72232: "make dist" is not reproducible

2024-07-21 Thread Pádraig Brady
On 21/07/2024 17:18, Bruno Haible wrote: Hi, Subsequent runs of "make dist" in the same environment produce tarballs with different contents. How to reproduce: In a git checkout of coreutils, do: $ echo snapshot > .tarball-version $ ./configure; make -k maintainer-clean $ ./bootstrap $ ./conf

bug#72024: documentation suggestion: make old versions of docs easily available

2024-07-10 Thread Pádraig Brady
On 09/07/2024 22:18, mark.yagnatinsky--- via GNU coreutils Bug Reports wrote: If go to the website of say, Perl or Python, and I see there's a cool function I want to use, then often there will be a note "new in version X.Y". Then I know that if I need to support versions older than that, I can'

bug#72012: [PATCH] id: Warn if user in more groups than `id` can reliably print

2024-07-10 Thread Pádraig Brady
tag 72012 notabug close 72012 stop On 10/07/2024 00:31, Paul Eggert wrote: On 7/10/24 00:35, Pádraig Brady wrote: OK so id(1) will always show all groups it knows about. Then the warning message might be along the lines of:   "warning: User '%s' is a member of more groups t

bug#72012: [PATCH] id: Warn if user in more groups than `id` can reliably print

2024-07-09 Thread Pádraig Brady
On 09/07/2024 21:15, Otto Kekäläinen wrote: Hi! The point is just to emit a warning when this happens. Sure it is rare but the fix is pretty safe to apply. OK so id(1) will always show all groups it knows about. Then the warning message might be along the lines of: "warning: User '%s' is a

bug#72012: [PATCH] id: Warn if user in more groups than `id` can reliably print

2024-07-09 Thread Pádraig Brady
On 09/07/2024 05:22, Otto Kekäläinen wrote: While rare, it is possible for a user to be a member in more groups than what the system limit allows (on Linux typically NGROUPS_MAX=65536) and if that is the case, running `id` or `id user` will not print all of them. This is a minor bug, but easily f

bug#71986: RFC: date @ to support ms.

2024-07-08 Thread Pádraig Brady
On 07/07/2024 20:46, Richard Neill wrote: Hello, I've noticed a lot of systems now return the timestamp in milliseconds since the epoch, rather than seconds. This means that e.g. date --date='@1720378861258' will do something rather unexpected! May I suggest that it would be nice if date

bug#71895: Test failure in Coreutils 9.4 [During LFS Build]

2024-07-02 Thread Pádraig Brady
On 02/07/2024 02:05, 0xn00dle via GNU coreutils Bug Reports wrote: Hello, While running the test for Coreutils during my LFS build (Chapter 8.57 Coreutils-9.4: https://www.linuxfromscratch.org/lfs/view/12.1/chapter08/coreutils.html), I encountered a potential bug and the test recommended I re

bug#71803: ls --time=mtime is sorting by name instead of mtime

2024-06-27 Thread Pádraig Brady
On 27/06/2024 16:05, Dave wrote: The ls command without the -l option and with the --time=mtime option, is incorrectly sorting by the name rather than by the modification time. ls # sorts by name (ok) ls --time=mtime # sorts by name (should sort by mtime) // The current stateme

bug#71242: PR: src/stat.c - add magic for bcachefs

2024-05-28 Thread Pádraig Brady
On 28/05/2024 12:08, Paul Hedderly via GNU coreutils Bug Reports wrote: Currently stat does not know bcachefs $:~/gits/coreutils$ sudo stat -f -c %T / UNKNOWN (0xca451a4e) But it just needs to know that magic $:~/gits/coreutils$ sudo ./src/stat -f -c %T / bcachefs Please pull

bug#71191: od does unnecessary reads instead of seeking

2024-05-25 Thread Pádraig Brady
On 25/05/2024 08:05, Joseph C. Sible wrote: Consider running the following command, for looking at the pagemap bits of a given memory page: od -t x8 -N 8 -j 34359738368 /proc/PID/pagemap That file supports seeking, but od will unnecessarily read and discard 32GB worth of data instead of doing s

bug#71186: email address for patch

2024-05-25 Thread Pádraig Brady
tab 71186 notabug close 71186 stop On 24/05/2024 19:15, Данила Скачедубов wrote: Hi! I have a few questions. Please tell me, I want to compile the main files so that they are output by the man command. As far as I understand, this is done by the help2man-1.48.5 command. But at the

bug#71029: single-binary build broken on systems with separate libintl

2024-05-21 Thread Pádraig Brady
On 18/05/2024 18:09, Audrey Dutcher wrote: I presume you have the same issue with coreutils 9.4 ? Correct. I presume the problematic flags are propagated through LIBINTL or MBRTOWC_LIB. What are those set to for reference in your Makefile? On plain FreeBSD it is set to /usr/local/lib/libin

bug#71029: single-binary build broken on systems with separate libintl

2024-05-18 Thread Pádraig Brady
On 17/05/2024 17:11, Audrey Dutcher wrote: On my FreeBSD system, downloading coreutils-9.5.tar.xz, then building with `./configure --enable-single-binary && make` does not succeed, with the error message `don't know how to make -Wl,-rpath. Stop` I believe the root cause of this is https://github

bug#70946: [PATCH] doc: improve the man page for sleep

2024-05-15 Thread Pádraig Brady
On 15/05/2024 03:46, Nikolaos Chatzikonstantinou wrote: On Tue, May 14, 2024 at 4:03 PM Nikolaos Chatzikonstantinou wrote: On Tue, May 14, 2024, 3:59 PM Pádraig Brady wrote: On 14/05/2024 17:36, Nikolaos Chatzikonstantinou wrote: See attachment. Well just above your new mention of

bug#70946: [PATCH] doc: improve the man page for sleep

2024-05-14 Thread Pádraig Brady
On 14/05/2024 17:36, Nikolaos Chatzikonstantinou wrote: See attachment. Well just above your new mention of floating-point, we have: "NUMBER need not be an integer". How about I adjust your patch to adjust that text to say: "NUMBER can be an integer or floating-point". cheers, Pádraig.

bug#70887: In coreutils 9.5, "cp" command does not honor "--interactive" option

2024-05-12 Thread Pádraig Brady
On 12/05/2024 16:06, Paul Eggert wrote: On 2024-05-12 04:49, Pádraig Brady wrote: @@ -1151,7 +1151,8 @@ main (int argc, char **argv) { /* Default cp operation. */ x.update = false; - x.interactive = I_UNSPECIFIED

bug#70887: In coreutils 9.5, "cp" command does not honor "--interactive" option

2024-05-12 Thread Pádraig Brady
On 12/05/2024 00:03, Robert Hill wrote: After upgrading coreutils from 9.0 to 9.5, the following change occurred: In coreutils 9.0, the command "cp -Tipruvx /src-dir /dst-dir" requested interactive confirmation before replacing an old destination file with a newer source file, as expected. In c

bug#70873: join --return-error-if-any-unmatched-lines

2024-05-11 Thread Pádraig Brady
On 11/05/2024 10:14, Dan Jacobson wrote: join should have an option to return an error value in the shell's $? if any lines are not matched. Currently the man page doesn't even mention a return value. So it is not set in stone yet. Currently one must save -v output in a file then use test -s do

bug#70214: 'install' fails to copy regular file to autofs/cifs, due to ACL or xattr handling

2024-05-09 Thread Pádraig Brady
On 13/04/2024 18:42, Pádraig Brady wrote: On 13/04/2024 17:39, Pádraig Brady wrote: install(1) defaults to mode 600 for new files, and uses set_acl() with that (since 2007 https://github.com/coreutils/coreutils/commit/f634e8844 ) The psuedo code that install(1) uses is: copy_reg() if (x

bug#70814: pwd(1) man page: Unclear "avoid" wording

2024-05-07 Thread Pádraig Brady
On 07/05/2024 05:19, Bruce Jerrick wrote: This wording in the pwd(1) man page is unclear:     -P, --physical     avoid all symlinks "resolve all symlinks" would be much better wording. Pushed that in your name. Marking this as done. thanks, Pádraig

bug#70801: Weird behaviour when standard input is closed

2024-05-06 Thread Pádraig Brady
On 06/05/2024 08:38, Bernard Burette wrote: Hi, If I try: $ cat <&- cat: -: Bad file descriptor cat: closing standard input: Bad file descriptor $ The error on stdin beign closed is displayed twice plus "-" is for a FILE argument to replace standard input, It would make more sense to m

bug#70727: cp doesn't recognize the new --update=none-fail option

2024-05-03 Thread Pádraig Brady
On 03/05/2024 05:12, Attila Fidan via GNU coreutils Bug Reports wrote: Hi, I wanted to use the new cp --update=none-fail option introduced in 9.5, but it said "invalid argument ‘none-fail’ for ‘--update’". It turns out that the commit (49912bac286eb3c0ef7d1567ae790193ad5eb2e8) adding it forgot t

bug#70714: realpath no error for unreadable-symlink

2024-05-02 Thread Pádraig Brady
On 02/05/2024 07:16, Nineteendo INC wrote: coreutils version: stable 9.5 (bottled) OS version: macOS 13.6.6 (22G630) `realpath` doesn’t behave correctly for unreadable symlinks: wannes@Stefans-iMac ~ % ln -s . src wannes@Stefans-iMac ~ % grealpath -e src/.. /Users wannes@Stefans-iMac ~ % chmod

bug#70699: Possible bug in /usr/bin/paste

2024-05-01 Thread Pádraig Brady
On 01/05/2024 15:28, Art Shelest via GNU coreutils Bug Reports wrote: Good morning, I am seeing an aberrant behavior from the /usr/bin/paste utility when working with Windows-style CR/LF text files. The repro is for Mint Mate (Virginia). If I change the line endings in the first file to Unix f

bug#70532: sort: Mention counting fields from the end

2024-04-23 Thread Pádraig Brady
On 23/04/2024 11:14, Dan Jacobson wrote: In (info "(coreutils) sort invocation") be sure to add an example of a way or workaround for counting fields from the end of the line. E.g., we want to sort on the last field, but don't know for sure how many fields a line might contain. E.g., sort by surn

bug#70418: ls bug

2024-04-17 Thread Pádraig Brady
On 16/04/2024 23:17, Paul Eggert wrote: On 4/16/24 14:30, Toby Kelsey wrote: The man page doesn't explain this format conflict, while the info page (info '(coreutils) ls invocation' or 'info ls') claims '-f' implies '-1' which is also incorrect: 'ls -1f' gives different output to to 'ls -f'. Y

bug#70411: [bug] install(1) fails to read /dev/stdin on Darwin

2024-04-16 Thread Pádraig Brady
On 16/04/2024 15:47, Alejandro Colomar wrote: Hi Pádraig, On Tue, Apr 16, 2024 at 03:25:22PM +0100, Pádraig Brady wrote: What version of darwin is this? I can't repro on Darwin 21.6.0 (MacOSX 12.6). The issue seems to be that /dev/stdin returns a varying inode which install(1) doesn&#

bug#70411: [bug] install(1) fails to read /dev/stdin on Darwin

2024-04-16 Thread Pádraig Brady
On 16/04/2024 12:33, Pádraig Brady wrote: On 16/04/2024 01:19, Alejandro Colomar wrote: Hi! I don't own a Darwin system, so I can't help much reproduce. However, I've received a bug report to the Linux man-pages, that our build system (GNUmakefile-based), which

bug#70411: [bug] install(1) fails to read /dev/stdin on Darwin

2024-04-16 Thread Pádraig Brady
On 16/04/2024 01:19, Alejandro Colomar wrote: Hi! I don't own a Darwin system, so I can't help much reproduce. However, I've received a bug report to the Linux man-pages, that our build system (GNUmakefile-based), which ends up calling ... | install /dev/stdin $@ doesn't work on Darwi

bug#70214: 'install' fails to copy regular file to autofs/cifs, due to ACL or xattr handling

2024-04-15 Thread Pádraig Brady
On 15/04/2024 15:37, Andreas Grünbacher wrote: Hello, Am So., 14. Apr. 2024 um 00:43 Uhr schrieb Pádraig Brady : On 13/04/2024 20:29, Bruno Haible wrote: Hi Pádraig, I wrote: 5) The same thing with 'cp -a' succeeds: $ build-sparc64/src/cp -a /var/tmp/foo3941 $HOME/foo3941;

bug#70214: 'install' fails to copy regular file to autofs/cifs, due to ACL or xattr handling

2024-04-13 Thread Pádraig Brady
On 13/04/2024 20:29, Bruno Haible wrote: Hi Pádraig, I wrote: 5) The same thing with 'cp -a' succeeds: $ build-sparc64/src/cp -a /var/tmp/foo3941 $HOME/foo3941; echo $? 0 $ build-sparc64-no-acl/src/cp -a /var/tmp/foo3941 $HOME/foo3941; echo $? 0 You wrote: The psuedo code that install(1) us

bug#70214: 'install' fails to copy regular file to autofs/cifs, due to ACL or xattr handling

2024-04-13 Thread Pádraig Brady
On 13/04/2024 17:39, Pádraig Brady wrote: install(1) defaults to mode 600 for new files, and uses set_acl() with that (since 2007 https://github.com/coreutils/coreutils/commit/f634e8844 ) The psuedo code that install(1) uses is: copy_reg() if (x->set_mode) /* install */ set_acl(d

bug#70214: 'install' fails to copy regular file to autofs/cifs, due to ACL or xattr handling

2024-04-13 Thread Pádraig Brady
[PATCH] acl-permissions: avoid erroneous failure on CIFS * lib/set-permissions.c (set_acls): On Linux also discount EACESS as a valid errno with FD operations, as CIFS was seen to return that erroneously in some cases. --- ChangeLog | 7 +++ lib/set-permissions.c | 8 +++- 2 fi

bug#35247: [PATCH] Add alacritty to terminal list supporting colors

2024-04-10 Thread Pádraig Brady
Things have changed a little since the original request. alacritty sets $COLORTERM, and dircolors now auto accepts that since: https://github.com/coreutils/coreutils/commit/75c9fc674 There are some complications with remote shells, but they should boil down to setting up ssh to send/accept COLORT

  1   2   3   4   5   6   7   8   9   10   >