On Mon, 02 Oct 2017 07:10:04 +0200 Andreas Beckmann <a...@debian.org> wrote: > Package: apt > Version: 1.5 > Severity: important > User: debian...@lists.debian.org > Usertags: piuparts > Control: affects -1 + fdisk-dbgsym mount-dbgsym > > Hi, > > during a test with piuparts I noticed that apt refuses to remove the > "essential" fdisk-dbgsym and mount-dbgsym packages. I have no idea where > apt gets the idea that these are essential. > > This happens in sid and buster chroots. > > 0m22.3s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmptrow8E', > 'apt-get', 'remove', 'mount-dbgsym'] > 0m22.8s DUMP: > Reading package lists... > Building dependency tree... > Reading state information... > The following packages will be REMOVED: > mount-dbgsym > WARNING: The following essential packages will be removed. > This should NOT be done unless you know exactly what you are doing! > mount-dbgsym > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > E: Essential packages were removed and -y was used without > --allow-remove-essential. > 0m22.8s ERROR: Command failed (status=100): ['chroot', > '/srv/piuparts/tmp/tmptrow8E', 'apt-get', 'remove', 'mount-dbgsym'] > > > Andreas > >
They inherited the "Important: yes" field from their "main" binary counterparts, because debhelper was unaware that it should unset that field. A rebuild of these packages with debhelper/10.9 should resolve this issue. Thanks, ~Niels
