On Sun, 08 Sep 2019 at 11:12:57 +0200, intrig...@debian.org wrote:
> In order to better support partial upgrades and to ensure that
> migration to testing happens in the correct order, it would be sweet
> if we could prevent folks from upgrading to mutter >= 3.33.3
> without also upgrading apparmor to 2.13.3.5.
That makes sense. I've queued this in git for experimental. I'm not
uploading right now, since I'm not yet running GNOME 3.33 myself (I'm
trying to get fixes for 3.30.x into unstable and then stable before
GNOME 3.33/3.34 starts to land).
> I guess this should do the job (perhaps with the corresponding
> Replaces on top):
>
> Breaks: apparmor (<< 2.13.3-5~)
>
> If I got this wrong and this should instead be handled in
> src:apparmor, please let me know.
I think you are correct to say that this should be represented by a
Breaks in mutter (more precisely libmutter-5-0, which is the component
that creates these files).
Replaces is not desirable here, because mutter does not overwrite any files
included in apparmor.
smcv
