No functional change, this is just to satisfy my internal OCD since the package
description otherwise looks... off:
$ rpm -qi systemd-container
Name : systemd-container
Version : 256
Release : 15.el10
Architecture: x86_64
Install Date: Wed 23 Oct 2024 09:33:06 AM EDT
Group : Unspecified
Size : 1479381
License : LGPL-2.1-or-later
Signature : (none)
Source RPM : systemd-256-15.el10.src.rpm
Build Date : Tue 15 Oct 2024 09:22:45 AM EDT
Build Host : x86-64-02.build.eng.rdu2.redhat.com
Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Vendor : Red Hat, Inc.
URL : https://systemd.io
Summary : Tools for containers and VMs
Description :
Systemd tools to spawn and manage containers and virtual machines.
This package contains systemd-nspawn, machinectl,
systemd-machined, and systemd-importd.
Follow-up for a591ab1d82.
Related: RHEL-58765
Even on non-uefi architectures, ukify can be used to build UKIs for
UEFI images. For example, mkosi can use it to build UKIs on s390x.
To enable this use case, let's always build ukify, but with a conditional
dependency on systemd-boot only on arches that support UEFI.
(cherry picked from commit a67221c3f0d0b81b9b5b3230a71d09044342f1a4)
Resolves: RHEL-52634
Since the tests repo is not accessible there. The `rpm-tmt-test` job
will still fail, since with this change it will complain about an empty
test plan, but that's something to (possibly) fix in the near future.
- A bunch of various fixes for memory and behaviour, in many different
components (bootctl, systemd, udev, systemd-networkd, systemd-homed,
systemd-logind, systemd-resolve, systemd-repart, systemd-analyze,
systemd-dissect, systemd-boot, pam modules, systemd-storagetm,
systemd-journal-remote, kernel-install)
- Improved detection of virtualization (Google Compute Engine, Apple Virt)
- Updates for shell completions and docs
- An update for hardware database
Our config files in /etc/ were marked as %config(noreplace). This means that the
would not be replaced on upgraded if local modifications have been made. But
when we moved them to /usr/lib, they would be be renamed to .rpmsave, if they
had local modifications. This is not what I expected, but what rpm apparently
does. So we need to add them as %ghost to prevent the removal. This is probably
for the better anyway.
This is a bit of a mess: sshd can only load configuration from
/etc/ssh/sshd_config.d, and that directory is declared as non-world-readable.
This is in violation of the packaging guidelines which say that packaged files
must be world-readable, and also makes very little sense, since those files
are part of the package payload.
If we create the directory with different permissions, and list it in %files,
installation will fail. If we don't list it in %files, and the user doesn't have
openssh-server installed, they will have an unowned directory. Another option
would be to depend on owner of this directory, i.e. openssh-server, but we don't
want to have that dependency. So let's copy the %files line from openssh-server
and figure out what to do if it changes in openssh-server again.
... (e.g. /etc/systemd/system.conf → /usr/lib/systemd/systemd.conf).
Both config file locations were already supported, and the files
installed in /etc/ were "empty" (i.e. they had only comments and section
headers). The move does not change the configuration, but just makes
/etc more empty by default. See
https://github.com/systemd/systemd/commit/6495361c7d for more
discussion and details.
We would fail later anyway, because rpm refuses %files with an empty filelist
file. But this is much later, after %check, so let's fail already in %install.
[skip changelog]
