apt/test, branch 2.7.14Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.7.142024-02-28T17:22:01ZTemporarily downgrade key assertions to "soon worthless"2024-02-28T17:22:01ZJulian Andres Klodejulian.klode@canonical.com2024-02-28T16:04:05Zurn:sha1:66998ed3d299bede651ad40368bdb270f5f5b0f9
This will only issue warnings instead of errors while we continue
cleaning up our repositories.
Rename 'weak digest algorithm' to 'weak algorithm'2024-02-28T17:22:01ZJulian Andres Klodejulian.klode@canonical.com2024-02-28T15:52:33Zurn:sha1:8a14c18c5b487139948dcb22abd37bffdd9cf5f4
This allows us to render public key algorithms as weak as well.
Implement gpgv --assert-pubkey-algo=>=rsa2048,ed25519,ed4482024-02-28T17:22:01ZJulian Andres Klodejulian.klode@canonical.com2024-02-28T14:14:43Zurn:sha1:50e3fee26ae843a812b1c9ec8531946931773fd3
The assertion can be overriden using apt::key::assert-pubkey-algo,
the default is the most opinionated one.
This will inform the user during apt-cdrom add as we do not
pass --quiet to user, so adjust test case.
Add a simple test case for it to test-method-gpgv.
LP: #2055193
gpgv: Add a reason to worthless signers2024-02-28T17:21:01ZJulian Andres Klodejulian.klode@canonical.com2024-02-28T13:49:48Zurn:sha1:60d653634f889abe09c0f4d88f2559eab9202635test-snapshot: Add test case for automatic snapshot2024-02-20T18:12:16ZJulian Andres Klodejulian.klode@canonical.com2024-02-20T18:04:36Zurn:sha1:78c3ad795de7f14de3ee22e9f04fe24b5f21f0ea
1. repository not supporting snapshots, implicit Enabled
2. repository not supporting snapshots, Enabled: yes
3. URL-based lookup, implicit Enabled
test-snapshot: Fix a test case2024-02-20T18:04:03ZJulian Andres Klodejulian.klode@canonical.com2024-02-20T18:04:03Zurn:sha1:1f67cf94ec2df0d30349f033c777495b80b41484
This was accidentally using testfailure instead of
testfailureequal, hence trying to run the output string
as a command :(
Automatically enable snapshots where supported2024-02-20T17:50:14ZJulian Andres Klodejulian.klode@canonical.com2024-02-19T11:07:55Zurn:sha1:b6274188312e6338e94edc45dbf9cc410d650477
Convert sources.list Snapshot option from opt-in to automatic. If
we can find a snapshot server, Snapshot: yes is assumed if a snapshot
is specified.
On the implementation side, we record automatic snapshot enablement
by adding a '?' suffix to the snapshot timestamp, if any is specified,
this avoids introducing bugs into the code where we could end up with
an empty snapshot.
This has an annoying internal implementation caveat: Since we call
GetDebReleaseIndexBy() with the SHADOWED option emplaced, if we do
not find a server, we need to remove the SHADOWED option again, but
we already have inserted a shadowed release index into the list.
This will simply insert the release index a second time without the
SHADOWED option which in preliminary testing works fine, but it would
arguably be more correct to also remove the release index again if
we have created it.
FIXME: This only has one test case: A source with supported snapshot
server is auto-discovered. We should also add a test case where we
cannot detect a server and then don't fail in automatic mode.
Modernize standard library includes2024-02-20T12:49:04ZJulian Andres Klodejulian.klode@canonical.com2024-02-20T12:43:08Zurn:sha1:40a75722c43ae24cb9a99d6730a3b25b65819c49
This was automated with sed and git-clang-format, and then I had to
fix up the top of policy.cc by hand as git-clang-format accidentally
indented it by two spaces.
Merge branch 'homar-typo' into 'main'2024-02-20T08:29:06ZJulian Andres Klodejak@debian.org2024-02-20T08:29:06Zurn:sha1:33c2f0fe5b9ec1c368a7f377de5632f183b12e12
Typos in integration tests
See merge request apt-team/apt!313Show a separate list of upgrades deferred due to phasing2024-02-13T14:08:57ZJulian Andres Klodejulian.klode@canonical.com2024-02-13T11:54:07Zurn:sha1:1a0882558da05eaf471c2b4049ae27305e7c70ec
This introduces a new line:
The following upgrades have been deferred due to phasing
This is any kept back package that is also phasing. This may
not be 100% accurate as we have kept it back due to other reasons
in an install command, for example, but we don't track for which
packages we applied phasing in reality.
If additional packages are kept back that are not phasing, show
a a notice
"N: Some packages may have been kept back due to phasing."
LP: #1988819