For ubuntu-unity-meta I asked the maintainer in #1842014 to update it but they didn't yet. Considering the urgency here, I took matters into my hands:
1) Ported https://code.launchpad.net/~unity7maintainers/ubuntu-seeds/ubuntu-unity.cosmic -> https://code.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu-unity
2) Updated ubuntu-unity-meta to reference eoan. Due to how germinate works, it falls back to https://code.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu-unity when https://code.launchpad.net/~unity7maintainers/ubuntu-seeds/ubuntu-unity.oean doesn't exist.
3) Refreshed dependencies using ./update
4) Uploaded to eoan
So I believe that Ubuntu plans can continue now.
That said there is discussion in Debian now to turn fwupdate into a transitional package with something like this (advice welcome). https://salsa.debian.org/efi-team/fwupdate/commit/b4daba89c567d4cf52f5deaab1ea2ee13039d03f
For ubuntu-unity-meta I asked the maintainer in #1842014 to update it but they didn't yet. Considering the urgency here, I took matters into my hands:
1) Ported https:/ /code.launchpad .net/~unity7mai ntainers/ ubuntu- seeds/ubuntu- unity.cosmic -> https:/ /code.launchpad .net/~ubuntu- core-dev/ ubuntu- seeds/+ git/ubuntu- unity
2) Updated ubuntu-unity-meta to reference eoan. Due to how germinate works, it falls back to https:/ /code.launchpad .net/~ubuntu- core-dev/ ubuntu- seeds/+ git/ubuntu- unity when https:/ /code.launchpad .net/~unity7mai ntainers/ ubuntu- seeds/ubuntu- unity.oean doesn't exist.
3) Refreshed dependencies using ./update
4) Uploaded to eoan
So I believe that Ubuntu plans can continue now.
That said there is discussion in Debian now to turn fwupdate into a transitional package with something like this (advice welcome). /salsa. debian. org/efi- team/fwupdate/ commit/ b4daba89c567d4c f52f5deaab1ea2e e13039d03f
https:/