Re: Tomb 2.6+dfsg1-1 not migrated to testing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi SZ, yes, it migrated about 11 hours after my mail, seems I was to unpatient. :-) Sven Am Dienstag, den 20.08.2019, 13:38 +0800 schrieb SZ Lin (林上智): > 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] > https://tracker.debian.org/news/1056037/tomb-26dfsg1-1-migrated-to-testing/ > > > Sven > > > > Am Sonntag, den 18.08.2019, 19:33 +0100 schrieb Samuel Henrique: > > > 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, > > > > > -BEGIN PGP SIGNATURE- > > > > iQIzBAEBCgAdFiEEPfXoqkP8n9/QhvGVrfUO2vit1YUFAl1a4UoACgkQrfUO2vit > > 1YUODQ/+KCI12XIMn2Ri5jFyM+t/weA4Z3AAYgAGwp5eWlF6L/QtGQ2kXPwk8GpB > > TGN5f4Olu+YEbwosAAkHbshIr2iG1Trak+Cubz04LCHRZwDSyWedestHwP8GuM00 > > jeRIfPFs0C3vhO8QVmFt2aZOH5/wRRDK04/WF0KD0sSRMBbcUrEiH0VHsEYNFBaE > > zuKQqDzpjPyBB48iTQup/L5fL6WzzSJpjcJVv6VaCkOJUpkghq+ble0q0Pw1uLoJ > > cBWaKTfO+R/t8WR5/ZTdCu9IKFIt+g4JumXU2EBatWIO5RK5H7GIorneyP0YDNKE > > XepucOR6h2Oas4jHWdfpAAGjB0ZTLCAKMqWVrhlT9WumWplY7UTjQBjTAUdH5zQt > > A9QU4ATSrz8msQcoPtYSg06tj9WzB6TCh5KjXnJCol8AmiOT5Gr6bGRUM5Ek89Qn > > Jjdm/WVSfE53ICAy+ghLqQudwocGpN7HNnANpct7Oc7xruSfNta5FU5Tsyz49py4 > > SdgHb9dc+z+18/RB8ihFc9/lNWwAHQVUk7cvPOAVqeu09IQz3aOGTPgpoXRs7s/F > > YDnPYc5Mj5E0diejDCbjK3A4flGpB8JVCVaqAR1DgSPdujdW5X453KpYiwazYtYR > > K5G1nnzSOl+IUZSPxO4EbDWapB42qNWmTVNBS0/Tur0ezPeKgQk= > > =VGf8 > > -END PGP SIGNATURE- > > > > -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEPfXoqkP8n9/QhvGVrfUO2vit1YUFAl1cM90ACgkQrfUO2vit 1YXUWw/8CdRXXQ3h5XQWBmAwrqys15PbQn+7KzZz3IGAy1uAm9xk4GR8VRE5B2rL dsFTA8CYlhtsFAdwyJGSp8WHFrCCYEXAK37gMawem6X66WnVqieJ1vakGf4mm7bq SdT9laWQoAzHPqUF8Vpwa2qwqKdKRQ8XHOFoXTC4c3YuXSgJG2yl35hY0yrsl3xG A9eVGH3oUTyN0VAOjLRVKQmKlBcMI82YjceN1ZQUr1DMId3kUq1A0+OQ0F05Hd0W pEPbdzFM+GoxFTyLqitwE8BJNuXR2kieDZtLWGKDSV+Gf2Pc++Zc1GwpyNrfpb7C U/jAURXPHpmbHqdhE9ji44pdoVGus4B0zSM9w9IWCt0838uQ+yIgrxuEFJuVUymI l/C4imPsTU7hBcAdLQv5uJWPovIRm2agxQ1tC+IE6deJqn/9NDzlforjjJuWQN2/ CQWzv6p8iRHX3hIu3lP/aduBc82kI4ISmNDDTisitPjrlPrUL42vgksMGiZBWHlG pTax4sAIFZYLMxveeW09Ly3JaMLfDJzHJCPHOyMaX2KWol2/Un+ModGuacVIZ8VL MCNY2r7agZLgjhRmWThXSq+DNpRITlhZKoHspaUL6RrCdTiNYbkZxUzjaRRatGya uFLX360LUYztB+o7zxB4Jvv1cIqjfMIN3sd1jbbQK0eF24eo/Ts= =kss9 -END PGP SIGNATURE-
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] https://tracker.debian.org/news/1056037/tomb-26dfsg1-1-migrated-to-testing/ > > Sven > > Am Sonntag, den 18.08.2019, 19:33 +0100 schrieb Samuel Henrique: > > 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, > > > -BEGIN PGP SIGNATURE- > > iQIzBAEBCgAdFiEEPfXoqkP8n9/QhvGVrfUO2vit1YUFAl1a4UoACgkQrfUO2vit > 1YUODQ/+KCI12XIMn2Ri5jFyM+t/weA4Z3AAYgAGwp5eWlF6L/QtGQ2kXPwk8GpB > TGN5f4Olu+YEbwosAAkHbshIr2iG1Trak+Cubz04LCHRZwDSyWedestHwP8GuM00 > jeRIfPFs0C3vhO8QVmFt2aZOH5/wRRDK04/WF0KD0sSRMBbcUrEiH0VHsEYNFBaE > zuKQqDzpjPyBB48iTQup/L5fL6WzzSJpjcJVv6VaCkOJUpkghq+ble0q0Pw1uLoJ > cBWaKTfO+R/t8WR5/ZTdCu9IKFIt+g4JumXU2EBatWIO5RK5H7GIorneyP0YDNKE > XepucOR6h2Oas4jHWdfpAAGjB0ZTLCAKMqWVrhlT9WumWplY7UTjQBjTAUdH5zQt > A9QU4ATSrz8msQcoPtYSg06tj9WzB6TCh5KjXnJCol8AmiOT5Gr6bGRUM5Ek89Qn > Jjdm/WVSfE53ICAy+ghLqQudwocGpN7HNnANpct7Oc7xruSfNta5FU5Tsyz49py4 > SdgHb9dc+z+18/RB8ihFc9/lNWwAHQVUk7cvPOAVqeu09IQz3aOGTPgpoXRs7s/F > YDnPYc5Mj5E0diejDCbjK3A4flGpB8JVCVaqAR1DgSPdujdW5X453KpYiwazYtYR > K5G1nnzSOl+IUZSPxO4EbDWapB42qNWmTVNBS0/Tur0ezPeKgQk= > =VGf8 > -END PGP SIGNATURE- >
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 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, > -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEPfXoqkP8n9/QhvGVrfUO2vit1YUFAl1a4UoACgkQrfUO2vit 1YUODQ/+KCI12XIMn2Ri5jFyM+t/weA4Z3AAYgAGwp5eWlF6L/QtGQ2kXPwk8GpB TGN5f4Olu+YEbwosAAkHbshIr2iG1Trak+Cubz04LCHRZwDSyWedestHwP8GuM00 jeRIfPFs0C3vhO8QVmFt2aZOH5/wRRDK04/WF0KD0sSRMBbcUrEiH0VHsEYNFBaE zuKQqDzpjPyBB48iTQup/L5fL6WzzSJpjcJVv6VaCkOJUpkghq+ble0q0Pw1uLoJ cBWaKTfO+R/t8WR5/ZTdCu9IKFIt+g4JumXU2EBatWIO5RK5H7GIorneyP0YDNKE XepucOR6h2Oas4jHWdfpAAGjB0ZTLCAKMqWVrhlT9WumWplY7UTjQBjTAUdH5zQt A9QU4ATSrz8msQcoPtYSg06tj9WzB6TCh5KjXnJCol8AmiOT5Gr6bGRUM5Ek89Qn Jjdm/WVSfE53ICAy+ghLqQudwocGpN7HNnANpct7Oc7xruSfNta5FU5Tsyz49py4 SdgHb9dc+z+18/RB8ihFc9/lNWwAHQVUk7cvPOAVqeu09IQz3aOGTPgpoXRs7s/F YDnPYc5Mj5E0diejDCbjK3A4flGpB8JVCVaqAR1DgSPdujdW5X453KpYiwazYtYR K5G1nnzSOl+IUZSPxO4EbDWapB42qNWmTVNBS0/Tur0ezPeKgQk= =VGf8 -END PGP SIGNATURE-
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 [1] https://tracker.debian.org/pkg/tomb -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEPfXoqkP8n9/QhvGVrfUO2vit1YUFAl1ZGWMACgkQrfUO2vit 1YVB8BAAikKmblAJH3AllcNjE2/8dZNCK1oa3tUjJjCCTb5NXtOzBr6cMR4X4gr2 Fs5odDWKBLzqmW80LTJryDVyYiSqPV4/dG0RIJ5KjcsGXDrmPBYON9CdkcVya5VI vnZ/d29Z6AgWMXo08J3Z3CvL1+PShJkr89S78QMo5ipn2QMVU0m4ObwTrPgaJO3S bwTgpiB9o1EjLT/4dx4vL45vS+7UBeleSdkn08exOOHGWj06aIS5tDBQ8USpzHOD ONO877pPUxUgdesYQ2ZJ5FC51jRFfSYjkPnKRjGfmgVsolb0Zby0zXFzBQ/UnGFC 1uQR9ENRizrqEzyNagTzW7aOdRKis65R9JWSkuhSRIH2zEGorwsMtYW6DnhhT3U6 ce44jqarak52mjxKa77uxH3NF5APbgaq7HlE6fjX2nJzdN/SYN7dbOAEahxZvHSi QFilpJChfaVogQhhqtabPB3U39WfsgptW7TLuTIQuZ94/vO6zK0ZhUXpxaCYMWca LK1egwuNaPBpxrpZo+6bRVxY0VbG3MZbU/6hFaZj7tEZJPoyzZ3KGxd9gCk6FOja ZEfZ7DWU37EgHJ2uoFgeuw0LKQ3fwbpbFPu+WbUipYxDQBJ01XkuoFj6HqTgzPrO cWauU/JNtna0MXojVjtC7TRKcWhR1HWIKidwCoju983lnmfuIS8= =hjEO -END PGP SIGNATURE-
