Is there anyone from ubuntu-fan developers willing to satisfy SRU requirements below?
> Blocked on:
>
> * SRU paperwork
> * Fixes for future stable releases
> * Fix for Bionic
I could try those, but it's not ideal since I have to go through sponsorship processes and guess the intention of the patch.
This bug is critical to me since the proposed workaround for MAAS deployments as adding -proposed in MAAS is not realistic in production cloud because:
- MAAS is not capable to add ubuntu-release aware apt line for -proposed using the custom repository management (trusty nodes will also have xenial-proposed apt line unexpectedly)
- MAAS cannot specify the pin-priority of xenial-proposed using the custom repository management so unnecessary kernels and grub will be installed from -proposed
Is there anyone from ubuntu-fan developers willing to satisfy SRU requirements below?
> Blocked on:
>
> * SRU paperwork
> * Fixes for future stable releases
> * Fix for Bionic
I could try those, but it's not ideal since I have to go through sponsorship processes and guess the intention of the patch.
This bug is critical to me since the proposed workaround for MAAS deployments as adding -proposed in MAAS is not realistic in production cloud because:
- MAAS is not capable to add ubuntu-release aware apt line for -proposed using the custom repository management (trusty nodes will also have xenial-proposed apt line unexpectedly)
- MAAS cannot specify the pin-priority of xenial-proposed using the custom repository management so unnecessary kernels and grub will be installed from -proposed
I ended up using a little bit verbose late_commands in curtin_userdata which is not so handy: /paste. ubuntu. com/26319353/
https:/