Hi,

On 28-05-2024 10:54 a.m., Luca Boccassi wrote:
If 6.8 migrates to testing, it will break amd64 debci for unrelated
packages for migration tests too. I don't think that's something we
want? Paul, wouldn't that qualify as RC?

With the kernel team being aware of the issue, I trust the kernel team to balance the options appropriately. I defer to make a call as a Release Team member.

Options that I'm aware of:

1) accept the kernel package as is in testing where it will cause some regression in some autopkgtest on ci.d.n infrastructure in testing. We have (only) 56 packages tested with qemu and I could disable qemu based testing on ci.d.n until this bug is resolved (which means that isolation-machine tests will not be run, but also not cause unnecessary failures).

2) update the kernel package with the bisected commit reverted. I understand that the kernel team tries to follow upstream as much as possible to avoid Debian delta's that might be hard to get rid of.

3) update the kernel package with a proposed (but not accepted) patch.

4) wait with updating the kernel package in testing until this issue is solved upstream, causing all kernel fixes to hit testing later.

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to