Bug#339136: stat behavior change

2005-11-25 Thread Junichi Uekawa
Hi, For the record, in the case of cowdancer; the solution was system("find . -xdev -print0 -type f | xargs -0 stat --format '%d %i ' > .ilist"); to add a space after '%i' in '%d %i', so that there is a whitespace for later consumption. regards, junichi -- [EMAIL PROTECTED],net

Bug#339136: stat behavior change

2005-11-25 Thread Junichi Uekawa
Hi, > >However, from an upstream software POV, this is > >a nightmare. > >I'll need to check for stat version before giving it > >a format string, possibly by checking it in configure.ac > > Yeah, the problem is that if upstream doesn't acknowledge this as an > issue you'll either be compabtibl

Bug#339136: stat behavior change

2005-11-23 Thread Michael Stone
On Wed, Nov 23, 2005 at 01:24:08PM +0900, Junichi Uekawa wrote: However, from an upstream software POV, this is a nightmare. I'll need to check for stat version before giving it a format string, possibly by checking it in configure.ac Yeah, the problem is that if upstream doesn't acknowledge t

Bug#339136: stat behavior change

2005-11-22 Thread Jim Meyering
Junichi Uekawa <[EMAIL PROTECTED]> wrote: > reopen 339136 > retitle 339136 stat --format behavior change with default newline > thanks ... > Older (sarge system): ... > stat * --format "%d %i:"|tr : '\n' | head > 2054 21186142 > 2054 21186136 > 2054 7831563 > > Newer(current sid): ... > $ stat * --

Bug#339136: stat behavior change

2005-11-22 Thread Junichi Uekawa
reopen 339136 retitle 339136 stat --format behavior change with default newline thanks Hi, I've noticed that it's also affecting cowdancer. I'm planning on getting a workaround and fixing it in 0.7. However, from an upstream software POV, this is a nightmare. I'll need to check for stat version