bug-coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: coreutils-8.2 bug-fix-only release coming soon


From: Jim Meyering
Subject: Re: coreutils-8.2 bug-fix-only release coming soon
Date: Thu, 07 Jan 2010 14:34:23 +0100

Ludovic Courtès wrote:
> Hi Jim,
> Jim Meyering <address@hidden> writes:
>> Ludovic Courtès wrote:
>>> Jim Meyering <address@hidden> writes:
>>>
>>>>> Regarding ‘chgrp/basic’, the test finds groups='30000 65534'.  However,
>>>>> 65534 corresponds to ‘nogroup’.  (The build process runs under a special
>>>>> user, typically:
>>>>>
>>>>>   $ id nixbld1
>>>>>   uid=30001(nixbld1) gid=65534(nogroup) 
>>>>> groups=30000(nixbld),65534(nogroup)
>>>>
>>>> It looks like there is something different
>>>> about NixOS, since normally when a user U is a member
>>>> of a group G, and U runs "chown U:G file", that command succeeds.
>>>
>>> This has now been fixed in NixOS by having build users belong to the
>>> ‘nixbld’ group and no supplementary groups.
>>>
>>> The test suite passes on GNU/Linux
>>
>> Great!
>> Is there a way I can be notified of each change in pass/fail state?
>
> Yes, by email.  Hydra email notification has been improved recently:
>
>   - Notifications are only sent when the package’s status changes from
>     SUCCEEDED to FAILED and vice versa.
>
>   - Messages for failed builds include the last 50 lines of the build
>     log.
>
> Other than that, they look like those found here:
>
>   http://lists.gnu.org/archive/html/build-inetutils/2010-01/threads.html
>
> The Inetutils folks created a ‘build-inetutils’ mailing list to receive
> such messages.  Perhaps something similar could be done for Coreutils?
>
> Or we can use ‘bug-coreutils’ for that purpose and make sure it doesn’t
> flood the list.

That sounds perfect.

I'd like to follow it, but would like to get a feel for the volume
before either creating a new list or imposing it on bug-coreutils.
Can I (and maybe a few other people) subscribe individually for now?

Thank you!




reply via email to

[Prev in Thread] Current Thread [Next in Thread]