There is 1 open security issue in sid.
There is 1 open security issue in forky.
There are 3 open security issues in bullseye.
commit 9bf2cc9eca3f89ebfbe68de5599d09505019041b
Author: Nick Rosbrook <enr0n@ubuntu.com>
Date: Thu Oct 22 10:52:10 2026 -0500
d/t/upstream: remove all nura mkosi config on Ubuntu
Older mkosi will fail if any configuration mentions nura, so just
remove the config at test time.
Gbp-Dch: Short
commit b889bfd3d6dfb614edac6c85201bb3edb8c379a0
Author: Nick Rosbrook <enr0n@ubuntu.com>
Date: Thu Jul 2 13:41:17 2026 -0400
d/t/upstream: skip remaining problematic tests
A handful of these just require features from mkosi that are not
available in v26, so skip those until it's available.
The other two tests require swtpm, and the VMs just never appear to boot
on Ubuntu autopkgtest infra, but are okay on other hardware (e.g. local
VM).
There are open issues remaining for these, but we need to skip these for
now to move systemd along.
Gbp-Dch: Short
commit e8422a458ba304a7d333b238d1def88986321758
Author: Nick Rosbrook <enr0n@ubuntu.com>
Date: Thu Oct 22 21:32:25 2026 -0500
d/t/boot-and-services: use busybox-static
commit ea6ae0db3d1f6dd3916d4ce6a29c6458d65b27a0
Author: Emil Renner Berthing <esmil@mailme.dk>
Date: Sun Nov 1 06:56:46 2026 -0500
Use defaults for mDNS enablement
It is quite confusing that most systemd-resolved
options have defaults that can be changed in /etc/systemd/resolved.conf,
but changing the MulticastDNS option here has no effect.
Instead of overriding this setting with a file in
/usr/lib/systemd/resolved.conf.d/00-multicast-dns.conf
just rely on defaults like other resolved options.
commit eeb5b5ea4299540a9c9e3f69b3c104a05ea5f3e4
Author: Luca Boccassi <luca.boccassi@gmail.com>
Date: Mon Nov 9 10:26:27 2026 +0000
Install new files for upstream build
Gbp-Dch: ignore
commit e6266d8ca4e237dbbf06732b5907d4af4ec0c701
Author: Luca Boccassi <luca.boccassi@gmail.com>
Date: Sat Nov 7 11:05:41 2026 +0000
Install new files for upstream build
Gbp-Dch: ignore
There are 3 open security issues in trixie.
You can find information about how to handle these issues in the security team's documentation.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/s/systemd.png){kind=link}