Control: reassign -1 deborphan Control: severity -1 wishlist Control: retitle -1 Removing dummy packages should marks dependencies as manually installed
Hi,
On Wed, 10 Jul 2019 at 00:01:00 +0100, Conrad J.C. Hughes (for Debian package
stuff) wrote:
> So this is probably a buster upgrade issue, but not sure where to report it..
>
> After upgrading to buster, deborphan --guess-dummy (seemingly correctly)
> identified cryptsetup as a transitional dummy package, suitable for removal.
> However after removing cryptsetup, apt now tells me all the time that
> cryptsetup-bin, cryptsetup-initramfs and cryptsetup-run "were automatically
> installed and are no longer required". But my system's LUKS1-on-LVM-RAID-1..
> Running "apt autoremove" at this point would surely cause chaos?
Sounds like a feature request for deborphan, reassigning and retitling
accordingly.
cryptsetup.NEWS reads
cryptsetup (2:2.0.3-1) unstable; urgency=medium
With this version, cryptsetup has been split into cryptsetup-run
(init script) and cryptsetup-initramfs (initramfs integration).
'cryptsetup' is now a transitional dummy package depending on
cryptsetup-run and cryptsetup-initramfs.
-- Guilhem Moulin <guil...@debian.org> Wed, 16 May 2018 23:39:20 +0200
So if you remove the transition package you'll also need to `apt mark
manual` the dependencies. I guess deborphan could do that
automatically?
For what it's worth in your case marking ‘cryptsetup-initramfs’ only as
manually installed should be enough, because the package depends on
‘cryptsetup-run’. On a system where the initramfs integration is not
needed, one could instead remove ‘cryptsetup-initramfs’ and mark
‘cryptsetup-run’ as manually installed.
Cheers,
--
Guilhem.
signature.asc
Description: PGP signature
