apt/test/integration, branch 2.9.8

Merge branch 'main' into 'main'

2024-08-12T14:07:11Z

Do not return error if `Signed-By` value in source list is empty See merge request apt-team/apt!364

Fix obsoleted-by handling for experimental

2024-08-12T14:05:54Z

Basically this boils down to checking that the priority of the source candidate candidate is higher or equal than the priority of the package's candidate that is being under consideration. It stands to reason if we maybe we should actually calculate a source candidate version; this will look similar but may perhaps perform slightly different.

Merge branch 'deprecate-pubkey-algos' into 'main'

2024-07-30T04:18:02Z

Only revoke weak RSA keys now, add 'next' and 'future' levels See merge request apt-team/apt!365

Only revoke weak RSA keys for now, add 'next' and 'future' levels

2024-07-15T17:17:55Z

Algorithms not in the next level give a warning, algorithms in not in the future level introduce an audit message for the --audit flag. next: >=rsa2048,ed25519,ed448,nistp256,nistp384,nistp512 future: >=rsa3072,ed25519,ed448 LP: #2073126

Do not return error if `Signed-By` value in source list is empty

2024-07-12T03:28:47Z

Signed-off-by: Aristo Chen

Parse snapshot option for apt show/list

2024-07-08T14:12:37Z

The option is supported by the command (as this is done by a bit more low level code), but the command line parsing did not expect them to be used for the apt show & list command, so that it would report error. As such, a workaround for this issue is to use: -o APT::Snapshot=BANANA instead of e.g. -S BANANA Closes: #1075819

Show installed version (not candidate version) while removing a package

2024-07-05T04:27:32Z

Showing a package version which was never installed in removals is confusing.

solver3: Refactor (rewrite) FromDepCache()

2024-07-01T19:49:26Z

Refactor the various Install requests into a single one and move some stuff around, this should be a bit easier to maintain and we don't repeat ourselves all the time. This accidentally uncovered some bugs in the code, that get fixed by this: - The UpgradeManual and InstallManual groups did not work correctly, Essential packages were Install and others were Upgrade. - Automatically installed packages falsely got promoted to the manual groups as they got promoted into the manual code path, whenever we ran without allowing their removal. - The combination of --mark-auto --auto-remove now works correctly We previously skipped the installation of automatically installed packages when we did autoremoval, but we did not consider if the action was protected, that is specified on the command-line. Now we do not autoremove protected actions, and have added a test case for it. - The AllowRemoveManual option no longer is applied if removals are generally denied. Closes: #1071519

solver3: Do not accidentally promote Replaces and Enhances to dependencies

2024-07-01T14:28:53Z

As part of the refactoring, we allowed the code to work on unimportant dependencies as we needed to promote Suggests to Depends if they are currently satisfied. However, Replaces and Enhances were not considered properly and both are not negative dependencies so they were accidentally promoted to Depends too if they were currently satisfied.

solver3: Order obsolete choices last

2024-06-13T13:10:06Z

This has two aspects: 1. For a dependency A | B | C we order the obsolete packages last, that is, if A is obsolete, this gets reordered to B | C | A, such that we try to pick non-obsolete packages first to ease upgrade calculation. 2. When comparing two dependencies, we order dependencies into three groups: First we satisfy dependencies mentioning only non-installed (NEW) packages, then we satisfy "normal" dependencies, and finally we satisfy any dependencies mentioning obsolete packages. This means for example if you have obsolete libfoo1 and a new libfoo1t64, that we will see Depends: libfoo1t64 before any Depends: libfoo1 (which may expand to libfoo1 | libfoo1t64), so we effectively will have selected "replacement" packages this way already before getting to older packages where we would have to choose between the obsolete package and its replacement.