bug#16940: [PATCH] tests: Do not access /dev/tty if it does not exist

2014-03-05 Thread Pádraig Brady
On 03/05/2014 09:17 AM, Bernhard Voelker wrote: On 03/05/2014 05:20 AM, Pádraig Brady wrote: if test -w /dev/full test -c /dev/full test -w /dev/tty test -c /dev/tty; then This looks right. However, I'm wondering why the 'test -t 1' right after the exec redirection didn't

bug#16940: [PATCH] tests: Do not access /dev/tty if it does not exist

2014-03-05 Thread Pádraig Brady
On 03/05/2014 03:43 PM, Bernhard Voelker wrote: On 03/05/2014 04:21 PM, Pádraig Brady wrote: Ondřej Vašík ran the rawhide build again producing: ./tests/misc/nohup.sh: line 66: /dev/tty: No such device or address + fail=1 So exec /dev/tty is throwing ENXIO and exiting the subshell

bug#16940: [PATCH] tests: Do not access /dev/tty if it does not exist

2014-03-05 Thread Pádraig Brady
On 03/05/2014 04:46 PM, Pádraig Brady wrote: Note the ':' is problematic though as the : always returns true. Well it does for solaris, freebsd, dash, bash-4.3 at least. In ksh and bash=4.2 it does return an error as you assumed. The ':' construct is only needed for csh anyway I think which

bug#16940: [PATCH] tests: Do not access /dev/tty if it does not exist

2014-03-04 Thread Pádraig Brady
On 03/05/2014 03:34 AM, Cyril Roelandt wrote: * tests/misc/nohup.sh: Do not try to access /dev/tty if it does not exist. This happens on GNU Guix, for instance. --- tests/misc/nohup.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/misc/nohup.sh

bug#16922: df --si -h should emit a warning

2014-03-03 Thread Pádraig Brady
On 03/03/2014 08:00 AM, Bernhard Voelker wrote: On 03/03/2014 04:02 AM, Pádraig Brady wrote: Very few read info pages, and anyway in this case we should be clear at the man page level. Mateusz stated the issue was that on a quick glance, the --si option wasn't described well enough

bug#16922: df --si -h should emit a warning

2014-03-03 Thread Pádraig Brady
On 03/03/2014 04:55 AM, Paul Eggert wrote: Pádraig Brady wrote: + -h, --human-readable print abbreviated sizes in powers of 1024 (e.g. %s)\n\ + -H, --si print abbreviated sizes in powers of 1000 (e.g. %s)\n\ Thanks for looking into improving this. Please put commas after

bug#16922: df --si -h should emit a warning

2014-03-03 Thread Pádraig Brady
On 03/03/2014 09:36 AM, Pádraig Brady wrote: On 03/03/2014 04:55 AM, Paul Eggert wrote: Pádraig Brady wrote: + -h, --human-readable print abbreviated sizes in powers of 1024 (e.g. %s)\n\ + -H, --si print abbreviated sizes in powers of 1000 (e.g. %s)\n\ Thanks for looking

bug#16922: df --si -h should emit a warning

2014-03-03 Thread Pádraig Brady
On 03/03/2014 10:54 AM, Pádraig Brady wrote: On 03/03/2014 09:36 AM, Pádraig Brady wrote: On 03/03/2014 04:55 AM, Paul Eggert wrote: Pádraig Brady wrote: + -h, --human-readable print abbreviated sizes in powers of 1024 (e.g. %s)\n\ + -H, --si print abbreviated sizes

bug#16922: df --si -h should emit a warning

2014-03-02 Thread Pádraig Brady
On 03/02/2014 12:33 PM, Mateusz Jończyk wrote: Hello, There should be a warning when running df --si -h because it will display results in blocks of 1024 and not 1000, as one might think (the switch --si displays blocks in a human-readable format when used by itself). This is confusing.

bug#16922: df --si -h should emit a warning

2014-03-02 Thread Pádraig Brady
On 03/02/2014 05:38 PM, Bernhard Voelker wrote: On 03/02/2014 03:33 PM, Pádraig Brady wrote: On 03/02/2014 12:33 PM, Mateusz Jończyk wrote: Hello, There should be a warning when running df --si -h because it will display results in blocks of 1024 and not 1000, as one might think (the switch

bug#16872: `date -d 'TZ=America/Los_Angeles 00:00 + 1 hour'` crashes

2014-02-27 Thread Pádraig Brady
On 02/27/2014 09:48 PM, Bernhard Voelker wrote: On 02/25/2014 12:11 PM, Pádraig Brady wrote: Proposed patch attached. parse_datetime per se is pretty ugly, however, the fix LGTM: +1 I've pushed that to gnulib, and the attached to coreutils. thanks for the review, Pádraig. From

bug#16889: erratic behavior of cp command i.e while copying files (using *) from one directory to another directory

2014-02-26 Thread Pádraig Brady
tag 16889 notabug close 16889 stop On 02/26/2014 12:36 PM, Anil Kumar wrote: Hello I have observed, one erratic behavior of cp command i.e while copying files (using *) from one directory to another directory if we miss destination directory then cp command copies content of 1st file into

bug#16872: `date -d 'TZ=America/Los_Angeles 00:00 + 1 hour'` crashes

2014-02-25 Thread Pádraig Brady
On 02/25/2014 08:13 AM, Mike Frysinger wrote: as reported by Bertrand Jacquin, this crashes: $ date -d 'TZ=America/Los_Angeles 00:00 + 1 hour' Segmentation fault (gdb) bt #0 0x77ab1014 in __GI___libc_free (mem=0x7fffc8b0) at malloc.c:2942 #1 0x00406730 in

bug#16872: `date -d 'TZ=America/Los_Angeles 00:00 + 1 hour'` crashes

2014-02-25 Thread Pádraig Brady
On 02/25/2014 08:50 AM, Pádraig Brady wrote: On 02/25/2014 08:13 AM, Mike Frysinger wrote: as reported by Bertrand Jacquin, this crashes: $ date -d 'TZ=America/Los_Angeles 00:00 + 1 hour' Segmentation fault (gdb) bt #0 0x77ab1014 in __GI___libc_free (mem=0x7fffc8b0

bug#16831: don't say uniq -D -c is meaningless

2014-02-21 Thread Pádraig Brady
On 02/21/2014 02:28 PM, mcmasters wrote: I think uniq -D -c may be meaningful when used in conjuction with -f Specifically, I wanted to use uniq -D -c -f 1 to find lines that are identical with respect to field 2 (-f 1), get a listing of how many times they occur (-c), but not throw away the

bug#16838: Confusing localization of seq

2014-02-21 Thread Pádraig Brady
On 02/21/2014 10:48 PM, Göran Uddeborg wrote: It seems the input arguments of seq are not localized, but the output is. I was surprised to find this, and thought I'd ask here if it is an intentional decision. More specifically, I'm using the Swedish locale, where the radix character is a

bug#16778: Neither ls nor sort do a correct lexicographic sort

2014-02-17 Thread Pádraig Brady
tag 16778 notabug close 16778 stop On 02/17/2014 02:40 PM, Jarosław Rzeszótko wrote: Hi, Please contemplate the following shell session: /home/jarek # mkdir test /home/jarek # cd test /home/jarek/test # touch x_y.c xs.c /home/jarek/test # ls -1 razem 0 -rw-r--r-- 1 jarek jarek 0

bug#16730: ls -dF double trailing slash bug

2014-02-12 Thread Pádraig Brady
On 02/12/2014 04:52 PM, Eric Blake wrote: tag 16730 notabug thanks On 02/12/2014 07:45 AM, Radko Dinev wrote: user@host ~$ ls -dF somedir somedir/ user@host ~$ ls -dF somedir/ somedir// Notice the double trailing slash which shouldn't be there in the second example. Not a bug.

bug#16718: bug in vi on linux

2014-02-11 Thread Pádraig Brady
tag 16718 notabug close 16718 stop On 02/11/2014 02:02 AM, Cheng Ong wrote: Hi there, Just encountered a bug in VI. Editing file 'x' using vi, when done, content of file 'x' was saved as well in file 'y'. File 'y' has no relation to file 'x' and is sitting in a different directory. Only

bug#16578: Wish: Support for non-native endianness in od

2014-02-09 Thread Pádraig Brady
On 02/09/2014 08:42 AM, Niels Möller wrote: Pádraig Brady p...@draigbrady.com writes: Attached in the patch I intend to push in your name. Nice. I also added docs to usage() and the texinfo file, and added a test. I don't quite understand how the test works, but as far as I see

bug#16700: [PATCH] - Add audio file type .m4a to LS_COLORS

2014-02-09 Thread Pádraig Brady
On 02/09/2014 11:51 AM, John wrote: Trivial patch to display .m4a files in the same cyan color as all other audio files via LS_COLORS. This [m4a] is a very common format generated by iTunes so I would think many users would like to see this implemented. Please cc me on any replies; I am

bug#16578: Wish: Support for non-native endianness in od

2014-02-09 Thread Pádraig Brady
On 02/10/2014 01:59 AM, Paul Eggert wrote: Pádraig Brady wrote: $ time od.new -tx8 --endian=bug od.in 4.97 elapsed If you really used --endian=bug and there was no diagnostic, then there must have been a bug. :-) Ha! I retyped incorrectly rather than copy/pasted. I can confirm

bug#15173: [PATCH] cp: with --link always use linkat() if available

2014-02-09 Thread Pádraig Brady
On 12/12/2013 06:44 PM, Pádraig Brady wrote: On 12/09/2013 02:24 AM, Pádraig Brady wrote: Sorry if you get multiple copies of this. The test for this is failing on solaris 10 (NFS) It does seem that hardlinks to symlinks are supported: $ touch tfile $ ln -s tfile tlink $ src/ln -L tlink

bug#15173: [PATCH] cp: with --link always use linkat() if available

2014-02-09 Thread Pádraig Brady
On 02/10/2014 02:29 AM, Paul Eggert wrote: Pádraig Brady wrote: +#if ! defined HAVE_LINKAT !(LINK_FOLLOWS_SYMLINKS S_ISLNK (src_mode) - x-dereference == DEREF_NEVER)) + x-dereference == DEREF_NEVER) +#endif Could you reword that sort of thing

bug#16578: Wish: Support for non-native endianness in od

2014-02-08 Thread Pádraig Brady
On 02/02/2014 01:20 AM, Pádraig Brady wrote: On 01/31/2014 09:44 AM, Niels Möller wrote: ni...@lysator.liu.se (Niels Möller) writes: Pádraig Brady p...@draigbrady.com writes: I agree this would be useful and easy enough to add. I suppose the interface would be --endian=little|big Maybe I

bug#16669: inconsistent 'rm -ir' prompting behavior

2014-02-06 Thread Pádraig Brady
On 02/06/2014 04:39 PM, Eric Blake wrote: On today's Austin Group call, we discussed http://austingroupbugs.net/view.php?id=802 regarding 'rm' behavior. They pointed out that GNU has an optimization not allowed by a strict reading of the current standard: $ mkdir foo $ rm -ir foo rm:

bug#16578: Wish: Support for non-native endianness in od

2014-02-01 Thread Pádraig Brady
On 01/31/2014 09:44 AM, Niels Möller wrote: ni...@lysator.liu.se (Niels Möller) writes: Pádraig Brady p...@draigbrady.com writes: I agree this would be useful and easy enough to add. I suppose the interface would be --endian=little|big Maybe I can have a look at what it takes. Below

bug#16329: Acknowledgement (`head --lines=-0' prints nothing if no newline at the EOF)

2014-01-29 Thread Pádraig Brady
On 01/03/2014 08:40 PM, Алексей Шилин wrote: Looks like I was overly cautious about decrementing an unsigned... size_t n = bytes_read; while (n) { if (all_lines) n -= n ? 1 : 0;// ...here. else As it is under `while (n)' statement, n is always true here, and

bug#16578: Wish: Support for non-native endianness in od

2014-01-29 Thread Pádraig Brady
On 01/28/2014 12:54 PM, Niels Möller wrote: For the od program, it would be nice with a flag to specify the endianness for all types which are larger than a byte. Possible alternatives could be big endian, little endian, native endian. I agree this would be useful and easy enough to add. I

bug#16539: More details on df command output for you

2014-01-28 Thread Pádraig Brady
On 01/28/2014 11:13 AM, Bernhard Voelker wrote: On 01/27/2014 11:47 PM, Bernhard Voelker wrote: On 01/27/2014 02:06 AM, Pádraig Brady wrote: wrt c) and annoying warnings, I also notice `df -a` on a default Fedora 20 install here, giving multiple duplicate warnings like: df: ‘net

bug#16336: bug report tail with hfsplus filesystem

2014-01-28 Thread Pádraig Brady
On 01/04/2014 06:01 AM, Pádraig Brady wrote: On 01/04/2014 03:04 AM, Pieter van Voorst Vader wrote: Hi bug-coreutils, got this bug in tail for a hfsplus filesystem on ubuntu 13.10 tail: unrecognized file system type 0x482b for ‘serviio.log’. please report this to bug-coreutils@gnu.org

bug#16539: More details on df command output for you

2014-01-26 Thread Pádraig Brady
On 01/25/2014 11:55 PM, Bernhard Voelker wrote: On 01/25/2014 04:19 AM, Pádraig Brady wrote: On 01/24/2014 10:27 PM, Bernhard Voelker wrote: The above is the result of df suppressing duplicate entries like bind mounts. This filtering is done based on the device number. As this example shows

bug#16539: More details on df command output for you

2014-01-26 Thread Pádraig Brady
On 01/26/2014 11:35 PM, Bernhard Voelker wrote: On 01/26/2014 12:28 PM, Pádraig Brady wrote: On 01/25/2014 11:55 PM, Bernhard Voelker wrote: However, I remember some other corner cases with eclipsed file systems in the Fedora bug tracker. I think we're quite close to solve them all this time

bug#16561: Bug report for 'head' (and 'wc' et. al.)

2014-01-26 Thread Pádraig Brady
forcemerge 16561 16329 stop On 01/26/2014 03:07 PM, LGUC wrote: THE INCOMPLETE ATTACMENT! (working on sunday makes not my lucky day. Sorry for the inconveniences!. Please disregard the previous 2 mails) __

bug#16550: Request review of CHOWN man page synopsis

2014-01-25 Thread Pádraig Brady
tag 16550 notabug close 16550 stop On 01/25/2014 01:11 PM, Anubhav Chaturvedi wrote: Hi I was going through the man page ( on my Ubuntu 12.04 ) and noticed that in the synopsis, owner has been marked as optional ( i.e, it is enclosed in [ ] ). chown [OPTION]... [OWNER][:[GROUP]] FILE...

bug#16549: bug

2014-01-25 Thread Pádraig Brady
On 01/25/2014 10:33 AM, sn...@eaglet.co.in wrote: make[6]: *** [test-suite.log] Error 1 make[6]: Leaving directory `/sources/coreutils-8.21/gnulib-tests' make[5]: *** [check-TESTS] Error 2 make[5]: Leaving directory `/sources/coreutils-8.21/gnulib-tests' make[4]: *** [check-am] Error 2

bug#16532: Test Fail: tests/chown/separator

2014-01-24 Thread Pádraig Brady
On 01/24/2014 07:43 AM, Bernhard Voelker wrote: On 01/24/2014 04:09 AM, Pádraig Brady wrote: On 01/24/2014 02:46 AM, Assaf Gordon wrote: $ getent group | grep ^users users:x:100: users:x:1000:www-data,XXX,YYY === Oh right, grep ^$id_gn: it is so. Note we can't rely on getent(1) being

bug#16532: Test Fail: tests/chown/separator

2014-01-24 Thread Pádraig Brady
On 01/24/2014 04:58 PM, Assaf Gordon wrote: On 01/24/2014 07:46 AM, Bernhard Voelker wrote: On 01/24/2014 04:09 AM, Pádraig Brady wrote: Oh right, grep ^$id_gn: it is so. BTW: I'd change the skip_ message to reflect the above mentioned corner case where getent is not available, something

