Hi, On Wed, 18 Jul 2018, Axel Beckert wrote: > > Axel mentioned failed bin-nmu but it looks like the bin-nmu worked: > > https://buildd.debian.org/status/fetch.php?pkg=wcc&arch=amd64&ver=0.0.2%2Bdfsg-3%2Bb2&stamp=1531313043&raw=0 > > Sorry, I deduced that from "uninstallable + FTBFS". > > > I downgraded the bug for now. > > Fair enough, but it's still uninstallable, even despite that BinNMU: > > The following packages have unmet dependencies: > wcc : Depends: libbinutils (< 2.30.90.20180711) but 2.31-1 is to be installed > E: Unable to correct problems, you have held broken packages. > > So raising to RC again. > > From my point of view this means that either another BinNMU was > necessary since the previous BinNMU, but was not yet triggered, or > something else is broken in the package.
Yeah, a new binutils got uploaded multiple times in the last days. Matthias, I don't know how many reverse deps there are but given that you have so strict dependencies on libbinutils, you have to handle a small transition for every upload of a new upstream release. For now I requested a bin-nmu in #904073. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/
