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

Bug#1105898: marked as done (unblock: chromium/136.0.7103.113-1)

Your message dated Fri, 16 May 2025 19:14:16 +0000
with message-id <E1uG0Vc-005dhV-0l@respighi.debian.org>
and subject line unblock chromium
has caused the Debian Bug report #1105898,
regarding unblock: chromium/136.0.7103.113-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 owner@bugs.debian.org
immediately.)


-- 
1105898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105898
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: dilinger@queued.net
Control: affects -1 + src:chromium
Please unblock (and hint in, so we don't have to wait additional days) chromium 136.0.7103.113-1. I'm waiting for the armhf build to finish, but that should happen sometime in the next half day based on past arm-ubc-04 performance.
The version in trixie contains 7 outstanding CVEs, and 136.0.7103.113-1~deb12u1 is already in bookworm-security.
Note that the prior version in sid, 136.0.7103.92-2, spent 7 days in sid without any RC bugs, autopkgtest failures, or other issues. I'm pretty confident that *.113-1, which contains only targeted fixes on top of *.92-2, is in good shape. 

Thanks,
Andres

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
Unblocked.

--- End Message ---
Reply to: