apt/debian, branch 3.1.1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=3.1.12025-06-10T16:06:26ZRelease 3.1.12025-06-10T16:06:26ZJulian Andres Klodejak@debian.org2025-06-10T16:05:29Zurn:sha1:f9b5f49fe6030fc028bc93debf856d1ae75ca7abRelease 3.1.02025-05-19T17:14:52ZJulian Andres Klodejak@debian.org2025-05-19T17:14:11Zurn:sha1:5bfea97d7b3c6f4fcaa56c24d6f3591b1862b86bInclude everything in our pkg-config autopkgtest2025-05-19T17:06:31ZDavid Kalnischkiesdavid@kalnischkies.de2022-12-30T17:56:19Zurn:sha1:aea3d9cf573a17400d4c1d399f410cb87ec58c6d
GCC defaults to C++17 currently, but our library users could be on other
(newer/older) standard still e.g. by explicit request, so to avoid
accidentally breaking them the pkg-config-test is adapted to include
all of our public headers as a smoke test for if you can build an
application against our library in a certain C++ standard.
The test script is also adapted to be runnable outside of autopkgtest
like in our CI or manually.
Introduce apt why, apt why-not2025-05-19T15:20:09ZJulian Andres Klodejak@debian.org2025-05-19T12:17:23Zurn:sha1:7724d170751b3dc1717ba7a08881437cf7151996
These are implemented somewhat differently from aptitudes
why and why-not commands: They produce the actual solver
trace for why a particular decision has been taken.
For the why-not case, we need to explicitly discover our
specified package, as if nothing else depends on it in
our graph, it would otherwise always be undiscovered and
conflicts not detected (see e.g. level-3 in the test).
debian/NEWS: Document new requirements on trusted.gpg.d2025-04-28T22:03:04ZJulian Andres Klodejak@debian.org2025-04-28T22:03:04Zurn:sha1:477f32c18bcde4150dbfafc3cb6335ce177fc498
All files in apt directories must follow the run-parts requirements,
the only allowed characters are:
a-z, A-Z, 0-9, _, -, :
and '.' if an extension is required, due to the use of the general
GetFilesInDirectory() function.
Other characters were previously supported as the directory was not
enumerated by apt, but by apt-key, an 850ish line shell script using
find "$TRUSTEDPARTS" -mindepth 1 -maxdepth 1 \( -name '*.gpg' -o -name '*.asc' \)
which obviously does not share the same requirements.
Document the difference in debian/NEWS, as it seems ill-advised to
introduce a flag-carrying version of GetFilesInDirectory() for the
sole purpose of a deprecated signing mechanism.
Closes: #1104320
Release 3.0.12025-04-25T21:12:18ZJulian Andres Klodejulian.klode@canonical.com2025-04-25T21:09:39Zurn:sha1:3e6de9c26e0e32e417629d8d5b90343e94b85ab6sqv: Warn about signatures that will be rejected by policy within a year2025-04-25T21:07:07ZJulian Andres Klodejulian.klode@canonical.com2025-04-25T18:53:45Zurn:sha1:85c435f23718e168345ea60270b24a57061b54f4
This implements a simple check where we first run `sqv` with
`--policy-as-of` 1 year in the future. If the file is validly
signed one year in the future, it is validly signed now.
If the file is not validly signed 1 year in the future, we check
if it is validly signed now, and otherwise print an error message.
The --policy-as-of feature was added in sqv 1.3.0, hence we add a
version requirement to the dependency.
Update Sequoia crypto policy2025-04-25T21:07:07ZJulian Andres Klodejulian.klode@canonical.com2025-04-25T18:03:52Zurn:sha1:0989275c2f7afb7a5f7698a096664a1035118ebf
Move our cut-offs to February to align with Sequoia, and cut-off more:
- 2024-02: DSA keys retroactively (align with GnuPG config)
- 2026-02: SHA224 hashes
- 2028-02: Brainpool keys (align closer with GnuPG backend)
- 2030-02: RSA2048 keys
These algorithms will not be valid starting on those cut-off dates.
Gbp-Dch: full
Release 3.0.02025-04-04T20:35:29ZJulian Andres Klodejulian.klode@canonical.com2025-04-04T20:33:20Zurn:sha1:1c5baadce8aff4ccee02eb283530385b7c4ba5fe
And so it begins.
symbols: Update to 2.9.352025-04-04T13:19:25ZJulian Andres Klodejulian.klode@canonical.com2025-04-04T13:19:25Zurn:sha1:b279e8b3df2c8620bb3a0f2deb8325a85f4a9a3b