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

Bug#1035973: marked as done (unblock: linux/6.1.27-1)

Your message dated Fri, 12 May 2023 07:57:30 +0000
with message-id <E1pxNec-00FuUJ-56@respighi.debian.org>
and subject line unblock linux
has caused the Debian Bug report #1035973,
regarding unblock: linux/6.1.27-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.)


-- 
1035973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035973
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: linux@packages.debian.org, kibi@debian.org, debian-boot@lists.debian.org, benh@debian.org, carnil@debian.org
Control: affects -1 + src:linux

Hi Release team, hi Cyril for debian-boot/d-i,

Please unblock package linux

The upload was announced in
https://lists.debian.org/debian-release/2023/05/msg00287.html and
summarizing consists of importing new stable series. But in particular
addressing recent CVEs, covering CVE-2023-31436 and CVE-2023-2002.
Additionally the fix for CVE-2023-32233 is cherry-picked.

The package has been only 3 days, but I'm asking for an unblock and
aging due to CVE-2023-32233 in particular.

*Unless* it is going to block d-i RC3 release, then let's wait after
that.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [ ] attach debdiff against the package in testing

Not attaching the debdiff.

Regards,
Salvatore

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

--- End Message ---
Reply to: