I disagree. user space migrations should not be blocked by kernel changes. We know that the kernel is sensible to compiler changes, so it probably should build-depend on an explicit GCC version. And no, we should not block migrations on build failures, just for this case. So the kernel needs to have an explicit switch to a new GCC version once it's supported by the kernel.
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836100 Title: Was able to migrate out of proposed despite breaking dkms Status in Auto Package Testing: Triaged Status in linux package in Ubuntu: New Bug description: The recent gcc update in eoan migrated out of proposed despite the fact that it was breaking dmks/nvidia users, could we have some sort of autopkgtest added to make sure that gcc gets blocked in proposed the next time we have a such situation? (see bug #1830961) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1836100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp