[pkg-apparmor] Heads up: please test AppArmor 2.10 packages

[Christian Boltz]

Hello,

Am Montag, 17. August 2015 schrieb Felix Geyer:
> On 17.08.2015 09:37, intrigeri wrote:
> > they're in experimental, so you folks who're running testing/sid may
> > need manual action to upgrade to them. Let's please eat our own
> > dog food and use them :)
> 
> apparmor is missing a dependency on python3-apparmor (>= 2.10):
> 
> % sudo aa-status
> Traceback (most recent call last):
>   File "/usr/sbin/aa-status", line 16, in <module>
>     from apparmor.fail import enable_aa_exception_handler
> ImportError: No module named 'apparmor.fail'
> 
> I guess we should add
> Depends: python3-apparmor (>= ${source:Upstream-Version})
> 
> or possibly something stricter.

No ;-)  (assuming you have the other aa-* tools in a separate package 
with a dependency on python3-apparmor)

I introduced the dependency on apparmor.fail without knowing that Debian 
and Ubuntu use aa-status in the debhelper and want minimal dependencies 
there.

Please use the upstream solution instead, which means to wrap the two 
lines in a try/except. Steve sent that as patch on Aug 1st and it's 
already acked, but he didn't commit it yet. Therefore you'll have to 
copy and paste the patch from his mail [1] - or ping him to finally 
commit it ;-)

BTW: The long term solution will probably be a small aa-enabled script, 
which might even be written as bash script.

And to answer intrigeri's note in the next mail: yes, please use 
versioned dependencies.


Regards,

Christian Boltz

[1] Subject: [apparmor] [patch] utils: make aa-status(8) function
              without python3-apparmor

-- 
Most languages allow you to shoot your own foot,
C just gives you a tank instead of a handgun ;-)
[Cristian Rodríguez in opensuse-factory]