http://bugzilla.opensuse.org/show_bug.cgi?id=881762 --- Comment #15 from Christian Boltz --- (In reply to Tony Pattison from comment #14)

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

The reason for asking for old versions is to find out when the bug was introduced.

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.

Thanks for the information. It was "just" a side question because I (disclaimer: I'm also one of the AppArmor upstream developers) was curious about the reasons to use the YaST module.

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).

So now we know that this is an "old" bug, and nothing introduced recently. That's already valueable information, even if I'd have preferred an answer like "introduced last month" because that would make debugging easier ;-)

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?).

No, YCP was a programming language "invented" for YaST (and not used otherwise AFAIK).

This, to me, suggests that the problem was there before the Ruby re-write.

Right.

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?

Hmm, good point. Given the current state of this YaST module, I'm surprised why it's installed by default now. It might be a good idea not to install it by default. Please don't get me wrong - I'd really like to have a fully working YaST module, but unfortunately it's based on deprecated code and has no maintainer, which makes things quite hard :-( -- You are receiving this mail because: You are on the CC list for the bug.