apt/apt-pkg, branch 2.7.12

Delete SHADOWED metaIndex if we don't actually use snapshots

2024-02-20T17:50:14Z

This adds a bit more code but avoids any surprises later on by having both the shadowed and non-shadowed meta index in the list. Gbp-Dch: ignore

Automatically enable snapshots where supported

2024-02-20T17:50:14Z

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 includes

2024-02-20T12:49:04Z

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 'prevent_read_conf_inf_loop' into 'main'

2024-02-20T08:31:44Z

Prevent infinite loop in `ReadConfigFile` See merge request apt-team/apt!314

Merge branch 'keep-kernel-size' into 'main'

2024-02-20T08:30:05Z

Configure the amount of kernels to keep See merge request apt-team/apt!324

Add the ?security pattern

2024-02-13T13:28:06Z

Add a new ?phasing pattern

2024-02-13T13:28:06Z

This selects all packages that are being kept back due to phasing on your system.

Add public phased update API

2024-02-13T13:27:27Z

This moves the functions of the PhasedUpgrader class into various other classes so they can be publicly exposed. This introduces three new functions: pkgDepCache::PhasingApplied() tells you whether phasing should be applied to the package. pkgProblemResolver::KeepPhasedUpdates() keeps back updates that have phasing applied. pkgCache::VerIterator::IsSecurityUpdate() determines whether this version contains security fixes.

For phasing, check if current version is a security update, not just previous ones

2024-02-13T13:13:56Z

We only considered an update a security update if a previous update is a security update but not the update in question itself. LP: #2051181

Configure the amount of kernels to keep

2024-01-24T17:23:33Z

This commit introduces the following configuration for keeping a configurable amount of kernels: APT::NeverAutoRemove::KernelCount The logic dictates that the running kernel and the latest kernel are not autoremoved. In case the running kernel is the latest kernel, the previous kernel is kept. Any count lower than two is therefore disregarded. This is in line with the previous behavior. The default is therefore similar to: APT::NeverAutoRemove::KernelCount 2; This will be ignored and we will still keep two: APT::NeverAutoRemove::KernelCount 1; This will keep 3 kernels (including the runnig, and most recent) APT::NeverAutoRemove::KernelCount 3; Signed-off-by: Wesley Schwengle