Comment 28 for bug 2051999

1. Doing 2.12 backports to Jammy will happen, but it's not an overnight process. The delta from 2.06 to 2.12 is large, and even though it might work on your and my machine. We are hoping that the 2.12 release to Debian testing now, upload to Debian -backports later, and release to Noble in April will give us more time to see the effect in the field.

Some minor breakage on old and odd machines will happen, I know that, as we have changed the entire kernel loading mechanism going from 2.12 -> 2.06, but hopefully it can be kept as minimal as possible. I am already in the process of integrating patches for issues reported in reaction to the Debian testing roll-out.

2. The PPA breaking Jammy has an additional very different reason to not doing 2.12 backports right now, it's because of the wrong build OS being used, basically:

If you only install grub-efi-* from the PPA it's less likely to break, but the problem is `grub*-common` is linked against user-space shlibs from Noble which can and will be newer than Jammy's, and ABI backwards compatibility isn't exactly always a guarantee.

The correct solution for Jammy would be to upload the same package with a slightly different version number and `jammy` as the series in d/changelog to a PPA, and then have
"deb [trusted=yes] https://ppa.launchpadcontent.net/your_user_here/ppa_here/ubuntu/ jammy main" in sources.

If you want a GRUB 2.12 build for Jammy right now, I can upload that to a PPA in my namespace.