Okay, I do not know the use case or the package enough to just say "yeah let us jump to the newest 1.5.x and use upstreams packaging". It would be wise to do so, but I lack the subject matter expertise. So for now let us fix the reported issue with what upstream did about it. The rest would need to be picked up on a wider overhaul.
So trying to stay as close as possible we are replicating what upstream did in 1.3.2 -> 1.3.4 for apparmor in dist/debian: - That has the profile itself and a little bit to install it (take that) - and some logic to differentiate old/new Ubuntu which we do not need as we know we are on stonking (<=23.10 will not apply). This is all in debian/* so no debian/patches magic, just carry the change. Taking $ git diff v1.3.2..v1.3.4 -- dist/debian Keep all the little issues, a stray whitespace, a useless empty line ... - this will avoid when moving to the real files some day by adopting the new version to not have any conffile churn. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2164911 Title: Non-root users cannot run containers because of missing AppArmor profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apptainer/+bug/2164911/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
