I got a message from testing auto removal saying:
But that bug is *fixed* in moonshot-ui 1.1.0+libsecret2.


I'm guessing that this is probably some race condition between migration and removals data sources updating.
But it seems odd that the testing auto removal script knows about the new version but doesn't know that the new version  fixes the RC bug in question.

If the removal notice is correct and moonshot-ui is still scheduled for removal even though I fixed the bug, I'd like to better understand what's up.

It's more likely that the race lies within the BTS.  The BTS only
exports data about whether a bug affects testing or not, without version
information.

At this writing, from what I see it's not scheduled for removal anymore.

Hi,

I guess Mattia is right here. For the removal mailing script, the data
source is UDD however, all the information comes from the
testing_autoremovals table.

Should we reassign this bug to qa.debian.org (using the udd usertag and
user qa.debian.org@packages.debian.org)? Not sure it's going to help.

Paul