bug#16539: More details on df command output for you

2014-01-24 Thread Pádraig Brady
On 01/24/2014 10:27 PM, Bernhard Voelker wrote: tag 16539 notabug close thanks On 01/24/2014 09:47 PM, Curtis Rubel wrote: df command output with no args: only 1 nfs mount is listed Just for info: df in openSUSE-13.1 is currently identical to that in coreutils-v8.21. The above is

bug#16532: Test Fail: tests/chown/separator

2014-01-23 Thread Pádraig Brady
On 01/23/2014 11:41 PM, Assaf Gordon wrote: On 01/23/2014 06:20 PM, Bernhard Voelker wrote: On 01/23/2014 07:41 PM, Assaf Gordon wrote: $ strace ../src/chown 34574:users . 21 | grep -A 5 -B 5 chown fchownat(AT_FDCWD, ., 34574, 100, 0) = -1 EPERM (Operation not permitted) ++ id -g +

bug#16532: Test Fail: tests/chown/separator

2014-01-23 Thread Pádraig Brady
On 01/24/2014 01:38 AM, Assaf Gordon wrote: This patch makes the test skip on my server (did not test it on other systems). On 01/23/2014 08:09 PM, Pádraig Brady wrote: On 01/23/2014 11:41 PM, Assaf Gordon wrote: So I guess this is not a bug, and can be closed. I'll just ignore

bug#16530: Bootstrapping fails with missing m4/cu-progs.m4

2014-01-23 Thread Pádraig Brady
tag 16530 notabug close 16530 stop On 01/23/2014 06:22 PM, Assaf Gordon wrote: Follow-up: On 01/23/2014 11:47 AM, Assaf Gordon wrote: Just tried to compile coreutils from scratch, and encountered the following problem: === $ git clone git://git.sv.gnu.org/coreutils $ cd coreutils $

bug#16532: Test Fail: tests/chown/separator

2014-01-23 Thread Pádraig Brady
On 01/24/2014 01:43 AM, Pádraig Brady wrote: On 01/24/2014 01:38 AM, Assaf Gordon wrote: This patch makes the test skip on my server (did not test it on other systems). On 01/23/2014 08:09 PM, Pádraig Brady wrote: On 01/23/2014 11:41 PM, Assaf Gordon wrote: So I guess this is not a bug

bug#16532: Test Fail: tests/chown/separator

2014-01-23 Thread Pádraig Brady
On 01/24/2014 02:46 AM, Assaf Gordon wrote: On 01/23/2014 09:32 PM, Pádraig Brady wrote: Actually I messed up the login in the suggestion. I think the above should be s/!=/=/ which I've done in the attached patch. If you could confirm it was skipped on your system it would be great. I'll

bug#16468: join

2014-01-16 Thread Pádraig Brady
On 01/17/2014 12:00 AM, Bernhard Voelker wrote: On 01/16/2014 07:10 PM, Eric Blake wrote: On 01/16/2014 10:46 AM, barry kesner wrote: How do you tell join this without resorting. The files are huge! Unfortunately, there isn't any really good way, short of re-processing the files to make

bug#16335: Segmentation fault when using cp -a with SELinux and fakeroot

2014-01-14 Thread Pádraig Brady
On 01/14/2014 10:54 AM, Bernhard Voelker wrote: On 01/13/2014 09:09 PM, Pádraig Brady wrote: Pushing the attached 2 patches in a while. Hi Padraig, thanks, the refactoring into gcc_shared_ is a good idea. But I missed this one: when selinux is not supported, the new no-ctx.sh test

bug#16335: Segmentation fault when using cp -a with SELinux and fakeroot

2014-01-14 Thread Pádraig Brady
On 01/14/2014 12:38 PM, Bernhard Voelker wrote: On 01/14/2014 12:35 PM, Pádraig Brady wrote: On 01/14/2014 10:54 AM, Bernhard Voelker wrote: + test -e preloaded + skip_ 'LD_PRELOAD interception failed' Oh right. I think this should restrict the test appropriately... commit

bug#16335: Segmentation fault when using cp -a with SELinux and fakeroot

2014-01-13 Thread Pádraig Brady
I'm going to push the attached very soon, to address this. thanks, Pádraig. From 2b3b5bfcd5f4161d17c0bc3d43f6edcfc4a2b294 Mon Sep 17 00:00:00 2001 From: Nicolas Looss nicolas.io...@m4x.org Date: Sat, 4 Jan 2014 03:03:51 + Subject: [PATCH] copy: fix a segfault in SELinux context copying code

bug#16335: Segmentation fault when using cp -a with SELinux and fakeroot

2014-01-13 Thread Pádraig Brady
On 01/13/2014 02:50 PM, Pádraig Brady wrote: +# Then compile/link it: +$CC -shared -fPIC -O2 k.c -o k.so \ + || framework_failure_ 'failed to build SELinux shared library' I'll change that to a || skip_ ... so that we avoid issues with no (stub) selinux/selinux.h being available. thanks

bug#16335: Segmentation fault when using cp -a with SELinux and fakeroot

2014-01-13 Thread Pádraig Brady
On 01/13/2014 03:27 PM, Bernhard Voelker wrote: On 01/13/2014 03:57 PM, Pádraig Brady wrote: On 01/13/2014 02:50 PM, Pádraig Brady wrote: +# Then compile/link it: +$CC -shared -fPIC -O2 k.c -o k.so \ + || framework_failure_ 'failed to build SELinux shared library' I'll change

