A System and Service Manager
efa3d301b9
... (rhbz#2164594) The socket exists and is enabled in the initrd. After switch-root, the system goes into an infinite loop trying to stop the socket while incoming audit messages trigger start jobs for the socket. This is a bug in the transaction logic, that'll need to be fixed separately. We need to preset the socket after the upgrade so that it remains enabled by default. This should fix the boot issue, though it's not a complete fix, because we actually want to allow people to disable the socket. On initial install, the socket is covered by preset-all and gets enabled. |
||
|---|---|---|
| tests | ||
| .gitignore | ||
| .zuul.yaml | ||
| 10-oomd-defaults.conf | ||
| 10-oomd-per-slice-defaults.conf | ||
| 20-yama-ptrace.conf | ||
| changelog | ||
| fedora-use-system-auth-in-pam-systemd-user.patch | ||
| inittab | ||
| libsystemd-shared.abignore | ||
| macros.sysusers | ||
| owner-check.sh | ||
| owner-check.template | ||
| purge-nobody-user | ||
| README.build-in-place.md | ||
| rpminspect.yaml | ||
| sources | ||
| split-files.py | ||
| sysctl.conf.README | ||
| systemd-journal-gatewayd.xml | ||
| systemd-journal-remote.xml | ||
| systemd-udev-trigger-no-reload.conf | ||
| systemd.rpmlintrc | ||
| systemd.spec | ||
| sysusers.attr | ||
| sysusers.generate-pre.sh | ||
| sysusers.prov | ||
| triggers.systemd | ||
| use-bfq-scheduler.patch | ||
| yum-protect-systemd.conf | ||
Building systemd rpms for local development using rpmbuild --build-in-place
This approach is based on filbranden's git-rpmbuild and his talk during ASG2019.
git clone https://github.com/systemd/systemd
fedpkg clone systemd fedora-systemd
cd systemd
rpmbuild -bb --build-in-place --noprep --define "_sourcedir $PWD/../fedora-systemd" --define "_rpmdir $PWD/rpms" --with inplace ../systemd.spec
sudo dnf upgrade --setopt install_weak_deps=False rpms/*/*.rpm
--without lto and --without tests may be useful to speed up the build.