There is 1 open security issue in trixie.
There is 1 open security issue in sid.
commit e99fa4e6f153f27d81b79b2019073a52aee83a84 Author: Andrea Bolognani <eof@kiyuko.org> Date: Wed Mar 6 01:20:40 2024 +0100 templates: Adopt across maintscripts This massively reduces code duplication and will make it a lot easier to roll out changes if necessary. Gbp-Dch: Ignore commit cde6d3e45fbad41ff9ac7df08fa6e46cfdcdb9ec Author: Andrea Bolognani <eof@kiyuko.org> Date: Wed Mar 6 01:21:59 2024 +0100 templates: Turn all maintscripts into templates No actual change for now, just setting the stage for what's to come. Gbp-Dch: Ignore commit 66afacc556720ff37c801bbd36195d0cad7f7591 Author: Andrea Bolognani <eof@kiyuko.org> Date: Wed Mar 6 00:36:26 2024 +0100 scripts: Make it possible to turn maintscripts into templates Maintainer scripts are supposed to be completely stand-alone, so it's not possible to create a "library" of common code. We still need to perform the same operations in the context of several binary packages though, so code sharing is still happening - it just takes the crude form of copy and paste. Since we are already processing templates at build time, however, we can extend the existing tooling to work on maintainer scripts too. The idea is fairly simple: we can have a single file that contains various shell snippets, each delimited by specific markers and assigned a unique name; then, in each maintainer script, we can inject the snippets that we need, avoiding duplication. Gbp-Dch: Ignore commit 806dea6354e3530ce7be9cd4e6d7dc4fcb41f50f Author: Andrea Bolognani <eof@kiyuko.org> Date: Wed Mar 6 00:57:22 2024 +0100 scripts: Error out on unknown suffix Make the script robust against random packaging files being turned into templates without implementing proper handling for them first. Gbp-Dch: Ignored commit 03fb4b424bb845f4d66e9f78f3649de551f2d750 Author: Andrea Bolognani <eof@kiyuko.org> Date: Wed Mar 6 02:11:03 2024 +0100 scripts: Sort templates before processing them It just makes for nicer output. Gbp-Dch: Ignore commit f5d3d2c6310127f052bd6958af40f4fdda832f25 Author: Andrea Bolognani <eof@kiyuko.org> Date: Wed Mar 6 01:57:33 2024 +0100 scripts: Use pathlib more Instead of performing string manipulation, use pathlib for semantic access to the various parts of each path. Gbp-Dch: Ignore commit 73d94b57ac6025fd9abcb2e79108fe7464f42da6 Author: Andrea Bolognani <eof@kiyuko.org> Date: Wed Mar 6 02:01:15 2024 +0100 scripts: Use better name for variable It's not used for generic "variables", but to store architectures. Name it accordingly. Gbp-Dch: Ignore commit 1a3a1f61f3f43bd2213d0b6b32351961caf2fbcd Author: Andrea Bolognani <eof@kiyuko.org> Date: Thu Feb 29 00:48:40 2024 +0100 install: Turn all into templates This makes for a more consistent experience when editing them, and avoids the churn that would happen in the future if architecture-dependent files were moved between package, or were added to packages that didn't have any until then. The script that processes these templates is fairly fast, so processing a dozen more doesn't cause a noticeable increase in build time. Gbp-Dch: Ignore commit 2d2fd1ae383221d5b9132f7b74deb826db75656f Author: Andrea Bolognani <eof@kiyuko.org> Date: Thu Feb 29 00:47:28 2024 +0100 templates: Move from debian/templates/ to debian/ Turns out that years of habit when it comes to editing files in the debian/ directory are hard to undo :) Keep the templates in the same directory as everything else. For *.install, the output files are only generated at build time so there is no ambiguity and you hardly even notice the difference compared to before. For control, the two files being side by side is still not a big problem, because the suffix can be used to tell the template apart, and I've noticed that getting used to editing that one instead of the output file took hardly any time. Gbp-Dch: Ignore commit 345e3ca4eea14da4a540338117f3df481cfd8cc5 Author: Andrea Bolognani <eof@kiyuko.org> Date: Thu Feb 29 02:00:36 2024 +0100 templates: Drop unnecessary uses of [linux-any] libvirt-daemon and libvirt-daemon-system are only built on Linux, so making these lines conditional is unnecessary. Gbp-Dch: Ignore
There are 7 open security issues in bullseye.
You can find information about how to handle these issues in the security team's documentation.
There are 3 open security issues in bookworm.
You can find information about how to handle these issues in the security team's documentation.
Among the 6 debian patches available in version 10.0.0-2 of the package, we noticed the following issues: