Hi,

First, for a variety of reasons, the preferred way to add AppArmor policy to
Debian (short of having it maintained upstream) is to include it in the package
that ships the confined software, so it can be tested together with software
updates, and the maintainer is the best placed to tell whether a specific newly
denied access is legitimate or not.

So apparmor-profiles-extra was always meant to be a temporary hack. The amount
of profiles shipped in that package has been decreasing a fair bit and we're now
down to 2 profiles + 1 abstraction that's not used anywhere, except by
fwknop-apparmor-profile (#1147157).

Additionally, it's always been awkward to maintain the profiles shipped in this
package, with no automated mechanism to track the multiple sources of input we
use here.

Finally, and this is the last nail in the coffin for me, the main source of
AppArmor profiles for this is deprecated. Not only it was dormant since a year
or 3, with no capacity available for reviewing fixes, but more recently the
corresponding GitLab project was repurposed and does not include the profiles
that we have in apparmor-profiles-extra anymore:
https://lists.ubuntu.com/archives/apparmor/2026-August/014935.html

Thanks!

Hi,

please remove the moreinfo tag once fwknop no longer depends on this package.

   Thorsten

Hi,

Thorsten Alteholz (2026-09-15):

Doing this now :)

Cheers,

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

apparmor-profiles-extra |       1.37 | source, all

------------------- Reason -------------------
ROM; Obsolete upstream
----------------------------------------------

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1147158@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1147158

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)

Thank you,
Jeremy Bícha