[pkg-apparmor] Bug#968607: Bug#968607: Bug#968607: pidgin-openpgp: AppArmor profil prevents execution of XEP-0027.pl

[intrigeri]

Hi Seth,

Seth Arnold (2020-10-30):
> On Thu, Oct 29, 2020 at 09:14:55AM +0100, intrigeri wrote:
>> I believe that in practice, during a Buster → Bullseye upgrade,
>> pidgin-openpgp will be removed anyway because libgtk2-perl will get
>> removed. So in this context, having this Conflicts or not does not
>> matter much. (I understand Ubuntu adopted a different strategy wrt.
>> deprecating libgtk2-perl so things would look different there.)
>
> Oh curious, I'm not accustomed to 'leaf' packages being removed on
> upgrades; for example, on my Focal system now, I've got eight packages
> installed that aren't available for download.

They're not removed as long as they're still co-installable with more
important packages, i.e. they don't block the rest of the upgrade.
In the case at hand case, during a Buster → Bullseye upgrade, the
previously installed libgtk2-perl from Buster:

 - won't have upgrades available 
 - depends on perlapi-5.28.0, which is a virtual package
   perl-base (5.28.1-6)
 - perl-base will need to be upgraded to 5.3x from Bullseye

So it won't be co-installable with the newer perl-base.
Then I expect the package manager to offer, as a resolution,
to remove libgtk2-perl, and in turn, its reverse-dependencies,
such as pidgin-openpgp.

> Anyway, thanks for the quick turnaround. :) I appreciate it.

You're welcome, thank *you* for paying attention :)