There is 1 open security issue in sid.
There is 1 open security issue in forky.
commit bcdf90c6707ecc0626543bea649bf8be790b160e
Author: Johannes Schauer Marin Rodrigues <josch@debian.org>
Date: Fri Jul 3 23:17:15 2026 +0200
debian/libpam-systemd.postinst: pam-auth-update does not use getopt
Option names and arguments must not be connected with an equal sign but
be separate entries in argv.
commit 743e3399acdb699541d3ec7e05f49c05d47e503d
Author: Luca Boccassi <luca.boccassi@gmail.com>
Date: Fri Jul 3 19:29:08 2026 +0100
d/README.source: document policy for adding new binary packages
Gbp-Dch: ignore
commit cbea74783ce9475c8baa8a6f8c2f8413b1094268
Author: Luca Boccassi <luca.boccassi@gmail.com>
Date: Fri Jul 3 19:11:48 2026 +0100
Install new files for upstream build
Gbp-Dch: ignore
commit ef267b3ad65d366b7be5059fd6ddff8caf14e0ed
Author: Johannes Schauer Marin Rodrigues <josch@debian.org>
Date: Thu Jul 2 11:12:00 2026 +0200
debian/libpam-systemd.postinst: run pam-auth-update with --root=$DPKG_ROOT
If $DPKG_ROOT is set and not empty (this happens if dpkg is run with
--force-script-chrootless) let pam-auth-update operate on a different
directory by passing the --root parameter. Passing the root parameter
is no longer needed if pam-auth-update switches to $DPKG_ROOT as the
default for --root. See #1137186.
Changing the calls to pam-auth-update in the prerm scripts is not
necessary because package removal is not supported with chrootless mode.
systemd-homed is not patched because there was yet no use-case (and thus
also no tests in the dpkg-root-demo salsa CI pipeline) for installing
that package. We want to keep this patch and changes minimal.
This change should introduce zero behavioral change in the "normal case"
because for regular installations, DPKG_ROOT will be empty and thus the
pam-auth-update will be identical to how it always has been.
commit 54df2859b4a47e6a95e4ccce2d8f8c0283019bd7
Author: Nick Rosbrook <enr0n@ubuntu.com>
Date: Tue Jun 30 12:15:28 2026 -0400
d/t/upstream: use mkosi from archive for Ubuntu autopkgtest
In Ubuntu, we do not want to rely on mkosi from git because that
requires Restrictions: needs-internet and is not guaranteed. Add logic
to the script so that when running for Ubuntu (and not for upstream
tests), mkosi is not pulled from git, and instead is used from the
archive.
Gbp-Dch: Short
commit 21959e8a5937941048672f583e57e9072e0a4268
Author: Luca Boccassi <luca.boccassi@gmail.com>
Date: Sun Jun 28 11:10:49 2026 +0100
Fix zsh installation path, again
Follow-up for e31737edc4a116db3edbe7a13891e24537af6350
Gbp-Dch: ignore
commit f01dddb047b1f472b28b8c07ffddc26b912fe86e
Author: Luca Boccassi <luca.boccassi@gmail.com>
Date: Sun Jun 28 10:48:44 2026 +0100
Fix zsh installation path
Follow-up for e31737edc4a116db3edbe7a13891e24537af6350
Gbp-Dch: ignore
commit e31737edc4a116db3edbe7a13891e24537af6350
Author: Luca Boccassi <luca.boccassi@gmail.com>
Date: Sun Jun 28 10:31:37 2026 +0100
Install new files for upstream build
There is 1 open security issue in trixie.
You can find information about how to handle this issue in the security team's documentation.
There is 1 open security issue in bookworm.
You can find information about how to handle this issue in the security team's documentation.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/s/systemd.png){kind=link}