bug#13635: Strange ls bug (Combination of -a and --color)

My guess is that 'csf' is readable but not searchable. That would explain your symptoms: $ ls -ld csf dr. 2 eggert eggert 4096 Feb 6 15:31 csf $ ls -ld csf/. ls: cannot access csf/.: Permission denied $ ls --color=always -a csf ls: cannot access csf/.: Permission denied ls: cannot access

bug#13640: Error while compiling: no `doc/perm.texi' target

On Wed, 06 Feb 2013 20:02:31 + P__draig Brady wrote: > That file is already present in the repo and shouldn't need to be built. > http://git.sv.gnu.org/gitweb/?p=coreutils.git;a=blob;f=doc/perm.texi;hb=HEAD > Perhaps you had an issue when cloning the repo? My fault, sorry. Best regards, Co

bug#13409: [patch] make some error messages clearer

On Wed, Feb 6, 2013, at 16:54, Pádraig Brady wrote: > But I'll note that "error reading" and "error writing" are quite > unambiguous and fit well to indicate partial failure of the operation. > If we used "failed to write", then it might imply that nothing was written > etc. To both points: +1.

bug#13640: Error while compiling: no `doc/perm.texi' target

tag 13640 notabug close 13640 stop On 02/06/2013 06:27 PM, Cojocaru Alexandru wrote: I am trying to compile from the git master and I am getting the following error: make[2]: *** No rule to make target `doc/perm.texi', needed by `doc/coreutils.info'. Stop. How to fix it? That file is alre

bug#13640: Error while compiling: no `doc/perm.texi' target

I am trying to compile from the git master and I am getting the following error: make[2]: *** No rule to make target `doc/perm.texi', needed by `doc/coreutils.info'. Stop. How to fix it? Best regards, Cojocaru Alexandru

bug#13638: linux-sort inconsistency

tag 13638 notabug thanks On 02/06/2013 03:49 AM, Knud Arnbjerg Christensen wrote: > Hi > linux-sort inconsistency occours when sorting an alfpha-numeric field, > then the order becomes different depending on if the following field is > numeric (file 1) or alfanumeric (file 2). In case one the len

bug#13638: linux-sort inconsistency

On 02/06/13 02:49, Knud Arnbjerg Christensen wrote: > linux-sort inconsistency occours when sorting an alfpha-numeric field, > then the order becomes different depending on if the following field is > numeric (file 1) or alfanumeric (file 2). In case one the length of the > shorter fields is exte

bug#13638: linux-sort inconsistency

Hi linux-sort inconsistency occours when sorting an alfpha-numeric field, then the order becomes different depending on if the following field is numeric (file 1) or alfanumeric (file 2). In case one the length of the shorter fields is extended by ´zeros´ in case 2 the fields is extended by blank

bug#13409: [patch] make some error messages clearer

On 01/14/2013 09:08 AM, Jim Meyering wrote: Benno Schulenberg wrote: On Fri, Jan 11, 2013, at 8:39, Jim Meyering wrote: wwarn (_("%s: read failed"), src_name); When things go wrong, I would prefer to see a word like "failed", "error", "mistake", "bad", "invalid" or "mayday" at the be

bug#13409: [patch] make some error messages clearer

Pádraig Brady wrote: > On 01/14/2013 09:08 AM, Jim Meyering wrote: >> Benno Schulenberg wrote: >>> On Fri, Jan 11, 2013, at 8:39, Jim Meyering wrote: wwarn (_("%s: read failed"), src_name); >>> >>> When things go wrong, I would prefer to see a word like >>> "failed", "error",

bug#13635: Strange ls bug (Combination of -a and --color)

Joshua Rogers wrote: > Okay, I understand that, but the > > " > > d? ? ? ? ?? . > d? ? ? ? ?? .." > > That is a bug, no? No it isn't. Since ls didn't have permission to search the directory it could not stat those files and therefore could not re

bug#13635: Strange ls bug (Combination of -a and --color)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Okay, I understand that, but the " d? ? ? ? ?? . d? ? ? ? ?? .." That is a bug, no? Thanks *Joshua Rogers* - Retro Game Collector && IT Security Specialist gpg pubkey

bug#13635: Strange ls bug (Combination of -a and --color)

Joshua Rogers wrote: > $ ls -ld csf > drw--- 2 toil toil 4096 2013-02-05 19:26 csf Yes. :-) > So it seems that you may be correct. > That chmod fixes the problem, Yes. You said you rsync'd data from another machine. Was the permissions copied from the remote machine the same there? > But

bug#13635: Strange ls bug (Combination of -a and --color)

Hi Bob, Here is the result of that command; $ ls -ld csf drw--- 2 toil toil 4096 2013-02-05 19:26 csf The result of running it with the trailing / aswell; $ ls -ld csf/ drw--- 2 toil toil 4096 2013-02-05 19:26 csf/ So it seems that you may be correct. That chmod fixes the problem, But

bug#13635: Strange ls bug (Combination of -a and --color)

Joshua Rogers wrote: > I just rsync'd my remote server for backup, and on my local machine I > run the command 'ls -lh csf/' > Well.. Here's the result; > > $ ls -lh csf/ > ls: cannot access csf/.: Permission denied > ls: cannot access csf/..: Permission denied > total 0 > d? ? ? ? ?