Okay, I see now that there is some confusion due to the way the test plan is written. It is stated that the lsblk example is specific to Plucky. However, the expectation is that we test all releases where the update is being released. It is not acceptable to say "we tested on plucky, so it's okay to release on noble and jammy."
So, can we find a way to test on noble and jammy? First option I can think of - can you just copy the lsblk profile from plucky to re-create the same issue? Or is there some reason why that doesn't work? ** Tags removed: verification-done-jammy verification-done-noble ** Tags added: verification-needed-jammy verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2115234 Title: Improper globbing in rules for /sys/devices PCI paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2115234/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
