Your message dated Thu, 12 Dec 2024 14:25:49 -0500
with message-id <7a93abe5-436e-47b5-9aee-5b8792511...@queued.net>
and subject line Re: Bug#1089181: chromium: security update wants to remove
chromium package itself
has caused the Debian Bug report #1089181,
regarding chromium: security update wants to remove chromium package itself
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 ow...@bugs.debian.org
immediately.)
--
1089181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089181
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 131.0.6778.108-1~deb12u1
Severity: grave
Hi.
Today's chromium update in stable wants to remove "chromium" and
"chromium-l10n":
------------------------------------------------------------------------------------
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
libopenh264-7
Use 'apt autoremove' to remove it.
The following packages will be REMOVED:
chromium chromium-l10n
The following packages have been kept back:
chromium-common
The following packages will be upgraded:
chromium-sandbox
1 upgraded, 0 newly installed, 2 to remove and 1 not upgraded.
Need to get 97.7 kB of archives.
After this operation, 387 MB disk space will be freed.
Do you want to continue? [Y/n]
------------------------------------------------------------------------------------
Also, on a VM where chrome is not installed yet, chrome may
not be installed at all:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
chromium : Depends: libc++1-19 (>= 1:19.1.4) but it is not installable
Depends: libc++abi1-19 (>= 1:19.1.4) but it is not installable
Depends: libunwind-19 (>= 1:19.1.4) but it is not installable
Depends: chromium-common (= 131.0.6778.108-1~deb12u1) but it is not
going to be installed
E: Unable to correct problems, you have held broken packages.
Thanks.
--- End Message ---
--- Begin Message ---
On Tue, 10 Dec 2024 14:50:37 -0500 Andres Salomon <dilin...@queued.net>
wrote:
On 12/10/24 14:41, Neil Van Dyke wrote:
> Are those library updates part of the security update?
>
> The following packages will be REMOVED:
> libc++1-16 libc++abi1-16 libunwind-16
> The following NEW packages will be installed:
> libc++1-19 libc++abi1-19 libunwind-19
> The following packages will be upgraded:
> chromium chromium-common chromium-sandbox
>
> I don't recall seeing this before in Debian Stable, so I'm hesitant to
> install the `chromium` security update.
>
Yes.
However, for the next security release (scheduled for later today;
upstream just released for IOS, so I expect a Linux release any minute
now) I'm going to temporarily switch back to gcc's libstdc++ so that
users can upgrade without those conflicts.
New DSA with security update has been released. This should fix all
issues related to libc++.
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
