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 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.
Well, the arch:all package didn't build yet, so if the source would migrate, it would be effectively removing the binary. (It seems like the while I'm typing this message, somebody hit the rebuild retry.)
https://release.debian.org/britney/update_output.txt does not mention spamassassin at all. It also seems very short, not like a full run with less than 1000 lines.
If the first phase of britney (the policy phase) already blocks an item, the second phase doesn't see it, so that's expected. See the docs [1].
Paul [1] https://release.debian.org/doc/britney/short-intro-to-migrations.html
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature