On Thursday 19 June 2008 03:42:13 am Jim Meyering wrote: [...] > >> FAIL: misc/runcon-no-reorder.log (exit: 1) > >> ========================================== > >> ... > > > > As expected, this one still triggers. > > I've changed the test to also accept that diagnostic. > Patch below.
Patch verified, mock build doesn't fail on this test now. [...] > >> FAIL: cp/preserve-gid.log (exit: 1) > >> =================================== > >> ... > >> This one was trickier. I think it must be the case that > >> root's primary group is 103. The test requires that it be 0. > >> Can you confirm? (i.e., run id -g -- or better, id -a to get all of > >> them) I'll either adapt the test or make it skip in that case. > > > > Ah, here we go... In this case, I'm doing a build in a mock chroot, as > > the user 'mockbuild', who (within the chroot) has a uid of 0, gid of 101: > > > > mockbuild::0:101::/builddir:/bin/bash > > Good. That's easy to accommodate. This one also no longer triggers. Excellent, now its time to back out the utimens{,at}() work-arounds and see what else we can see... -- Jarod Wilson [EMAIL PROTECTED] _______________________________________________ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils