Hi
Am 21. September 2016 09:03:03 MESZ, schrieb Per Jessen
I am unfamiliar with the systems management processes for this server - I think the update happened automagically, it looks like it's done as a daily cron-job.
Right: all openSUSE servers have a cron job running each day (around 19:30 +- 15min) that updates all packages that do not have a "license to confirm" (which is used by kernel updates for example). Additionally, there is a monitoring check around 20:00 running zypper to check for pending updates (like the kernel one, which does not get installed automatically) and packages from alien repositories (means 3rd party packages not provided via official repos) that are not acknowledged by the admin. If there is a package in the official repo that should be updated to solve a problem, we open a bug report to get this fixed the official way.
For baloo, I can easily extract the newer mlmmj profiles from apparmor-profiles-2.10, and add them into /etc/apparmor.d/local/, but it seems to me that apparmor-profiles in SLE12-SP1 needs to be updated?
(even if not very many people use mlmmj).
As mlmmj is not part of the official repository provided by SUSE, I would recommend to add the profile to the mlmmj package or distribute it via configuration management. As it is a config file, I would normally recommend to use the 2nd approach, but I guess we might be able to generate a generic apparmor profile that can help others if it gets integrated in the mlmmj package. But it's up to you to decide as admin :-) CU, Lars -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org