Hi, if you look at the tracker.d.o page for libvirt[1] you'll see that it displays inconsistent information. Specifically, the "news" sections mentions the recent (2023-08-08) upload of 9.6.0-1[2], but the "action needed" section still claims that a new upstream version is available; the vcswatch message is consistent with this. A security issue is also mentioned as still open in sid, while in reality the recent upload addressed it and the security tracker[3] correctly reports this. Further down, in the "testing migrations" section, the excuses reported are for the *9.5.0-2* version, which is an earlier (2023-07-25) upload. Looking at the current excuses[4] correctly refer to the 9.6.0-1 version, where migration is apparently held up because of gnutls28. There are more inconsistencies, but you get the point. I'm pretty sure everything will go back to normal given enough time, but it looks like the particular set of circumstances around the libvirt package have fallen through the cracks of tracker.d.o's logic and it could be interesting to investigate them while the issue is still manifesting itself. Cheers! [1] https://tracker.debian.org/pkg/libvirt [2] https://tracker.debian.org/news/1451405/accepted-libvirt-960-1-source-into-unstable/ [3] https://security-tracker.debian.org/tracker/source-package/libvirt [4] https://qa.debian.org/excuses.php?package=libvirt -- Andrea Bolognani <eof@kiyuko.org> Resistance is futile, you will be garbage collected.
Attachment:
signature.asc
Description: PGP signature