Hrm, that seems like I very likely passed the wrong thing to sbuild's -d option :-/ I'm not sure what the correct fix is, uploading an epoch'd version to wheezy backports would then require an epoch everywhere else, but uploading a properly built 0.5.4-5 to wheezy-backports would be a violation of the rules for foo-backports I think. I've copied d-backports@ and ftp-master@ for advise. TL;DR: I seem to have uploaded a package built (and intended) for jessie-backports into wheezy-backports by mistake, it is fortunately uninstallable in that context. Is it possible to simply remove the incorrect package from wheezy -backports? Ian. On Sun, 2015-12-20 at 10:50 -0800, Martin Michlmayr wrote: > Hi Ted, > > You just found a problem. Ian Campbell recently uploaded a qcontrol > backport for *jessie* but it seems this ended up in > *wheezy*-backports. > > I've copied Ian. > > > Distribution: wheezy-backports > ^^^^^^^^^ > >Changes: > > qcontrol (0.5.4-5~bpo8+1) jessie-backports; urgency=medium > > . > > * Rebuild for jessie-backports. > > I'm not quite sure how that happened since the control file lists. > jessie-backports > > > * Ted To <ted@theo.to> [2015-12-20 13:10]: > > Hi Martin, > > > > Recently there is a qcontrol upgrade available but it cannot be > installed > > because qcontrol requires libc6 >= 2.15. > > > > qcontrol : Depends: libc6 (>= 2.15) but 2.13-38+deb7u8 is to be > installed > > > > What is the appropriate workaround? > > > > Thanks, > > Ted To >
Attachment:
signature.asc
Description: This is a digitally signed message part