Steve Langasek <[email protected]> writes:
> Hi Roger,
>
> On Sat, Jun 11, 2011 at 02:02:52AM +0100, Roger Leigh wrote:
>> Because unstable was changing between the rebuilds, some of the
>> failures are likely due to churn, including multiarch work, so a
>> failure does not necessarily implicate the patch being tested.
>
> I'm surprised that the build environment was continuing to track updates to
> unstable at this time, as opposed to using a static mirror. That's an
> unfortunate source of noise in the data; how can we get the list of packages
> that failed to build with autodetection that didn't fail with 'debian/rules
> build', to determine if they are indeed false positives?
>
> Thanks,
The build process should pick a source and then build all flavours in
one go. Only then continue with the next source. Sources that FTBFS the
old way could skip all the other flavours.
MfG
Goswin
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]
