Your message dated Fri, 3 May 2024 07:26:19 +0200
with message-id <zjr1e965biahp...@ramacher.at>
and subject line Re: Bug#1070266: nmu: chromium_124.0.6367.118-1
has caused the Debian Bug report #1070266,
regarding nmu: chromium_124.0.6367.118-1
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.)
--
1070266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian....@packages.debian.org
Usertags: binnmu
Severity: serious
Hello,
Snappy 1.2.0-1 was uploaded with broken symbols (see
https://bugs.debian.org/1070217). This is fixed in snappy 1.2.0-2, but
chromium in sid had already built against the broken version of snappy.
Please rebuild chromium against snappy 1.2.0-2 to fix its broken symbol
dependencies. Because this chromium release has CVE fixes (and there's
20-something pending CVEs in trixie already that would be fixed by
chromium migration), I'm filing this with a higher severity than usual.
nmu chromium_124.0.6367.118-1 . ANY . -m 'Rebuild against
libsnappy1v5 to fix broken symbols (#1070217)'
OpenPGP_0x645D0247C36E7637.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On 2024-05-02 18:54:20 -0400, Andres Salomon wrote:
> Package: release.debian.org
> User: release.debian....@packages.debian.org
> Usertags: binnmu
> Severity: serious
>
> Hello,
>
> Snappy 1.2.0-1 was uploaded with broken symbols (see
> https://bugs.debian.org/1070217). This is fixed in snappy 1.2.0-2, but
> chromium in sid had already built against the broken version of snappy.
>
> Please rebuild chromium against snappy 1.2.0-2 to fix its broken symbol
> dependencies. Because this chromium release has CVE fixes (and there's
> 20-something pending CVEs in trixie already that would be fixed by chromium
> migration), I'm filing this with a higher severity than usual.
>
> nmu chromium_124.0.6367.118-1 . ANY . -m 'Rebuild against libsnappy1v5 to
> fix broken symbols (#1070217)'
Scheduled.
Cheers
--
Sebastian Ramacher
--- End Message ---
