> 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 to do, though at some times (perhaps now) it might interfere with an automatic migration to testing. 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://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797761 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797762 Perhaps they need a better explanation. Should such bugs be for the misbuilt package, or for release.debian.org, do you think? Edmund
