Package: snapd
Version: 2.37.4-1
Severity: normal
X-Debbugs-Cc: Jamie Strandboge <[email protected]>
Hi,
One of the Ubuntu maintainers for src:apparmor (Jamie, Cc'ed) has
recently added a "Breaks: snapd (<< 2.38~)" relationship for the
apparmor binary package, justified by the fact that in earlier
versions of snapd, "snap remove" is incompatible with the way AppArmor
maintains its compiled policy cache in /var/cache/apparmor since
2.13.2. I blindly trust Jamie's reasoning so I've merged this change
in apparmor 2.13.3-1.
So we have two problems in Debian now:
1. Buster is presumably affected by the "snap remove" breakage
Jamie:
- Can you please shed some light on what's the exact problem
and user impact?
- Can easily point us to the fixes brought by snapd 2.38
in this area?
I'd like to understand whether this is severe enough to warrant
fixing it in a Buster point-release, and whether the fix has
a chance to be accepted by the SRMs.
2. apparmor >= 2.13.3-1 cannot migrate to testing as it breaks
co-installability with snapd
This could be fixed by uploading snapd 2.38 or newer to sid.
Dear snapd maintainers, what are your plans in this respect?
Cheers,
--
intrigeri
