On Mon, Apr 16, 2012 at 08:14:04PM +0100, Adam D. Barratt wrote: > On Tue, 2012-03-27 at 14:48 +0200, Michael Vogt wrote: > > We need to make sure that libept gets rebuild right after apt is ready > > to ensure that its updated for the new apt. Ideally we take the > > version in experimental that encodes the apt ABI version in its soname > > to ensure that its clear that while libept did not change ABI it > > indirectly did because of the libapt ABI break. > > Well, libept got re-uploaded, but with nothing in its build-depends that > forced the new version of apt in to the chroots, so it just got rebuilt > against apt 0.8 again - toolchain and similar packages like apt are > always installed in buildd chroots, so they don't get automatically > upgraded. I've poked a couple of the buildd admins about how they'd > like to handle the upgrades. In the meantime, I'm not scheduling any > more binNMUs.
Oh, thanks! So what should I do? Upload libept with the updated build-dependency? Will that be fine? > It looks like your python-apt upload is also FTBFS everywhere, with test > suite failures - again, they got built against apt 0.8. Same for python-apt I assume? Just a updated build-dependency? Thanks, Michael -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120416192326.GU3104@localhost