Re: Understanding what is blocking spamassassin 4.0.0 testing migration
On 2022-12-29 "Adam D. Barratt" <adam@adam-barratt.org.uk> 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 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.
Thank you (and Paul) for the explanation. I did not get that "removing
spamassassin" was talking about the binary. The retried build succeeded.
:-)
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
Reply to: