summaryrefslogtreecommitdiff
path: root/debian
Commit message (Collapse)AuthorAgeFilesLines
* Release 3.1.13.1.1Julian Andres Klode2025-06-101-0/+35
|
* Release 3.1.03.1.0Julian Andres Klode2025-05-191-0/+44
|
* Include everything in our pkg-config autopkgtestDavid Kalnischkies2025-05-191-7/+59
| | | | | | | | | | | 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-notJulian Andres Klode2025-05-191-0/+1
| | | | | | | | | | | 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.dJulian Andres Klode2025-04-291-0/+6
| | | | | | | | | | | | | | | | | | | | | | | 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.13.0.1Julian Andres Klode2025-04-251-0/+18
|
* sqv: Warn about signatures that will be rejected by policy within a yearJulian Andres Klode2025-04-252-2/+2
| | | | | | | | | | | | 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 policyJulian Andres Klode2025-04-251-2/+16
| | | | | | | | | | | | | 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.03.0.0Julian Andres Klode2025-04-041-0/+30
| | | | And so it begins.
* symbols: Update to 2.9.35Julian Andres Klode2025-04-041-2/+9
|
* Release 2.9.352.9.35Julian Andres Klode2025-03-271-0/+9
|
* Release 2.9.342.9.34Julian Andres Klode2025-03-201-0/+27
|
* Release 2.9.332.9.33Julian Andres Klode2025-03-121-0/+16
|
* Release 2.9.32Julian Andres Klode2025-03-091-0/+39
|
* Release 2.9.312.9.31Julian Andres Klode2025-02-281-0/+27
|
* Release 2.9.302.9.30Julian Andres Klode2025-02-161-23/+15
|
* Update symbols from experimentalJulian Andres Klode2025-02-161-0/+2
| | | | | Some manual editing, as riscv64 and mips64el are not yet built in exp2
* Release 2.9.29+exp2Julian Andres Klode2025-02-151-0/+13
|
* Add more excludes to the versionscriptJulian Andres Klode2025-02-151-2/+0
|
* cacheset: Drop APT_PUBLIC from templatesJulian Andres Klode2025-02-151-15/+0
| | | | | These templates are all inline and there is not much sense exposing their vtables and typeinfo publicly.
* Remove some more unused functionsJulian Andres Klode2025-02-151-8/+0
| | | | Final ABI cleanup before unstable?!
* Release 2.9.29+exp1Julian Andres Klode2025-02-141-0/+11
|
* Symbols?наб2025-02-141-20/+20
|
* apt-pkg: Avoid exporting any optional symbolsJulian Andres Klode2025-02-141-275/+0
|
* Bump symbolsJulian Andres Klode2025-02-141-1611/+1611
|
* Bump ABI to 7.0Julian Andres Klode2025-02-144-6/+4
|
* Release 2.9.292.9.29Julian Andres Klode2025-02-141-0/+36
|
* Release 2.9.282.9.28Julian Andres Klode2025-02-071-0/+35
|
* Release 2.9.272.9.27Julian Andres Klode2025-02-031-0/+31
|
* Symbols: Update for 2.9.23/2.9.25Julian Andres Klode2025-01-281-2/+3
|
* Release 2.9.262.9.26Julian Andres Klode2025-01-281-0/+22
| | | | | This reflows the documentation po files now using the latest gettext.
* apt-secure manual page is in manual section 8Andreas Rönnquist2025-01-281-1/+1
|
* Release 2.9.252.9.25Julian Andres Klode2025-01-221-0/+6
|
* Release 2.9.242.9.24Julian Andres Klode2025-01-212-0/+23
|
* Release 2.9.232.9.23Julian Andres Klode2025-01-171-0/+12
|
* Release 2.9.222.9.22Julian Andres Klode2025-01-141-0/+32
|
* Merge branch 'remove-gdb-minimal' into 'main'Julian Andres Klode2025-01-141-1/+1
|\ | | | | | | | | d/t/control: Don't depend on gdb-minimal. See merge request apt-team/apt!429
| * d/t/control: Don't depend on gdb-minimal.Sergio Durigan Junior2025-01-111-1/+1
| | | | | | | | | | | | | | | | gdb-minimal will soon be dropped from the archive; it doesn't offer any advantages over the gdb binary package. Just depend on gdb directly. Signed-off-by: Sergio Durigan Junior <sergiodj@debian.org>
* | Remove leftovers from ftp and rsh/ssh methods removalDavid Kalnischkies2025-01-051-2/+2
| | | | | | | | References: fd3684cdbc165ceaa635ed19fcbd231f509b0179
* | Move apt-extractexamples desc line from apt-utils to aptDavid Kalnischkies2025-01-051-2/+2
| | | | | | | | | | References: f4e0e9daf221e840e122b0ffa97007aa512020a6 Closes: #1091344
* | Remove leftovers of the apt-key removalDavid Kalnischkies2025-01-051-1/+0
|/ | | | References: a00fbbdb28cc31e78882301c2efe7218583ab4cb
* debian/changelog: v3 signature packet, not v3 subkeyJulian Andres Klode2025-01-021-1/+1
| | | | I typoed that.
* Release 2.9.212.9.21Julian Andres Klode2025-01-011-0/+20
| | | | | | We updated po/ with libunistring 1.3 as before, but had no doc changes since the manual update with libunstring 1.2, so no churn there. Hooray.
* Extend v3 subkey expiry to 2026, owing to OBS useJulian Andres Klode2025-01-011-0/+2
| | | | | SUSE's Open Build Service is signing multiple repositories using v3 signing keys.
* Release 2.9.202.9.20Julian Andres Klode2024-12-281-0/+7
|
* Re-include std:: symbols in the symbols file as optional againJulian Andres Klode2024-12-281-1/+279
| | | | | | | This will restore most of the symbols from before and ensure reverse dependencies not depending on new symbols can migrate. It also ensures we see any missing symbols.
* symbols: Merge 2.9.19 and fix version for InsertErrnoJulian Andres Klode2024-12-231-2/+2
| | | | | | | | | | Somehow InsertErrno was wrongly formatted as symbol 0.8.11.4 1 and that caused dedup to miss-handle it. The 2.9.19 merge fixes that but kept "1" as the version, change it to say 0.8.11.4 instead.
* Release 2.9.192.9.19Julian Andres Klode2024-12-232-0/+34
|
* Merge branch 'symbols'Julian Andres Klode2024-12-231-119/+74
|\
| * Symbols: Merge stable, noble, testing, unstableJulian Andres Klode2024-12-231-119/+74
| | | | | | | | | | | | | | Hand edit 2.7.14build2 to 2.7.14 The funny 999:0misbuilt version number gets auto-reduced to the current version when building which is sad, but it works.
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2026-10-14 13:02:04 +0000