bug#16335: Segmentation fault when using cp -a with SELinux and fakeroot

2014-01-13 Thread Pádraig Brady
On 01/13/2014 05:09 PM, Pádraig Brady wrote: On 01/13/2014 03:27 PM, Bernhard Voelker wrote: On 01/13/2014 03:57 PM, Pádraig Brady wrote: On 01/13/2014 02:50 PM, Pádraig Brady wrote: +# Then compile/link it: +$CC -shared -fPIC -O2 k.c -o k.so \ + || framework_failure_ 'failed to build

bug#16335: Segmentation fault when using cp -a with SELinux and fakeroot

2014-01-13 Thread Pádraig Brady
On 01/13/2014 08:12 PM, Nicolas Iooss wrote: Le 13/01/2014 15:50, Pádraig Brady a écrit : I'm going to push the attached very soon, to address this. thanks, Pádraig. Thanks for setting me as the author of this patch. Nevertheless my name (Iooss) spells with and I (like India) and not L

bug#16409: Some amusing results with dd

2014-01-10 Thread Pádraig Brady
tag 16409 notabug close 16409 stop You're hitting various type and system limits. In general it's best to keep bs=1 and increase the seek size to get this functionality portably. Newer versions of GNU dd though will handle the count=0 case better and not alloc since:

bug#16329: `head --lines=-0' prints nothing if no newline at the EOF

2014-01-03 Thread Pádraig Brady
On 01/03/2014 03:50 PM, Алексей Шилин wrote: Hi, If one runs `head --lines=-0 somefile', he'll sometimes get no output instead of full file contents as expected after reading the manual: -n, --lines=[-]K print the first K lines instead of the first 10; with the lead‐

bug#16329: `head --lines=-0' prints nothing if no newline at the EOF

