Package: debhelper
Version: 13.2.1
Control: affects -1 + apt aptitude

If I want to uninstall libgcc-s1-dbgsym, I'm prompted as if it would
harm the system if I uninstall it:

Here's the prompt by aptitude's TUI:

  +-------------------------------------------------------------+
  |libgcc-s1-dbgsym is an essential package!                    |
  |                                                             |
  |Are you sure you want to remove it?                          |
  |Type 'Yes, I am aware this is a very bad idea' if you are.   |
  |                                                             |
  |         [ Ok ]                          [ Cancel ]          |
  +-------------------------------------------------------------+

And here's the same with apt when calling "apt purge libgcc-s1-dbgsym":

  The following packages will be REMOVED:
    libgcc-s1-dbgsym*
  WARNING: The following essential packages will be removed.
  This should NOT be done unless you know exactly what you are doing!
    libgcc-s1-dbgsym
  0 upgraded, 0 newly installed, 1 to remove and 9 not upgraded.
  After this operation, 159 kB disk space will be freed.
  You are about to do something potentially harmful.
  To continue type in the phrase 'Yes, do as I say!'
   ?]

I'm sure this counts for libgcc-s1, but clearly not for
libgcc-s1-dbgsym.

I'm not 100% sure if this is an issue in debhelper, dpkg-dev or the
gcc-10 source package, but I currently assume it's a bug in
debhelper. (Feel free to reassign in case I'm wrong here.)

So from my point of view, the following package headers must not be
copied into *-dbgsym packages if the source binary package (what a word
:-) has them:

* Important
* Protected
* Essential

… and probably some more which have the same effect on package managers.

Besides:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=libgcc-s1-dbgsym
claims:

  There is no maintainer for libgcc-s1-dbgsym. This means that this
  package no longer exists (or never existed). Please do not report new
  bugs against this package.

Which is kinda wrong, except the last part. Maybe debbugs should
recommend to file bugs in *-dbgsym packages generally against debhelper?
(If so, I'd file an according bug against debbugs, too. :-)

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 
'buildd-experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages libgcc-s1-dbgsym depends on:
ii  libgcc-s1  10.2.0-19

libgcc-s1-dbgsym recommends no packages.

libgcc-s1-dbgsym suggests no packages.

-- no debconf information

Reply via email to