** Changed in: apparmor (Debian)
Status: Unknown => New
--
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/1435452
Title:
dh_apparmor has no dh sequencer support
** Bug watch added: Debian Bug tracker #934735
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934735
** Also affects: apparmor (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934735
Importance: Unknown
Status: Unknown
--
You received this bug notification
FWIW I went hunting for bug reports about this issue in response to
https://github.com/snapcore/snapd/pull/6508 - if this were solved
centrally in dh-apparmor, I expect that would benefit a number of
packages over the long term.
--
You received this bug notification because you are a member of
** Changed in: apparmor (Ubuntu)
Importance: Undecided = Wishlist
--
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/1435452
Title:
dh_apparmor has no dh sequencer
How about:
debian/apparmor/usr.sbin.mysqld: actual profile
debian/mysql-server-5.6.apparmor:
debian/apparmor/usr.sbin.mysqld usr.sbin.mysqld
OR (both would work)
debian/apparmor/usr.sbin.mysqld
(profile name defaults to basename of path provided)
then, in debian/rules:
dh --with apparmor
Thanks Steve.
Yes - I was thinking about something like a .apparmor file that tells
dh_apparmor what it needs.
Without the dh sequencer, we're requiring two things:
1) For the packager to understand *where* to put the override
2) For the packager to specify information needed by dh_apparmor
Hey Robie,
I'm not particularly clueful when it comes to debhelper, but I don't
really see how to accomplish this given what knowledge dh_apparmor
has/doesn't have. It needs to know what profile(s) to create a local
file for, as well as to reload; this is why the --profile-name argument
is
To clarify, I mean that the existing dh_apparmor needs to be passed the
profile name and potentially the package name as well as it has no means
currently of discerning what those might be, which means there's no
current way to get around requiring the packager to manually add the
dh_apparmor call
To be clear, I'm expecting that a debian/rules file that calls dh should
not need to explicitly call dh_apparmor at all, and that AppArmor
profiles will end up loaded before any corresponding service installed
with dh_installinit is started.
--
You received this bug notification because you are
9 matches
Mail list logo
