Control: close -1 On Mon, Aug 16, 2021 at 11:14:02AM +0200, Steinar H. Gunderson wrote: > On Sun, Aug 15, 2021 at 01:56:50PM +0200, Steinar H. Gunderson wrote: > > mlocate in unstable has now been replaced with plocate, ie., plocate > > contains a > > binary package “mlocate” that is a transitional package. Thus, please remove > > the mlocate source package in unstable (but not the mlocate binary package, > > which comes from the plocate source). > > > > bullseye still contains both mlocate and plocate.
Actually, you don't need a RM bug in this case: the src:mlocate source
package will be manually decrufted whenever some ftp-master goes through
the cruft report, since it's a "source that doesn't build any binary
anymore".
As such, I'm closing this RM bug, since more than once I saw such bugs
executed wrongly and also removed the binary….
> A question: Normally, when a package is removed, all bugs filed against it
> are closed; does this also happen in this case? (It doesn't make sense for
> plocate to “adopt” all of these bugs, they should probably just be closed.)
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
There is only *1* bug attached to the source src:mlocate that would be
affected by this (#969522 - which I recommend you go and manually close
already, since it's clearly obsoleted now).
--
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
