From a quick glance this seems fine in principle IIUC. There are some questions/expectations I have in these cases though:
1) Which Ubuntu developer team is committing to maintaining this feature on an ongoing basis? If this is important enough to SRU, it would follow that there should be such a commitment. 2) Since this was a "dropped upstream, we didn't notice and released without" case, I would expect there to be an automated smoke test added in our packaging in the development release to ensure that the feature doesn't break in the future and get released again without us noticing. Is there one? > If this firmware is built with secure boot on it changes security scope and it's questionable if the code is unmaintained. IMHO, this is essentially the same as my first point above: part of the point of Ubuntu is to maintain delta against upstreams for use cases we care deeply about, but this needs to come with an appropriate commitment to ongoing maintenance, which includes security maintenance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2129178 Title: Can not boot qemu VMs using ParaVirtual SCSI controllers with Ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/2129178/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
