On Tue, 9 Feb 2016 22:52:53 +0100
Andreas Müller wrote:
> Are user IDs affected? If yes there would be a chance to reduce loads
> of host contamination warnings..
They could be in some cases, especially with build history. In most cases,
packages were fine, but reporting could be wrong. But basi
On 2/9/16 3:52 PM, Andreas Müller wrote:
> On Tue, Feb 9, 2016 at 9:11 PM, Mark Hatle wrote:
>> Once the corresponding tarball is available, this should likely be
>> backported/merged to Jethro and Fido as well.
>>
>> Everything remains compatible, but it does fix a subtle race condition that
>>
On Tue, Feb 9, 2016 at 9:11 PM, Mark Hatle wrote:
> Once the corresponding tarball is available, this should likely be
> backported/merged to Jethro and Fido as well.
>
> Everything remains compatible, but it does fix a subtle race condition that
> can
> lead to files under pseudo control inherit
On Tue, 2016-02-09 at 15:16 -0600, Peter Seebach wrote:
> On Tue, 9 Feb 2016 14:11:09 -0600
> Mark Hatle wrote:
>
> > Everything remains compatible, but it does fix a subtle race
> > condition that can
> > lead to files under pseudo control inheriting their host system
> > permissions.
> >
> > S
On Tue, 9 Feb 2016 14:11:09 -0600
Mark Hatle wrote:
> Everything remains compatible, but it does fix a subtle race condition that
> can
> lead to files under pseudo control inheriting their host system permissions.
>
> See bug 9031 for more details.
For reference, the thing which exposed the c
Once the corresponding tarball is available, this should likely be
backported/merged to Jethro and Fido as well.
Everything remains compatible, but it does fix a subtle race condition that can
lead to files under pseudo control inheriting their host system permissions.
See bug 9031 for more detai
