(In reply to Kip Warner from comment #28) > TJ, I may have spoke too soon. I've tried running it again on the hello > source. My image uses your patched kernel via a PPA with the upgrade > performed via the --setup-commands: > > https://launchpad.net/~kip/+archive/ubuntu/linux-kernel-6.8.0
I see no sign of the patch being applied in the build log; I see it in the source diff but it would not be applied at build-time since it is in the wrong place. https://launchpad.net/~kip/+archive/ubuntu/linux- kernel-6.8.0/+files/linux_6.8.0-31.31_6.8.0-35.35ubuntu1+kip1.diff.gz Shows a patch file at: --- linux-6.8.0.orig/patches/fix-218916.patch +++ linux-6.8.0/patches/fix-218916.patch but no sign of it being applied in the tree. Ubuntu kernel development flow is different to Debian; it's more like mainline with changes committed directly in the kernel tree. On upload a source diff is then generated between mainline and the Ubuntu tree to create the usual Debianised orig.tar.gz/diff.gz packages that the buildd's use. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056461 Title: autopkgtest-virt-qemu on noble images sometimes hangs doing copydown To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056461/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
