Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1034446: unblock: linux/6.1.24-1
5 views
Skip to first unread message
Salvatore Bonaccorso
Apr 15, 2023, 11:10:04 AM4/15/23
to
Package: release.debian.org
Severity: normal
User: release.d...@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: li...@packages.debian.org, ki...@debian.org, car...@debian.org
Control: affects -1 + src:linux
Dear release team,
Please unblock package linux
I'm seaking for pre-approval and your opinion on time availability to
still do at least (and depending on finding the release date for
bookworm) further stable series imports. After 6.1.20-2 migration to
testing (which I see it is already unblocked, thanks Paul Gevers), the
next update could be to update to at least 6.1.24:
There are stable series imports from 6.1.20 up to 6.1.24, convering as
well fixes for CVE-2023-1989, CVE-2023-1583 and CVE-2023-1611. Ideally
we as well address #1033058 (Cyril will be happy).
There are fixed in different areas as well, which we can benefit of
(e.g. fixes for the newly enabled mpi3mr driver, this was known the
fixes will land in post 6.1.20). With the stable series import there
is as well always a slight risk on new upstream regressions.
Would you in principle agree on that, imporantly, at this stage of the
release? The current debian/changelog is attached.
unblock linux/6.1.24-1
Regards,
Salvatore
Severity: normal
User: release.d...@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: li...@packages.debian.org, ki...@debian.org, car...@debian.org
Control: affects -1 + src:linux
Dear release team,
Please unblock package linux
I'm seaking for pre-approval and your opinion on time availability to
still do at least (and depending on finding the release date for
bookworm) further stable series imports. After 6.1.20-2 migration to
testing (which I see it is already unblocked, thanks Paul Gevers), the
next update could be to update to at least 6.1.24:
There are stable series imports from 6.1.20 up to 6.1.24, convering as
well fixes for CVE-2023-1989, CVE-2023-1583 and CVE-2023-1611. Ideally
we as well address #1033058 (Cyril will be happy).
There are fixed in different areas as well, which we can benefit of
(e.g. fixes for the newly enabled mpi3mr driver, this was known the
fixes will land in post 6.1.20). With the stable series import there
is as well always a slight risk on new upstream regressions.
Would you in principle agree on that, imporantly, at this stage of the
release? The current debian/changelog is attached.
unblock linux/6.1.24-1
Regards,
Salvatore
Paul Gevers
Apr 15, 2023, 3:52:25 PM4/15/23
to
Hi Salvatore,
On 15-04-2023 17:02, Salvatore Bonaccorso wrote:
> Would you in principle agree on that, imporantly, at this stage of the
> release? The current debian/changelog is attached.
I'm pretty sure I've mentioned this to you before, but to be clear to
everybody I'll state it in public here: we currently trust the kernel
maintainers to make the right decision until (around) the full freeze
under the condition that they consider the following:
* would you propose the same for a point release?
* if activity in the archive on the d-i front is ongoing or expected
check with d-boot.
Paul
On 15-04-2023 17:02, Salvatore Bonaccorso wrote:
> Would you in principle agree on that, imporantly, at this stage of the
> release? The current debian/changelog is attached.
everybody I'll state it in public here: we currently trust the kernel
maintainers to make the right decision until (around) the full freeze
under the condition that they consider the following:
* would you propose the same for a point release?
* if activity in the archive on the d-i front is ongoing or expected
check with d-boot.
Paul
Salvatore Bonaccorso
Apr 17, 2023, 4:20:04 PM4/17/23
to
Hi Paul,
On Sat, Apr 15, 2023 at 09:41:02PM +0200, Paul Gevers wrote:
> Hi Salvatore,
>
> On 15-04-2023 17:02, Salvatore Bonaccorso wrote:
> > Would you in principle agree on that, imporantly, at this stage of the
> > release? The current debian/changelog is attached.
>
> I'm pretty sure I've mentioned this to you before, but to be clear to
> everybody I'll state it in public here: we currently trust the kernel
> maintainers to make the right decision until (around) the full freeze under
> the condition that they consider the following:
>
> * would you propose the same for a point release?
Yes confirmed.
> * if activity in the archive on the d-i front is ongoing or expected
> check with d-boot.
Right, I do CC as well respectively Cyril specifically and be verbose
with him on plans. So do check with d-i people accordingly.
What I cannot assure is that we never will see regressions in such
point releases, and in fact for instance currently on bullseye we have
for instance #1022126 (got long to get addressed) or #1031753 (to be
fixed in next upload).
So I completely agree, around the time before the full freeze those
updates then need to be postponed to the point releases to not risk
blocking the release.
Regards,
Salvatore
On Sat, Apr 15, 2023 at 09:41:02PM +0200, Paul Gevers wrote:
> Hi Salvatore,
>
> On 15-04-2023 17:02, Salvatore Bonaccorso wrote:
> > Would you in principle agree on that, imporantly, at this stage of the
> > release? The current debian/changelog is attached.
>
> I'm pretty sure I've mentioned this to you before, but to be clear to
> everybody I'll state it in public here: we currently trust the kernel
> maintainers to make the right decision until (around) the full freeze under
> the condition that they consider the following:
>
> * would you propose the same for a point release?
> * if activity in the archive on the d-i front is ongoing or expected
> check with d-boot.
with him on plans. So do check with d-i people accordingly.
What I cannot assure is that we never will see regressions in such
point releases, and in fact for instance currently on bullseye we have
for instance #1022126 (got long to get addressed) or #1031753 (to be
fixed in next upload).
So I completely agree, around the time before the full freeze those
updates then need to be postponed to the point releases to not risk
blocking the release.
Regards,
Salvatore
0 new messages