Comment 74 for bug 1990450

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Sorry, I'm very much lost by now.

Let's use jammy as an example:

update-manager | 1:22.04.9 | jammy | source
update-manager | 1:22.04.10 | jammy-updates | source
update-manager | 1:22.04.16 | jammy-proposed | source
update-manager | 1:22.04.17 | jammy/unapproved/93d92bdd | source

We have 22.04.16 in jammy-proposed, which claims to have fixed this bug here: #1990450

We have 22.04.17 in jammy unapproved, which claims in its changes file to be fixing #1990450 again, and #2043425. It has no new changes about #1990450, though.

And #1990450 has verification-failed tags.

If we accept the package in jammy-unapproved, it will again try to fix this bug here, but with no new changes, it won't. So should the package in unapproved not claim to fix #1990450? Or what is going on?