https://bugzilla.novell.com/show_bug.cgi?id=720617 https://bugzilla.novell.com/show_bug.cgi?id=720617#c1 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |jsrain@suse.com AssignedTo|jeffm@suse.com |suse-beta@cboltz.de --- Comment #1 from Christian Boltz <suse-beta@cboltz.de> 2011-09-27 21:50:44 CEST --- Good to know someone cares about apparmor and the apparmor yast modules ;-) (if you care enough, feel free to take bug 531512 *eg*) Seriously: Reports.pm and aa-eventd are deprecated upstream (that's why I didn't package them), and seem to be broken as in "they won't see most log messages". Therefore it doesn't really make sense to re-add it IMHO. Some sniplets from discussing this with the upstream developers: [19:55] <sbeattie> yeah, aa-eventd hasn't had any attention in at least 4 years, and is thus considered deprecated by jjohansen and I. [21:10] <jjohansen> cboltz: iirc it sort of works but will miss several/most log entires. [21:11] <jjohansen> the YaST module only requires it because it has a button to turn it on and configure it, so I would say the way to go is disable it [21:11] <jjohansen> at the YaST module [21:13] <jjohansen> in fact I think aa-notify could replace aa-eventd (just not this release) [21:15] <cboltz> another question: can I expect Reports.pm to work? [21:16] <jjohansen> cboltz: hrmm I think it has all the same problems as aa-eventd [21:16] <jjohansen> The big problem was, when these where developed, they where somewhat siloed and the developer did copy and paste coding :/ [21:18] <jjohansen> cboltz: we are slowly trying to put together an api to make things like the YaST module easier [21:19] <jjohansen> at some point it will need to be rewritten, /me plans to have a gui genprof/logprof that YaST would launch I can re-add Reports.pm and aa-eventd to the package if you really want, but I'm afraid that this won't magically solve all problems ;-) The better solution is probably to fix it on the YaST side - even if this means that you just disable the features related to aa-eventd and Reports.pm for now. What's your opinion on this? (If you agree to disable/fix it on the YaST side, I'll of course remove the aa-eventd initscript from the package.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.