Your message dated Tue, 9 Aug 2022 02:05:31 +0200
with message-id <[email protected]>
and subject line Re: Bug#976793: libgcc-s1-*-cross is Important: yes
has caused the Debian Bug report #976793,
regarding libgcc-s1-*-cross is Important: yes
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 [email protected]
immediately.)
--
976793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976793
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: gcc-10-cross
Version: 10.2.0-19cross1
Severity: normal
Hi!
While trying to uninstall cross toolchain:
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
libgcc-s1-arm64-cross gcc-10-cross-base (due to libgcc-s1-arm64-cross)
libc6-arm64-cross (due to libgcc-s1-arm64-cross)
0 upgraded, 0 newly installed, 28 to remove and 0 not upgraded.
After this operation, 477 MB disk space will be freed.
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'
?]
Which is caused by:
Package: libgcc-s1-arm64-cross
Version: 10.2.0-19cross1
Built-Using: gcc-10 (= 10.2.0-19)
Priority: optional
Protected: yes
Section: devel
Source: gcc-10-cross (13)
Maintainer: Debian GCC Maintainers <[email protected]>
Installed-Size: 97.3 kB
Provides: libgcc-s1-arm64-dcv1, libgcc1-arm64-cross (= 1:10.2.0-19)
Depends: gcc-10-cross-base (>= 10.2.0-19), libc6-arm64-cross (>= 2.31)
Breaks: libgcc1-arm64-cross (<< 1:10)
Replaces: libgcc1-arm64-cross (<< 1:10)
Homepage: http://gcc.gnu.org/
Important: yes
^^^^^^^^^^^^^^
Download-Size: 34.5 kB
APT-Manual-Installed: no
APT-Sources: http://apt-rosy.angband.pl:3142/debian unstable/main amd64 Packages
Description: GCC support library (arm64)
Meow!
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-rc6-00014-gc4c7126c671f (SMP w/64 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
On Mon, Aug 08, 2022 at 09:26:26PM +0100, Simon McVittie wrote:
> On Tue, 08 Dec 2020 at 00:51:00 +0100, Adam Borowski wrote:
> > Package: libgcc-s1-arm64-cross
> > Important: yes
>
> On Wed, 14 Jul 2021 at 08:00:19 +0200, Matthias Klose wrote:
> > According to the build logs, all lib*-*-cross packages have optional
> > priority,
> > so it needs to be adjusted for the archive.
> I believe Adam's concern was about the Protected and Important fields
> (which are controlled by the maintainer in the usual way, I think?) and
> not about the Priority field (which is controlled by the ftp team).
Aye.
> The Important field was an old name for the almost-Essential state that
> apt now calls Protected, and should not be confused with Priority:
> important, but obviously it's very easy to confuse them (hence the
> rename).
It is still used this way, and present on a bunch of packages.
> None of the versions of libgcc-s1-arm64-cross visible to my apt-cache
> seem to be Protected, Important, or have an inflated priority.
On the other hand, libgcc-s1 is both Important: yes and Protected: yes.
Obviously, this setting came from the regular package to -cross;
it's no longer there, though.
> So I think this has been dealt with somewhere/somehow?
Apparently it has.
Let's close then...
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ An imaginary friend squared is a real enemy.
⠈⠳⣄⠀⠀⠀⠀
--- End Message ---
