Because the service has ConditionACPower=true, it would be nice to try and
start it when plugging-in the AC power in case that an earlier timer trigger
was missed due to not being plugged-in.
It is not a problem that we may be invoking the service multiple times a day,
because it keeps track of its own timestamp file to run up to once every
"APT::Periodic::Update-Package-Lists" days
Related: https://launchpad.net/bugs/2089151
The --cli-version argument can be used to request a specific
CLI version. The default CLI version is the APT version for apt(8)
and 0 for the other apt-get tools.
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.
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).
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
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
Julian Andres Klode