Yes I can certainly do that in future updates of python-uefivars in devel, but I think I would only SRU that back if python-uefivars needs to be SRUd for some other reason.
On Tue, Oct 21, 2025 at 3:05 PM Simon Chopin <[email protected]> wrote: > > Mate, for future python-uefivars uploads, could you add a debian/* > copyright stanza with Canonical as copyright holder? I won't block on > this since it has already been accepted in Noble, but it *is* standard > practice to have a separate statement for the packaging, especially > since here it's non-trivial (patches, etc), even if the license is the > same. > > Julian, it is OK from an AA perspective. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2129017 > > Title: > [SRU] Fix incorrect PCR selection list used in nullboot tests > > Status in python-uefivars package in Ubuntu: > Invalid > Status in ubuntu-boot-test package in Ubuntu: > New > Status in python-uefivars source package in Jammy: > Fix Committed > Status in ubuntu-boot-test source package in Jammy: > Fix Committed > Status in python-uefivars source package in Noble: > Invalid > Status in ubuntu-boot-test source package in Noble: > Fix Committed > > Bug description: > [ Impact ] > > * This is a follow up fix for > https://bugs.launchpad.net/ubuntu/+source/ubuntu-boot- > test/+bug/2123887 > > * The incorrect PCR selection list was used in the nullboot automated > tests due to encrypt-cloud-image > not being passed a "UEFI config". > > [ Test Plan ] > > * Make sure the autopkgtests pass for ubuntu-boot-test in proposed, and > review the logs to ensure the correct PCR selection list is used. > > * ubuntu-boot-test is not intended to be installed or used on end user > machines, thus there isn't any value in traditional manual local tests. > > [ Where problems could occur ] > > * The ubuntu-boot-test package was never seeded, nor is it intended to be > used by end users. > > * The worst case scenario is regression of tests into producing false > positives, > but this is unlikely given that we are only changing the nullboot one, > which > does not currently test PCR sealing correctly. > > [ Other Info ] > > * Despite being a universe package, ubuntu-boot-test is maintained by the > Canonical Foundations team. > > * Azure CVMs are not supported by Ubuntu on non-LTS releases, thus there > is no > value in uploading this change first to devel as no images exist that are > required to enable this test. > > * The proper fix for this requires the backporting of the python-uefivars > package to Jammy. > This was accepted into the archive alongside the initial > ubuntu-boot-test uploads in 2023 > here: > https://bugs.launchpad.net/ubuntu/+source/python-uefivars/+bug/2044086 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/python-uefivars/+bug/2129017/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2129017 Title: [SRU] Fix incorrect PCR selection list used in nullboot tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-uefivars/+bug/2129017/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
