On Wed, Jan 01, 2025 at 09:51:48AM +0100, Joost van Baal-Ilić wrote: > Hi, > > At https://tracker.debian.org/pkg/pwdsphinx > it says: "Updating pwdsphinx would introduce bugs in testing: #1090262" . > > And at https://tracker.debian.org/pkg/pyequihash it says: "Marked for > autoremoval on 14 January: #1090264" . > > However, afaiu, both https://bugs.debian.org/1090262 and > https://bugs.debian.org/1090264 are closed.
The "done" status of a bug report almost never matters, to tools or to people. And tools like the migration and autoremoval ones care whether a bug is fixed in a given release, which is easily seen on the graph on the bug report page. > (They are about "FTBFS: ValueError: Unable to find libequihash", which was > fixed in the libequihash 1.0.10-2 upload at december 15; I closed the bugs > manually after that.) Closing bugs manually requires a lot of understanding how all of this works. You tried to mark both 1090262 and 1090264 as fixed in various packages that either don't exist or are not the package that the bug was reported against, so the packages remained to be marked as buggy. It seems that you did this because the bug was not in the packages those reports were filed against but in a different package. The reports describe this possibility and the correct way to deal with this: "If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package." If this was done, the bug reports would be correctly closed by the upload that fixed the bug itself. -- WBR, wRAR
signature.asc
Description: PGP signature
