[pkg-apparmor] Fixing apps that use Glycin [Was: Interest in backporting AppArmor 5 to Trixie once released?]
intrigeri
intrigeri at debian.org
Mon Apr 27 10:08:43 BST 2026
Hi,
Aaron Rainbolt (2026-04-23):
> A quick update on where I'm at so far; I was able to extract the
> Glycin-related apparmor.d profiles into a dedicated abstractions/glycin
> mechanism that works on LibreOffice and Evince on Debian Testing.
> Currently roddhjav (apparmor.d's maintainer) is helping me get the
> profiles into a state both of us are happy with so they can be
> upstreamed into AppArmor itself. I should have an MR to upstream
> *possibly* before the end of the month, depending on how things go.
> Once that's upstreamed, I'll package the patch and submit it for your
> review (and I'll keep you in the loop once I get an MR made).
Lovely, thank you so much!
> Patrick (adrelanos) and I discussed using an AppArmor 5 backport in
> Whonix in the future, and even though this email started with a backport
> request, I think we actually won't (at least immediately) use one if it
> were to happen. Neither me nor Patrick expected that there could be
> compatibility issues that ABI declarations in AppArmor profiles couldn't
> work around, and we don't want to maintain modified AppArmor profiles
> for apps we don't maintain downstream.
Fully understood. Adjust subject accordingly.
> That being said, we are still
> interested in helping with maintenance since AppArmor is very useful to
> us and we'll want things to work smoothly in Debian 14 and beyond.
I'm glad to read this :)
> Also, apparmor.d seems to be expecting a backport to exist at some
> point (see the end of
> https://github.com/roddhjav/apparmor.d/issues/967), so it might still
> be worthwhile.
I see, we can consider this once this is actually requested (and
we'll see how close we are to the Forky release, too).
Cheers,
--
intrigeri
More information about the pkg-apparmor-team
mailing list