On 26/08/12 at 16:57 -0400, David Prévot wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> Le 26/08/2012 13:28, Lucas Nussbaum a écrit :
> > On 25/08/12 at 19:11 -0400, David Prévot wrote:
> >> Le 14/08/2012 03:18, Lucas Nussbaum a écrit :
> >>> Source: backbone
> >> […]
> >>> Justification: FTBFS in wheezy on amd64
> >> Actually its an OR dependency:
> >> libnode-uglify | yui-compressor
> > By default, sbuild ignores alternative build-dependencies (a | b)
> Thanks for your quick answer, and thanks Jonas who was even quicker,
> preparing a t-p-u right now.
> >> I've tagged a few FTBFS on wheezy as unreproducible (because I didn't
> >> investigate why it failed ten days ago, or because I couldn't find an
> >> obvious reason), should I simply have closed them?
> > Did you Cc me? I have very little time for Debian recently, but try to
> > keep up with bugmail where I'm Cced.
> No, sorry about that, those were #684833, #684837 and #684860. Cédric
> already looked at the last one with the same result than me, and should
> investigate again soon.
> > Anyway, a good way to make progress is usually to provide a build log,
> > and a diff between my log and your log.
> Thanks for the tip, I'll try to have a second look at the first two,
> following your advice.
OK, the first two look like bugs that will be easier to understand with
a diff (maybe a build-dep that was broken was fixed in the meantime?).
For the third one, I'm a bit more puzzled.
Note that I auto-retry builds before filing, so when I file a bug, it
means that the build failed twice in a row. This does not exclude chroot
configuration issues, or environment issues, but at least excludes all
random/cosmic rays problems.