Re: Tomb 2.6+dfsg1-1 not migrated to testing

Hi Sven, Sven Geuer 於 2019年8月20日 週二 上午1:51寫道： > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hello Samuel et all, > > it has been built for amd64 by buildd now. Unfortunately it's still not > migrated. > > Any clue? It's already in testing archive [1]. [1]

Re: Tomb 2.6+dfsg1-1 not migrated to testing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello Samuel et all, it has been built for amd64 by buildd now. Unfortunately it's still not migrated. Any clue? Sven Am Sonntag, den 18.08.2019, 19:33 +0100 schrieb Samuel Henrique: > Hello Sven et all, > > After you sent this email somebody

Re: Tomb 2.6+dfsg1-1 not migrated to testing

Hello Sven et all, After you sent this email somebody triggered a binNMU so now it should be all fine. I believe this happened because SZ Lin didn't make a source-only upload, and that is required for the testing migration now. Regards, -- Samuel Henrique

Tomb 2.6+dfsg1-1 not migrated to testing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi SZ, Tomb does not make it into testing, presumably due to "Not built on buildd: arch amd64 binaries uploaded by sz...@cs.nctu.edu.tw" to be found on tracker [1]. How can this be fixed? Is there a way to force buildd to build for amd64? Sven