A System and Service Manager
b36512ad8f
I'm not entirely sure if this is the right form... Is Conflicts? useful when we have Obsoletes? Seem to work OK. I tested: dnf --installroot=... install x86_64/systemd-standalone-sysusers-246.6-2.fc34.x86_64.rpm x86_64/systemd-standalone-tmpfiles-246.6-2.fc34.x86_64.rpm → succeeds with a new installation → fails if the installroot already had systemd installed dnf --installroot=... install x86_64/systemd{,-libs,-pam}-246.6-2.fc34.x86_64.rpm noarch/systemd-noarch-246.6-2.fc34.noarch.rpm → uninstalls the two standalone packages |
||
---|---|---|
tests | ||
.gitignore | ||
20-grubby.install | ||
20-yama-ptrace.conf | ||
0001-Do-not-assert-in-test_add_acls_for_user.patch | ||
0001-Revert-test-path-increase-timeout.patch | ||
0001-test-acl-util-output-more-debug-info.patch | ||
0002-test-path-more-debugging-information.patch | ||
0003-test-path-do-not-fail-the-test-if-we-fail-to-start-s.patch | ||
0004-test-path-use-Type-exec.patch | ||
f58b96d3e8d1cb0dd3666bc74fa673918b586612.patch | ||
inittab | ||
libsystemd-shared.abignore | ||
macros.sysusers | ||
purge-nobody-user | ||
sources | ||
split-files.py | ||
sysctl.conf.README | ||
systemd-journal-gatewayd.xml | ||
systemd-journal-remote.xml | ||
systemd-udev-trigger-no-reload.conf | ||
systemd-user | ||
systemd.rpmlintrc | ||
systemd.spec | ||
sysusers.attr | ||
sysusers.generate-pre.sh | ||
sysusers.prov | ||
triggers.systemd | ||
use-bfq-scheduler.patch | ||
yum-protect-systemd.conf |