systemd (261-2) unstable; urgency=medium

  - Three new packages have been split out of the main systemd binary
    package, in order to reduce the default dependencies footprint:

    - systemd-tpm
    - systemd-imds
    - systemd-report

    It is advised to take special care regarding the first one, as it
    will be necessary to pull it in for initrd builds for the TPM2
    integration. A temporary dependency systemd -> systemd-tpm was
    added to facilitate migration, but it will be downgraded in the near
    future to Recommends.

 -- Luca Boccassi <bluca@debian.org>  Wed, 24 Jun 2026 22:15:24 +0100

systemd (258~rc1-1) experimental; urgency=medium

  - Support for legacy cgroupv1 has been completely removed. Any
    remaining override to force back cgroupv1 will no longer work.

  - Support for various deprecated SysV interfaces has been removed:
    - world-writable /run/lock/: unprivileged services must switch to
      RuntimeDirectories= and unprivileged users must switch to
      $XDG_RUNTIME_DIR. $TMPDIR can be used as a further fallback.
    - telinit
    - runlevel
    - runlevel targets

  - Support for SysV init scripts is retained for this release, but will
    be dropped in v259, due by the end of 2025. Any package intending
    to ship in Forky and work under systemd needs to start shipping a
    unit file within the Forky development cycle.

 -- Luca Boccassi <bluca@debian.org>  Sat, 05 Jul 2025 13:19:15 +0100

systemd (256-2) unstable; urgency=medium

  cryptsetup tools such as systemd-cryptsetup, systemd-cryptenroll,
  systemd-veritysetup, and more, have been split into a new systemd-cryptsetup
  package to reduce dependencies pulled in by the main systemd package. This
  new package is only listed as a Recommends, so if this functionality is used
  ensure that either Recommends are installed (default) or that it is
  manually installed.

 -- Luca Boccassi <bluca@debian.org>  Tue, 10 Sep 2024 18:19:16 +0200

systemd (256~rc3-3) unstable; urgency=medium

  - /tmp/ is now by default a tmpfs, via the tmp.mount unit provided upstream.
    The old default setup can be retained simply by masking the unit locally
    with (do not do this if you are defining /tmp/ manually in /etc/fstab):

    systemctl mask tmp.mount

    or:

    touch /etc/systemd/system/tmp.mount

    It is recommended to check /tmp/ for any leftover files before rebooting
    after installing this update and manually cleaning up, as the directory
    will no longer be cleaned up automatically on boot, as it is overmounted.
    It is always possible to remount the root filesystem in a local directory
    and remove leftovers manually after rebooting, but this will not be done
    automatically to avoid unintential removals. This situation can be easily
    detected by checking the journal after a reboot, as there will be a log
    message that says:

    tmp.mount: Directory /tmp to mount over is not empty, mounting anyway

  - /run/lock/ is no longer created with a patch before units start, but by
    a standard early-boot run-lock.mount unit that is ordered before
    local-fs.target. Any service needing to use /run/lock/ and running before
    sysinit.target (ie, they likely define DefaultDependencies=no) will need
    to be explicitly ordered with After=run-lock.mount. The two known cases
    where this happens in the archive have a bug+MR filed already.

  - On new installations, tmpfiles.d will now cleanup by default files
    that have not been changed or accessed on /tmp/ for 10 days, and /var/tmp/
    for 30 days. The legacy behaviour can be configured with a local override
    if needed:

    echo 'D /tmp 1777' > /etc/tmpfiles.d/tmp.conf

    This override will be automatically provided for upgrades of existing
    systems from previous releases to Trixie. As a reminder, individual
    files and directories can be marked for exclusion from cleanups with
    the 'x' type configuration line as described in the tmpfiles.d manpage,
    for example:

    echo 'x /tmp/my-precious' > /etc/tmpfiles.d/precious.conf

  - coredumps are now disabled by default via configuration files rather than
    an out-of-tree patch (installing the optional systemd-coredump package
    will enable them as before). As always, overriding via local drop-ins is
    possible if desired. The configuration files that respectively affect
    the system systemd instance, the user systemd instances and PAM sessions
    are:

    /usr/lib/systemd/system.conf.d/10-coredump-debian.conf
    /usr/lib/systemd/user.conf.d/10-coredump-debian.conf
    /usr/lib/sysctl.d/10-coredump-debian.conf
    /etc/security/limits.d/10-coredump-debian.conf

 -- Luca Boccassi <bluca@debian.org>  Tue, 28 May 2024 00:07:57 +0100

systemd (256~rc2-1) unstable; urgency=medium

  In the rare case a scheduled shutdown fails to be enqueued (most
  likely, D-Bus daemon/broker is not installed), the system will now
  immediately reboot, restoring the default behaviour intended upstream.

 -- Luca Boccassi <bluca@debian.org>  Wed, 15 May 2024 00:40:56 +0100
