Re: Understanding what is blocking spamassassin 4.0.0 testing migration

On 2022-12-29 "Adam D. Barratt" wrote: > On Thu, 2022-12-29 at 07:21 +0100, Andreas Metzler wrote: [...] > > removing spamassassin/4.0.0~rc4-1/amd64 from testing makes claws- [...] > That's due to the arch:all build failing, which means there is no > "spamassassin" binary package in unstable

Re: Understanding what is blocking spamassassin 4.0.0 testing migration

Hi Andreas, On 29-12-2022 07:21, Andreas Metzler wrote: I do not understand why spamassassin 4.0.0 does not prpagate to testing. Tracker/excuses https://qa.debian.org/excuses.php?package=spamassassin says: Issues preventing migration: [...] removing spamassassin/4.0.0~rc4-1/amd64 from testi

Re: Understanding what is blocking spamassassin 4.0.0 testing migration

Hi, On Thu, 2022-12-29 at 07:21 +0100, Andreas Metzler wrote: > I do not understand why spamassassin 4.0.0 does not prpagate to > testing. > Tracker/excuses > https://qa.debian.org/excuses.php?package=spamassassin > says: > Issues preventing migration: > [...] > removing spamassassin/4.0.0~rc

Understanding what is blocking spamassassin 4.0.0 testing migration

Hello, I do not understand why spamassassin 4.0.0 does not prpagate to testing. Tracker/excuses https://qa.debian.org/excuses.php?package=spamassassin says: Issues preventing migration: [...] removing spamassassin/4.0.0~rc4-1/amd64 from testing makes claws-mail-spamassassin/4.1.1-2/amd64 unin