On 2015-06-09 21:56, Micha Lenk wrote: > Hi Emilio, > > Am 04.06.2015 um 17:32 schrieb Emilio Pozuelo Monfort: >>> Let us know once the package has been through NEW. >> >> That's happened. You can go ahead with an upload to unstable, followed by >> severity:serious bugs against the rdeps to update their build-dependency on >> libaqbanking-dev. Please make those bugs block this one. > > Done. > > Meanwhile all rdeps have successfully been rebuilt. However the > transition tracker still considers libaqbanking itself bad (i.e. renders > it red on > https://release.debian.org/transitions/html/auto-libaqbanking.html). > Why? Does it maybe need a britney hint? >
Hi Micha, Thanks for following up. It measures all versions of libaqbanking in unstable including the old "SONAME" versions: * libaqbanking34 * libaqbanking34-dbg * libaqbanking34-dev * libaqbanking34-plugins Which are technically still present in unstable. These will need to be decrufted before the tracker will turn green and also before the package will be allowed to migrate. Mind you, decrufting generally only occurs at this point to avoid breaking packages in unstable. Decrufting is also something the FTP masters and accordingly is unrelated to Britney. > Is there anything left I can help with regarding the completion of this > transition? > > Cheers, > Micha > > At this point, no. We will need the FTP masters to decruft the binaries before the transition can continue. After that has happened, the transition /usually/ finishes on its own. Thanks, ~Niels -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
