Comment # 14 on bug 881762 from
Bug present in OpenSUSE v12.3

Hi,
first let me explain that I am not a developer, although I've been a Linux home
user since Redhat was v7.3 ( more than 10 years), I'm not a developer.

So the things you have asked me to do make no sense, apart that is that you're
after using older versions of the code and have asked about my need for
"yast2-apparmor".

To answer the last question first. No, I don't actually need YaST2 when I work
with Apparmor. I've recently come to OpenSUSE from Ubuntu, so have learnt
Apparmor from the command line. But, upon seeing the YaST2 option for Apparmor,
I couldn't help but think "how civilized", which was why I started using it.

To help with your troubleshooting I downloaded a copy of OpenSUSE v12.3 and
have installed it on a spare partition. I then repeated the process shown in
the first post and low and behold, got the same issue (the removal of the
#include line from outside of the main body of the profile).

Looking at files in /usr/share/YaST2/include/apparmor and
/usr/share/YaST2/clients I note that in OpenSuse v13.1 and v13.2 these are Ruby
(extension "rb") files, while in v12.3 they have an extension of "ycp"
(Python?). This, to me, suggests that the problem was there before the Ruby
re-write.

Additional information: version of "yast2-apparmor" in OpenSUSE v12.3 is
2.22.2-4.1.2

One final thought, "yast2-apparmor" is an installed part of OpenSUSE v13.1 and
v13.2 which was why I saw it and used it, but is a separate install in OpenSUSE
v12.3. Should it have been part of v13.1, if it was a separate install in
v12.3?

cheers
Tony


You are receiving this mail because: