[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#877474: marked as done (apt: considers fdisk-dbgsym, mount-dbgsym as essential)

Your message dated Mon, 2 Oct 2017 10:13:21 +0200
with message-id <20171002081320.3oo2jitu2q3onsdc@crossbow>
and subject line Re: Bug#877474: apt: considers fdisk-dbgsym, mount-dbgsym as essential
has caused the Debian Bug report #877474,
regarding apt: considers fdisk-dbgsym, mount-dbgsym as essential
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
877474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877474
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 1.5
Severity: important
User: debian-qa@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

--- End Message ---
--- Begin Message --- 
Hi,

On Mon, Oct 02, 2017 at 07:10:04AM +0200, Andreas Beckmann wrote:
> 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.

It gets the idea from the "Important" field included for those packages,
which triggers apt (and in future potentially also dpkg) to be as
annoying as it is for essential packages if such a package is marked for
removal, but gives no guarantees usually associated with essential.
So ideal for packages which can be considered "important" for a system.

(The field is OLD, so don't question the name if you don't have
a timemachine at your disposal. We have heard it all, but multi-release
transitions are no fun and the people responsible for it are gone for
more than decade by now. So changing it is basically just busy work)


I don't think we should change the output of apt here as its kinda the
point to be an "essential look-alike" and its relatively simple to find
advice about what essential is if you are looking for it as someone not
in the know. Whatever we would come up with for important would be less
discoverable and also easily confused with prio:important …


> This happens in sid and buster chroots.

It shouldn't happen any longer in 'sid' chroots as debhelper 10.9
(release 19 Sep 2017) was fixed to not emit the field for dbgsym
packages (but Niels already said that).


As apt operates as intended here & debhelper was already fixed,
closing as not a bug (for apt).


Best regards

David Kalnischkies

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: