Re: Understanding what is blocking spamassassin 4.0.0 testing migration

["Adam D. Barratt" <adam@adam-barratt.org.uk>]

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~rc4-1/amd64 from testing makes claws-
> mail-spamassassin/4.1.1-2/amd64 uninstallable
>     removing spamassassin/4.0.0~rc4-1/amd64 from testing makes
> evolution-plugin-spamassassin/3.46.2-1/amd64 uninstallable
> [ list of more spamassassin rdeps which would be uninstallable if ]
> 
> 
> Note that it only talks about "removing" instead of "upgrading".
> Which
> obviously cannot work.
> 

That's due to the arch:all build failing, which means there is no
"spamassassin" binary package in unstable currently when combined with
dak's feature of hiding arch:all packages that don't correspond to the
version of arch-dep packages. See #915948 for further details on
similar issues.

Looking at previous build failures, it looks like the arch:all build
has issues with IPv6-only buildds. I've given it back, so let's see
what happens.

Regards,

Adam