On Tue, Aug 17, 2021 at 02:22:11PM +0200, Steinar H. Gunderson wrote: > > In the case of a curft removal, no bugs are closed. > > However, this is not relevant in this case: bugs might be attached to > > either a binary package or a source package: taking over the bin:mlocate > > binary you also carried over all of its bugs already. > > See https://bugs.debian.org/src:plocate > > Sure, but I specifically don't want to take over those bugs. (E.g., some of > them are wishlist bugs from 2009...) I could go ahead and close them all > myself, but it sounds maybe better to have the official “mlocate is gone” > mail?
That's too late, as I said, since they are already "attached" to
src:plocate.
The official "mlocate is gone" message is definitely your job to write
as the new bin:mlocate maintainer ;)
That said, please do not mass-close those bugs. They are only a dozen,
I'm sure you can at least read the first message and confirm they indeed
do not apply anymore. But it's your call on how you want to handle the
bugs, so ¯\_(ツ)_/¯
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
