edubuntu-bugs team mailing list archive

[Robie Basak <2065915@xxxxxxxxxxxxxxxxxx>]

Thank you for working on this. I'm not doing my SRU shift but was
surprised to see so many uploads appear in the SRU queue together so
paused to take a look.

It looks like you're removing AppArmor confinement wholesale for a large
number of packages, which I think requires exceptional justification in
an SRU but I don't see this provided anywhere.

I would expect the minimal fix appropriate to fix the SRU to be to fix
the specific multiarch path that is described as the underlying issue in
bug 2064492. I see that was done initially in Oracular (eg.
https://launchpad.net/ubuntu/+source/cantor/4:23.08.5-0ubuntu5) but then
further changed again to drop confinement altogether (eg.
https://launchpad.net/ubuntu/+source/cantor/4:23.08.5-0ubuntu6). Please
could you explain why the former is (presumably) unsuitable?

Separately, we usually present SRUs as fixing the actual bug they're
fixing, rather than creating a separate bug. So I'd have expected only
bug 2064492 without this bug 2065915 being created. It's not clear to me
what is separate to track here. See "Do not create a meta-bug" in step 1
of https://wiki.ubuntu.com/StableReleaseUpdates#Procedure. But let's
focus on the real question and not worry about that for now.

-- 
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to marble in Ubuntu.
https://bugs.launchpad.net/bugs/2065915

Title:
  [SRU] Fix hard coded path in apparmor profiles.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2065915/+subscriptions