+++ Edmund Grimley Evans [2015-09-04 19:19 +0100]:
> I've already filed a few individual bugs, for cases that seem
> particularly pernicious, but with no effect, so far:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795288
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797758
> https
> I think we should look through the list and actively bin-nmu anything
> that looks like it might be affected, to avoid knock-on breakage.
So should we file individual bugs, or just tell someone?
I would have thought that at most times a binNMU on a single
architecture would be a harmless thing
+++ Edmund Grimley Evans [2015-09-04 11:56 +0100]:
> The buildd arm-arm-03 failed to update its chroot on Aug 2. As a
> result, in the period Aug 3-9 it built various packages using g++-4.9
> when people were expecting it to use g++-5. So there are library
> packages, such as libsigc++-2.0-0v5, whi
The buildd arm-arm-03 failed to update its chroot on Aug 2. As a
result, in the period Aug 3-9 it built various packages using g++-4.9
when people were expecting it to use g++-5. So there are library
packages, such as libsigc++-2.0-0v5, which are intended to handle the
transition to GCC 5 but were
4 matches
Mail list logo