2014-01-03 Thread Pádraig Brady
On 01/03/2014 04:57 PM, Eric Blake wrote: On 01/03/2014 08:50 AM, Алексей Шилин wrote: Hi, If one runs `head --lines=-0 somefile', he'll sometimes get no output instead of full file contents as expected after reading the manual: -n, --lines=[-]K print the first K lines instead of

bug#16335: Segmentation fault when using cp -a with SELinux and fakeroot

2014-01-03 Thread Pádraig Brady
On 01/03/2014 10:08 PM, Nicolas Iooss wrote: Hello, After upgrading to coreutils 8.22 I can no longer build packages which uses cp -a to copy files due to a segmentation fault happening in libselinux. I've tried to reproduce this bug with few commands, in a directory which doesn't have

bug#16336: bug report tail with hfsplus filesystem

2014-01-03 Thread Pádraig Brady
On 01/04/2014 03:04 AM, Pieter van Voorst Vader wrote: Hi bug-coreutils, got this bug in tail for a hfsplus filesystem on ubuntu 13.10 tail: unrecognized file system type 0x482b for ‘serviio.log’. please report this to bug-coreutils@gnu.org. reverting to polling Cool thanks, we'll add

bug#16309: cp is a cpu hog

2013-12-31 Thread Pádraig Brady
On 12/31/2013 07:37 AM, U.Mutlu wrote: Hello, there is a big bug with the cp command: it eats all cpu resources, the system is not responsive while copying a huge file, say a file of size 10 GB. There are other _desasterous_ consequences of this behaviour, if interessted I can tell you.

bug#16304: Upcoming clang-3.4 apparently miscompiles coreutils.

2013-12-30 Thread Pádraig Brady
On 12/30/2013 12:32 PM, Markus Trippelsdorf wrote: coreutils-8.22 build with clang-3.4 doesn't copy permissions correctly: markus@x4 tmp % touch test1 markus@x4 tmp % chmod 600 test1 markus@x4 tmp % ls -al test1 -rw--- 1 markus markus 0 Dec 30 13:25 test1 markus@x4 tmp %

bug#16245: sha1sum - probable bug.

2013-12-24 Thread Pádraig Brady
tag 16245 notabug close 16245 stop On 12/24/2013 11:11 AM, Dev Rana wrote: I'm not sure if this is a bug or a feature, but it appears that sha1sums of files with control characters in their names, are printed with a \ at the front of the sum. Here are two examples:

bug#16221: Error mounting File System

2013-12-23 Thread Pádraig Brady
tag notabug stop On 12/22/2013 01:22 PM, Jeff wrote: When trying to install Ubuntu 13.10 it gives me this error The install utility is for copying files, and is not used to install the operating system. Please direct your question elsewhere. thanks, Pádraig.

bug#16171: ptx: heap buffer overrun, when run with two file arguments

2013-12-17 Thread Pádraig Brady
On 12/17/2013 02:22 AM, Jim Meyering wrote: Hi, I built like this using just-built 4.9.0 20131216 (but it probably would work as well with 4.8.x): make check AM_CFLAGS='-ggdb3 -static-libasan -fsanitize=address' AM_LDFLAGS='-fsanitize=address -static-libasan -lpthread -ldl'

bug#16122: Typo in numfmt-invocation

2013-12-12 Thread Pádraig Brady
On 12/12/2013 09:57 AM, Tiger Lee wrote: Hi, I found a typo in page ' http://www.gnu.org/software/coreutils/manual/html_node/numfmt-invocation.html'. 'nunfmt' should be 'numfmt' in '4.2.3 Examples of using numfmt'. Fixed with:

bug#16123: please report

2013-12-12 Thread Pádraig Brady
On 12/12/2013 12:02 PM, Mark Menzel wrote: tail: unrecognized file system type 0xf2f52010 for '/var/lib/privoxy/log/logfile'. please report this to bug-coreutils@gnu.org. reverting to polling f2fs is already recognized in trunk and will be included in the soon to be released 8.22 thanks,

bug#15173: [PATCH] cp: with --link always use linkat() if available

2013-12-12 Thread Pádraig Brady
On 12/09/2013 02:24 AM, Pádraig Brady wrote: Sorry if you get multiple copies of this. The test for this is failing on solaris 10 (NFS) It does seem that hardlinks to symlinks are supported: $ touch tfile $ ln -s tfile tlink $ src/ln -L tlink tlink-ln-L $ src/ln -P tlink tlink-ln-P

bug#15173: [PATCH] cp: with --link always use linkat() if available

2013-12-12 Thread Pádraig Brady
So while the above patch is probably correct, it's slightly risky at this stage before a release. Also the benefits are minimal as the existing symlink to symlink emulation should be fine on the mentioned systems. Therefore I'll go with the attached patch which fixes the test to run on all

bug#15173: [PATCH] cp: with --link always use linkat() if available

2013-12-12 Thread Pádraig Brady
On 12/13/2013 12:51 AM, Bernhard Voelker wrote: On 12/13/2013 12:11 AM, Pádraig Brady wrote: So while the above patch is probably correct, it's slightly risky at this stage before a release. Also the benefits are minimal as the existing symlink to symlink emulation should be fine

bug#16094: bug: cp/mv cannot copy/move a file's extended attrs if they start with 'security'

2013-12-10 Thread Pádraig Brady
On 12/09/2013 11:15 PM, Linda Walsh wrote: On 12/9/2013 2:24 PM, Pádraig Brady wrote: So what's up with this? Shouldn't the NTACL be able to be stored/moved with the file? This would be security policy enforced by the system I suspect. I.E. mv is not filtering these explicitly

bug#16095: Problem with --files0-from option

2013-12-10 Thread Pádraig Brady
On 12/09/2013 10:21 PM, Pádraig Brady wrote: tag 16095 notabug stop On 12/09/2013 09:09 PM, aroc...@vex.net wrote: The --files0-from option appears to generate a spurious last iteration. E.g. $ wc --files0-from=file_lis 20 51 343 nyi 25 88 526 parser 6 8 64 rx wc

bug#16095: Problem with --files0-from option

2013-12-09 Thread Pádraig Brady
tag 16095 notabug stop On 12/09/2013 09:09 PM, aroc...@vex.net wrote: The --files0-from option appears to generate a spurious last iteration. E.g. $ wc --files0-from=file_lis 20 51 343 nyi 25 88 526 parser 6 8 64 rx wc: # These lines appear to be bogus

bug#16094: bug: cp/mv cannot copy/move a file's extended attrs if they start with 'security'

2013-12-09 Thread Pádraig Brady
tag 16094 notabug stop On 12/09/2013 08:09 PM, Linda Walsh wrote: I saved a file to my home directory on linux via windows. I wanted to move it to /tmp. I got: mv /home/law/tmp/oVars.pm /tmp mv: setting attribute ‘security.NTACL’ for ‘security.NTACL’: Operation not permitted So

bug#15173: [cp] --link overrides dereference settings

2013-12-08 Thread Pádraig Brady
Sorry if you get multiple copies of this. The test for this is failing on solaris 10 (NFS) It does seem that hardlinks to symlinks are supported: $ touch tfile $ ln -s tfile tlink $ src/ln -L tlink tlink-ln-L $ src/ln -P tlink tlink-ln-P $ src/ln tlink tlink-ln $ ls -li tfile tlink* 8550

bug#16075: ls/stat-free-color.sh fails on AArch64 architecture

2013-12-07 Thread Pádraig Brady
On 12/06/2013 09:12 PM, Pádraig Brady wrote: On 12/06/2013 08:58 PM, Bernhard Voelker wrote: On 12/06/2013 06:45 PM, Pádraig Brady wrote: Even at that the test is still brittle, as the guard only checks that `strace -e stat` works. Also it's conceivable that on some edge cases there may

bug#16075: ls/stat-free-color.sh fails on AArch64 architecture

2013-12-06 Thread Pádraig Brady
On 12/06/2013 04:48 PM, Bernhard Voelker wrote: On 12/06/2013 04:50 PM, Marcin Juszkiewicz wrote: Test checks for use of stat,lstat,stat64,lstat64 syscalls. But on AArch64 it is using statfs64 and newfstatat calls so test fails. log and log-help attached Commands used: strace -o log ls

bug#16075: ls/stat-free-color.sh fails on AArch64 architecture

2013-12-06 Thread Pádraig Brady
On 12/06/2013 05:20 PM, Pádraig Brady wrote: On 12/06/2013 04:48 PM, Bernhard Voelker wrote: On 12/06/2013 04:50 PM, Marcin Juszkiewicz wrote: Test checks for use of stat,lstat,stat64,lstat64 syscalls. But on AArch64 it is using statfs64 and newfstatat calls so test fails. log and log-help

bug#16061: Error in the message for src/shuf.c:73 in 8.22-pre3

2013-12-06 Thread Pádraig Brady
On 12/06/2013 05:57 PM, Paul Eggert wrote: On 12/05/2013 04:15 PM, Bernhard Voelker wrote: BTW: What was the reason to default n=1 with -r anyway? There is no reason, and I see that I should have reviewed the --repetition patch better. Let's change the default back to infinity, which is

bug#16061: Error in the message for src/shuf.c:73 in 8.22-pre3

2013-12-06 Thread Pádraig Brady
On 12/06/2013 07:26 PM, Bernhard Voelker wrote: On 12/06/2013 06:57 PM, Paul Eggert wrote: Here's a patch, which I've taken the liberty of pushing. Thanks, I'm fine with this behavior. Minor nit: sc_long_lines is triggered. BTW: I noticed another tiny flaw in the test (not related to

bug#16080: Unrecognized file system type 0x2fc12fc1

2013-12-06 Thread Pádraig Brady
unarchive 12301 forcemerge 16080 12301 stop On 12/06/2013 05:22 PM, G McAlister wrote: tail: unrecognized file system type 0x2fc12fc1 for â/repo/log/suse13.1u-20131206â. please report this to bug-coreutils@gnu.org. reverting to polling The filesystem that I’m using is ZFS on Linux release

bug#16075: ls/stat-free-color.sh fails on AArch64 architecture

2013-12-06 Thread Pádraig Brady
On 12/06/2013 06:40 PM, Marcin Juszkiewicz wrote: W dniu 06.12.2013 18:20, Pádraig Brady pisze: Also Marcin, could you try out the latest snapshot (which will also need the patch applied). It has another aarch64 specific patch included, and it would be great to verify it on this platform

bug#16075: ls/stat-free-color.sh fails on AArch64 architecture

2013-12-06 Thread Pádraig Brady
On 12/06/2013 08:58 PM, Bernhard Voelker wrote: On 12/06/2013 06:45 PM, Pádraig Brady wrote: Even at that the test is still brittle, as the guard only checks that `strace -e stat` works. Also it's conceivable that on some edge cases there may be more than one stat call used in this case

bug#16061: Error in the message for src/shuf.c:73 in 8.22-pre3

2013-12-05 Thread Pádraig Brady
On 12/05/2013 08:54 PM, Philipp Thomas wrote: The description for the -r option for shuf in 8.22-pre3 reads: -r, --repetitions output COUNT items, allowing repetition.\n -n 1 is implied if not specified.\n Which is confusing as to what COUNT relates

bug#16061: Error in the message for src/shuf.c:73 in 8.22-pre3

2013-12-05 Thread Pádraig Brady
On 12/06/2013 12:15 AM, Bernhard Voelker wrote: On 12/06/2013 12:37 AM, Pádraig Brady wrote: diff --git a/src/shuf.c b/src/shuf.c index f7fc936..4d0ae90 100644 --- a/src/shuf.c +++ b/src/shuf.c @@ -76,8 +76,8 @@ Write a random permutation of the input lines to standard output.\n\ -n

bug#16061: Error in the message for src/shuf.c:73 in 8.22-pre3

2013-12-05 Thread Pádraig Brady
On 12/06/2013 01:36 AM, Bernhard Voelker wrote: On 12/06/2013 02:26 AM, Bernhard Voelker wrote: On 12/06/2013 02:13 AM, Pádraig Brady wrote: I suppose we could make -r require that -n is specified, but I'm not sure. Regarding this in the above context - no, because then you would have

bug#15992: 'ls' ignores term capabilities when generating color.

2013-11-28 Thread Pádraig Brady
On 11/28/2013 08:31 PM, Linda Walsh wrote: I logged in on a *dumb* terminal and did an 'ls'. Rather than a file list, I got: \x1b[00;32mwpad.dat\x1b[0m* \x1b[00mwpad_socks.dat\x1b[0m \x1b[00mwuredir.xml\x1b[0m \x1b[00mx.c\x1b[0m \x1b[00mx.c.orig\x1b[0m \x1b[00;32mx1\x1b[0m*

bug#15926: RFE: unlink command already uses 'unlink' call; make 'rm' use 'remove' call

2013-11-28 Thread Pádraig Brady
On 11/28/2013 12:14 AM, Bernhard Voelker wrote: On 11/27/2013 04:14 AM, Pádraig Brady wrote: On 11/26/2013 11:08 PM, Bernhard Voelker wrote: +#--- +# Exercise rm -r / without and with the --preserve-root option

bug#15970: [Bug-tar] Crash in gettext() after fork() on Mac OS X

2013-11-27 Thread Pádraig Brady
On 11/27/2013 02:38 PM, Jack Howarth wrote: On Wed, Nov 27, 2013 at 01:25:52AM +, Pádraig Brady wrote: On 11/26/2013 10:09 PM, Jim Meyering wrote: Hi Pádraig, Thanks for dealing with that. Your patch looks correct. Did you consider using inttostr in place of that first part

bug#15970: [Bug-tar] Crash in gettext() after fork() on Mac OS X

2013-11-26 Thread Pádraig Brady
On 11/26/2013 04:55 AM, Paul Eggert wrote: Pádraig Brady wrote: How about the attached instead that just uses a somewhat degraded but simpler error() equivalent. That looks safe, though it could be simplified: use inttostr instead of repeating its body, Hah, I was thinking this must

bug#15970: [Bug-tar] bug#15970: Crash in gettext() after fork() on Mac OS X

2013-11-26 Thread Pádraig Brady
On 11/26/2013 10:53 AM, Joerg Schilling wrote: Are you using ignore_value because of the gcc bug that ignores the official method to tell that the return code is ignored intentionally: (void) write(fd, buf, len); Right:

bug#15970: [Bug-tar] Crash in gettext() after fork() on Mac OS X

2013-11-26 Thread Pádraig Brady
On 11/26/2013 10:09 PM, Jim Meyering wrote: Hi Pádraig, Thanks for dealing with that. Your patch looks correct. Did you consider using inttostr in place of that first part of async_safe_error? Paul suggested that too and I've pushed an updated patch now. I'd searched for INTTOSTR without

bug#15926: RFE: unlink command already uses 'unlink' call; make 'rm' use 'remove' call

2013-11-26 Thread Pádraig Brady
On 11/26/2013 11:08 PM, Bernhard Voelker wrote: +#--- +# Exercise rm -r / without and with the --preserve-root option. +# Also exercise the synonyms '///' and '' which would normally go into +# the 'synonyms' test

bug#15970: [Bug-tar] Crash in gettext() after fork() on Mac OS X

2013-11-25 Thread Pádraig Brady
On 11/25/2013 12:10 AM, Paul Eggert wrote: Eric Blake wrote: I bet coreutils' sort has a similar bug [Adding bug-coreutils to the CC:.] Referencing the original coreutils thread from the new bug: http://lists.gnu.org/archive/html/coreutils/2013-11/msg00083.html Coreutils 'sort' runs into

bug#15926: RFE: unlink command already uses 'unlink' call; make 'rm' use 'remove' call

2013-11-24 Thread Pádraig Brady
On 11/25/2013 12:15 AM, Bernhard Voelker wrote: On 11/23/2013 02:30 AM, Pádraig Brady wrote: On 11/23/2013 01:02 AM, Bernhard Voelker wrote: From a87e3d0a8417648e65ee077ca6f70d5d19fa757a Mon Sep 17 00:00:00 2001 From: Bernhard Voelker m...@bernhard-voelker.de Date: Sat, 23 Nov 2013 01:55:36

bug#15926: RFE: unlink command already uses 'unlink' call; make 'rm' use 'remove' call

2013-11-21 Thread Pádraig Brady
On 11/21/2013 12:03 AM, Bernhard Voelker wrote: if (dot_or_dotdot (last_component (ent-fts_accpath))) { - error (0, 0, _(cannot remove directory: %s), - quote (ent-fts_path)); + error (0, 0, +

bug#15926: RFE: unlink command already uses 'unlink' call; make 'rm' use 'remove' call

2013-11-21 Thread Pádraig Brady
On 11/21/2013 07:12 AM, Bernhard Voelker wrote: On 11/21/2013 03:07 AM, Eric Blake wrote: On 11/20/2013 05:03 PM, Bernhard Voelker wrote: What about the following? $ src/rm -r src/. src/rm: refusing to remove '.' or '..' directory: skipping 'src/.' That helps. Thanks, I'll push it

bug#15926: RFE: unlink command already uses 'unlink' call; make 'rm' use 'remove' call

2013-11-21 Thread Pádraig Brady
On 11/21/2013 01:39 PM, Eric Blake wrote: On 11/21/2013 12:12 AM, Bernhard Voelker wrote: Admittedly, compared to the academic question behind --no-preserve-root (which is like what happens to me when the globe under my feet disappears?), there may be more real-world reasons to remove ..

bug#15926: RFE: unlink command already uses 'unlink' call; make 'rm' use 'remove' call

2013-11-21 Thread Pádraig Brady
On 11/21/2013 05:39 PM, Eric Blake wrote: On 11/21/2013 10:38 AM, Eric Blake wrote: On 11/21/2013 10:35 AM, Pádraig Brady wrote: as I don't see it as specific to rm. I.E. other tools like chmod etc would have the same requirement, and they might be handled with various shell globbing

bug#15926: RFE: unlink command already uses 'unlink' call; make 'rm' use 'remove' call

2013-11-19 Thread Pádraig Brady
tag 15926 notabug close 15926 stop On 11/19/2013 11:56 AM, Linda Walsh wrote: Since there is already an unlink command that corresponds to unlinking a file, but there seems to be no command corresponding to the POSIX remove command, it seems upgrading 'rm' to use the 'remove' POSIX call would

bug#15869: Bug in seq command --separator option

2013-11-12 Thread Pádraig Brady
forcemerge 13227 13493 14584 15869 stop On 11/12/2013 08:01 AM, James Bowlin wrote: I'm using seq from the coreutils-8.20 package on Gentoo Linux. Here is the incorrect output $ seq -s, 1 5 1 2,3,4,5,% The newline comes after the 1 instead of after the 5. The % indicates

bug#15858: my ls command is not working.In /bin ls commnd is there but nothing waritten on it

2013-11-10 Thread Pádraig Brady
tag 15858 notabug close 15858 stop That probably implies there are no files in your home directory. You could confirm by listing another directory like: ls /etc thanks, Pádraig.

bug#15835: [PATCH] chmod: change in the inode's st_ctime

2013-11-08 Thread Pádraig Brady
tag 15835 wontfix close 15835 stop On 11/08/2013 01:07 PM, Guilherme de Almeida Suckevicz wrote: Hello, I saw this issue on TODO file: Modify chmod so that it does not change an inode's st_ctime when the selected operation would have no other effect. First suggested by Hans Ecke

<    9   10   11   12   13   14   15   16   17   18   >