apt/doc, branch 3.1.0

Release 3.1.0

2025-05-19T17:14:52Z

Update translation templates and merge translations

2025-05-19T16:29:05Z

sources.list(5): Explicitly say what the precedence order is

2025-05-19T16:07:34Z

The order of apt sources can matter, but this man page did not previously define whether /etc/apt/sources.list was parsed before or after the fragment files in sources.list.d. Giving a concrete example also provides a hint that numeric prefixes are a useful way to force a particular sort order, and clarifies that the .list or .sources extension is less important than lexicographic order. Signed-off-by: Simon McVittie

apt_preferences(5): Specify the order in which files are parsed

2025-05-19T16:05:40Z

The order of preference stanzas matters, but this man page did not previously define whether /etc/apt/preferences was parsed before or after the fragment files in preferences.d. Giving a concrete example also provides a hint that numeric prefixes are a useful way to force a particular sort order, and clarifies that the presence or absence of the .pref extension is less important than lexicographic order. Signed-off-by: Simon McVittie

dselect: Add https support

2025-05-19T16:02:55Z

Recognize the method and update the documentation and prompts.

Introduce apt why, apt why-not

2025-05-19T15:20:09Z

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).

Add 'Include'/'Exclude' options to limit packages used from a repository

2025-05-19T15:19:23Z

'Include' allows limiting a repository to a allowlist of packages, 'Exclude' allows removing packages from a repository. Implementation wise this is not the nicest as it goes via the IndexTarget options, so we first parse our option value into a vector, then we turn the vector into a string, and then vectorize it again. That said, we support both "," and " " as separators due to the construction (we split by "," then we join using " "). Gbp-Dch: full

Pass --check to msgfmt and fix broken format strings

2025-05-06T16:11:33Z

The check option discovers broken format string translations as well as other issues like broken headers, enable it. The Japanese translation was discovered to both use the wrong ordering for %.*s translations with different positions, and missing the dot, e.g. %1$*2$s should have been %2$.*1$s (the number after % matches the string and the number after .* the size)

Release 3.0.1

2025-04-25T21:12:18Z

Remove boggus option in French manpage translation

2025-04-07T12:51:45Z