We've discussed this in the past and it was determined that 'aa-status' is to be part of every apparmor minimal install (which is why it is in apparmor and all the other python tools are in apparmor-utils) so splitting out of apparmor-minimal doesn't really work with this thinking.
Perhaps moving aa-status to a new 'apparmor-status' package, have it Depends on python3, then have the 'apparmor' package Recommends 'apparmor-status' could be a way to go. snapd should still Depends on apparmor, which would pull in apparmor-status (and it should-- we want aa-status on UC devices, etc). Alternatively, aa-status could be rewritten in C/C++ (like other parts of apparmor). This is probably the best solution for your problem. Can you elaborate on the problem this is trying to solve (building snaps unnecessarily installs python3 onto the system-- why specifically is this an issue?) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1865519 Title: apparmor depends on python3 Status in snapd: New Status in apparmor package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: The TL;DR; - AppArmor depends on python3 to support aa-status. - snapd depends on apparmor. - buildd images have no python - building snaps requires snapd - snapd does not require aa-status - building snaps unnecessarily installs python3 onto the system Proposal: - Split runtime requirements from apparmor into apparmor-minimal - have apparmor depend on apparmor-minimal - change snapd's dependency on apparmor to apparmor-minimal To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1865519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
