Mailinglist Archive: opensuse-packaging (118 mails)
< Previous | Next > |
[opensuse-packaging] Re: systemd presets vs. package install order
- From: Yamaban <foerster@xxxxxxxx>
- Date: Mon, 15 Jun 2015 12:53:34 +0200 (CEST)
- Message-id: <alpine.LFD.2.11.1506151247040.15791@rhlx01.hs-esslingen.de>
On Mon, 15 Jun 2015 12:40, Jan Engelhardt wrote:
IMHO this problem should be addressed at the root cause:
The install of "systemd" should include a
"Require: systemd-presets-branding-openSUSE" and thus
make shure it's installed before any other services.
Or a full workaround in Apparmour in the "%pre"
sequence to force the install of
"systemd-presets-branding-openSUSE" before
Apparmour in really installed.
- Yamaban.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx
On Monday 2015-06-15 12:34, Andreas Schwab wrote:
Christian Boltz writes:
AppArmor has a preset "enable by default" (in the separate systemd-
presets-branding-openSUSE), but unfortunately the AppArmor package gets
installed before systemd-presets-branding-openSUSE gets installed.
How did that happen? Didn't it require %systemd_requires?
Well, few packages *actually* require systemd.
IMHO this problem should be addressed at the root cause:
The install of "systemd" should include a
"Require: systemd-presets-branding-openSUSE" and thus
make shure it's installed before any other services.
Or a full workaround in Apparmour in the "%pre"
sequence to force the install of
"systemd-presets-branding-openSUSE" before
Apparmour in really installed.
- Yamaban.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx
< Previous | Next > |