v253 batch

.semaphore/semaphore-runner.sh

@@ -6,7 +6,7 @@ set -o pipefail
 
 # default to Debian testing
 DISTRO="${DISTRO:-debian}"
-RELEASE="${RELEASE:-bullseye}"
+RELEASE="${RELEASE:-bookworm}"
 BRANCH="${BRANCH:-upstream-ci}"
 ARCH="${ARCH:-amd64}"
 CONTAINER="${RELEASE}-${ARCH}"

NEWS

@@ -3374,7 +3374,7 @@ CHANGES WITH 248:
           and PKCS#11 security tokens to LUKS volumes, list and destroy
           them. See:
 
-          http://0pointer.net/blog/unlocking-luks2-volumes-with-tpm2-fido2-pkcs11-security-hardware-on-systemd-248.html
+          https://0pointer.net/blog/unlocking-luks2-volumes-with-tpm2-fido2-pkcs11-security-hardware-on-systemd-248.html
 
           It also supports enrolling "recovery keys" and regular passphrases.
 
@@ -11858,7 +11858,7 @@ CHANGES WITH 215:
           system with /etc empty cleanly. For more information on the
           concepts involved see this recent blog story:
 
-          http://0pointer.de/blog/projects/stateless.html
+          https://0pointer.de/blog/projects/stateless.html
 
         * A new system group "input" has been introduced, and all
           input device nodes get this group assigned. This is useful
@@ -14596,7 +14596,7 @@ CHANGES WITH 193:
           journal. This will be extended later on. Here's an example
           screenshot of this app in its current state:
 
-          http://0pointer.de/public/journal-gatewayd
+          https://0pointer.de/public/journal-gatewayd
 
         Contributions from: Kay Sievers, Lennart Poettering, Robert
         Milasan, Tom Gundersen
@@ -15535,7 +15535,7 @@ CHANGES WITH 38:
           ssh://git.freedesktop.org/git/systemd/systemd
 
         * First release with the journal
-          http://0pointer.de/blog/projects/the-journal.html
+          https://0pointer.de/blog/projects/the-journal.html
 
         * The journal replaces both systemd-kmsg-syslogd and
           systemd-stdout-bridge.

docs/CONTAINER_INTERFACE.md

@@ -170,7 +170,7 @@ manager, please consider supporting the following interfaces.
    `SIGRTMIN+3` like this, this might confuse other init systems.
 
 4. To support [Socket Activated
-   Containers](http://0pointer.de/blog/projects/socket-activated-containers.html)
+   Containers](https://0pointer.de/blog/projects/socket-activated-containers.html)
    the container manager should be capable of being run as a systemd
    service. It will then receive the sockets starting with FD 3, the number of
    passed FDs in `$LISTEN_FDS` and its PID as `$LISTEN_PID`. It should take
@@ -181,9 +181,9 @@ manager, please consider supporting the following interfaces.
    activation work. The protocol to hand sockets from systemd to services is
    hence the same as from the container manager to the container systemd. For
    further details see the explanations of
-   [sd_listen_fds(1)](http://0pointer.de/public/systemd-man/sd_listen_fds.html)
+   [sd_listen_fds(1)](https://0pointer.de/public/systemd-man/sd_listen_fds.html)
    and the [blog story for service
-   developers](http://0pointer.de/blog/projects/socket-activation.html).
+   developers](https://0pointer.de/blog/projects/socket-activation.html).
 
 5. Container managers should stay away from the cgroup hierarchy outside of the
    unit they created for their container. That's private property of systemd,

docs/CREDENTIALS.md

@@ -75,7 +75,7 @@ Within unit files, there are four settings to configure service credentials.
 2. `SetCredential=` may be used to set a credential to a literal string encoded
    in the unit file. Because unit files are world-readable (both on disk and
    via D-Bus), this should only be used for credentials that aren't sensitive,
-   i.e. public keys/certificates – but not private keys.
+   e.g. public keys or certificates, but not private keys.
 
 3. `LoadCredentialEncrypted=` is similar to `LoadCredential=` but will load an
    encrypted credential, and decrypt it before passing it to the service. For

docs/ROOT_STORAGE_DAEMONS.md

@@ -188,6 +188,6 @@ few additional notes for supporting these setups:
   written in a way that does not negatively impact usability on non-systemd
   systems. For more information on making use of socket activation in your
   program consult this blog story: [Socket
-  Activation](http://0pointer.de/blog/projects/socket-activation.html)
+  Activation](https://0pointer.de/blog/projects/socket-activation.html)
 
 * Consider having a look at the [initrd Interface of systemd](INITRD_INTERFACE.md).

docs/index.md

@@ -27,8 +27,8 @@ Other parts include a logging daemon, utilities to control basic system configur
 
 ## See also
 
-* [Introductory blog story](http://0pointer.de/blog/projects/systemd.html)
-* [Three](http://0pointer.de/blog/projects/systemd-update.html) [status](http://0pointer.de/blog/projects/systemd-update-2.html) [updates](http://0pointer.de/blog/projects/systemd-update-3.html)
+* [Introductory blog story](https://0pointer.de/blog/projects/systemd.html)
+* [Three](https://0pointer.de/blog/projects/systemd-update.html) [status](https://0pointer.de/blog/projects/systemd-update-2.html) [updates](https://0pointer.de/blog/projects/systemd-update-3.html)
 * The [Wikipedia article](https://en.wikipedia.org/wiki/systemd)
 
 ---

docs/sysvinit/README.in

@@ -23,5 +23,5 @@ Thank you!
 Further reading:
         man:systemctl(1)
         man:systemd(1)
-        http://0pointer.de/blog/projects/systemd-for-admins-3.html
+        https://0pointer.de/blog/projects/systemd-for-admins-3.html
         https://www.freedesktop.org/wiki/Software/systemd/Incompatibilities

docs/var-log/README.logs

@@ -22,4 +22,4 @@ Further reading:
         man:journalctl(1)
         man:systemd-journald.service(8)
         man:journald.conf(5)
-        http://0pointer.de/blog/projects/the-journal.html
+        https://0pointer.de/blog/projects/the-journal.html