| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |\
| |
| |
| |
| | |
Various cherry-picks
See merge request apt-team/apt!480
|
| | |
| |
| |
| |
| |
| | |
If there is an error writing to cout, cerr, or clog, APT should return a
non-zero exit code. This allows automated tools to reliably check for
warnings.
|
| | |
| |
| |
| |
| |
| | |
Update our vendor config to enable the 3.0 solver by default,
using the legacy compat mode for apt-get, where it is allowed
to remove manually installed packages.
|
| |/
|
|
|
|
|
|
|
|
|
| |
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.
|
| |\
| |
| |
| |
| | |
💬 Recommend people use `apt update` over `apt-get update`
See merge request apt-team/apt!80
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| | |
sources.list(5): Explicitly say what the precedence order is
See merge request apt-team/apt!417
|
| |/
|
|
|
|
|
|
|
|
|
| |
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 <smcv@debian.org>
|
| |\
| |
| |
| |
| | |
apt_preferences(5): Specify the order in which files are parsed
See merge request apt-team/apt!416
|
| |/
|
|
|
|
|
|
|
|
|
| |
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 <smcv@debian.org>
|
| |\
| |
| |
| |
| | |
Cleanup dselect method
See merge request apt-team/apt!423
|
| | |
| |
| |
| |
| |
| | |
The information in the header was probably mostly useful to the author,
but even then, it seems it has long past its usefulness once it got
integrated into apt proper.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Move the warnings from the shebang into a proper pragma, so that we are
sure it will be enabled regardless of the script being called explicitly
without the flag.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
The dpkg --update-avail command has supported reading from stdin since
dpkg 1.17.7. This removes a temporary file which can be very big
nowadays.
|
| |/
|
|
| |
Recognize the method and update the documentation and prompts.
|
| |\
| |
| |
| |
| | |
Fix error handling with getline
See merge request apt-team/apt!265
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
| |
The function getline is used to read data from different streams, however,
the error handling is not accurate.
From the man page, getline returns -1 on failure and sets errno accordingly,
but the current implementation only checks errno to see if there was a
failure. With this approach, in case getline returns success but also sets
errno it is consider and error.
Fix the issue but also checking the return value of getline.
Signed-off-by: Walter Lozano <walter.lozano@collabora.com>
|
| |\
| |
| |
| |
| | |
Introduce apt why, apt why-not
See merge request apt-team/apt!479
|
| |/
|
|
|
|
|
|
|
|
|
| |
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).
|
| |\
| |
| |
| |
| | |
apt-pkg: fixed type comparison in 64bit systems using memsize cast
See merge request apt-team/apt!477
|
| |/ |
|
| |\
| |
| |
| |
| | |
Add 'Include'/'Exclude' options to limit packages used from a repository
See merge request apt-team/apt!439
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
'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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
| |\
| |
| |
| |
| | |
test: Fix test-skipped regression in 3.0.1
See merge request apt-team/apt!476
|
| | |
| |
| |
| | |
Make the test suite independent of the host sequoia config.
|
| |/
|
|
|
| |
There was an accidental exit in the if causing the test to exit
early, but the test suite still to pass.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |\
| |
| |
| |
| | |
Update Sequoia crypto policy, implement year-ahead warning
See merge request apt-team/apt!475
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |\
| |
| |
| |
| | |
Remove boggus option in French manpage translation
See merge request apt-team/apt!474
|
| |/ |
|
| |
|
|
| |
And so it begins.
|
| |
|
|
|
| |
Closes: #1100708
Reviewed-By: Debian L10n French <debian-l10n-french@lists.debian.org>
|
| | |
|
| |
|
|
| |
Closes: #1100550
|
| |\
| |
| |
| |
| | |
Translation updates
See merge request apt-team/apt!473
|
| | | |
|
| | |
| |
| |
| | |
Closes: #1101535
|
| | |
| |
| |
| | |
Closes: #1100964
|
| | |
| |
| |
| | |
Closes: #1100807
|
| |/
|
|
| |
Closes: #1100801
|