apt/apt-pkg, branch 2.9.7Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.9.72024-07-30T04:18:02ZMerge branch 'deprecate-pubkey-algos' into 'main'2024-07-30T04:18:02ZJulian Andres Klodejak@debian.org2024-07-30T04:18:02Zurn:sha1:d0e8f39437afdd557a8712047e1fc494fde9209e
Only revoke weak RSA keys now, add 'next' and 'future' levels
See merge request apt-team/apt!365solver3: Refactor Reason.Pkg()/Reason.Ver() use with iterator2024-07-16T11:55:07ZJulian Andres Klodejulian.klode@canonical.com2024-07-16T11:54:11Zurn:sha1:62573e3ca6b45b0d12b9be8b02da116ce0d91b75
More code but nicer to read
Only revoke weak RSA keys for now, add 'next' and 'future' levels2024-07-15T17:17:55ZJulian Andres Klodejulian.klode@canonical.com2024-07-15T17:13:58Zurn:sha1:47deb766c0a11c54d122197531279677545459af
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
gpgv: Add IsAssertedPubKeyAlgo() function2024-07-15T17:17:20ZJulian Andres Klodejulian.klode@canonical.com2024-07-15T16:42:54Zurn:sha1:29dd6c45bc2579d012ac78ba3100a2485c78ff1d
This checks whether a public key algorithm is asserted.
worker: Add an audit level to log audit messages2024-07-15T17:16:27ZJulian Andres Klodejulian.klode@canonical.com2024-07-15T15:57:42Zurn:sha1:c51ea9f44e9742c88a252b86cb0260798b4b9f7bsolver3: Formatting cleanup2024-07-02T18:10:33ZJulian Andres Klodejulian.klode@canonical.com2024-07-02T16:56:40Zurn:sha1:a16350427b8ce3865d2f11e637952210d34ee410
Run clang-format
solver3: Only demote obsolete packages in choices for upgrades2024-07-02T18:10:33ZJulian Andres Klodejulian.klode@canonical.com2024-07-02T16:53:33Zurn:sha1:ae141932d8b434098e3f77c75c428ca8caff9a6e
If we are not upgraded, we should continue to keep the installed
package installed if possible.
solver3: Consider packages as obsolete and not versions2024-07-02T18:08:38ZJulian Andres Klodejulian.klode@canonical.com2024-07-02T16:51:11Zurn:sha1:8c13d9cb1c38ebb52cf6e1c8c7561c5c5d87c970
This makes more sense, as all package versions are obsolete that
are not the candidate, usually.
Pay special attention to no-strict-pinning: If we don't have
strict pinning, a package without a candidate version may still
be non-obsolete if the latest version is not obsolete.
Likewise, in no-strict-pinning any later source version that exists
will cause the package to be considered obsolete, rather than just
candidates.
solver3: Refactor (rewrite) FromDepCache()2024-07-01T19:49:26ZJulian Andres Klodejulian.klode@canonical.com2024-06-13T15:55:10Zurn:sha1:b69f11fac9f4df52726ea7ac4f2c5920b7f71ccb
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: Unmark packages before setting any in ToDepCache2024-07-01T15:15:54ZJulian Andres Klodejulian.klode@canonical.com2024-06-13T15:54:13Zurn:sha1:7217910e75ce32938d28f9d653dec6b1d18e05b7
We should set the Mark/Garbage flags for all packages so we don't
end up in an inconsistent state, so reset the flags for each package
before evaluating further.