apt/apt-private, branch 3.1.9Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=3.1.92025-10-07T10:25:20ZLet APT::Get::Mark-Auto satisfy APT::Get::Build-Dep-Automatic2025-10-07T10:25:20ZJochen Sprickerhofjspricke@debian.org2025-09-16T06:29:39Zurn:sha1:f17371c879bd4eedb0fee56ded4bc8a9b766c8e3
This allows:
apt build-dep --mark-auto apt
Closes: #973260
Fix history command error when no ID was given2025-10-06T21:15:50ZSimon Johnssonsimon.johnsson@canonical.com2025-10-06T21:15:50Zurn:sha1:bcc245651becca2ce226589e76a7c7f0177e40a5Add history undo, redo, and rollback features2025-10-02T10:49:58ZSimon Johnssonsimon.johnsson@canonical.com2025-10-02T10:49:58Zurn:sha1:a65dca5d5e9b4bc71722bc91a5641126a1b0ec61history-list: reject any arguments provided2025-09-26T17:05:27ZJulian Andres Klodejak@debian.org2025-09-26T17:05:27Zurn:sha1:771d3e1d82cdf9286a002ef379a3edc7d62688f3history: Handle transactions without any changes2025-09-26T16:49:53ZJulian Andres Klodejak@debian.org2025-09-26T16:49:53Zurn:sha1:0c1fa8bae3a09f9efd1b30ebc3a5dacbbe58f193
For some reason I have them in my log file.
History Command and Parsing2025-09-26T16:18:42ZSimon Johnssonsimon.johnsson@canonical.com2025-09-26T16:18:42Zurn:sha1:66962bee233b617e4a9ce436f9b26875511b35e6Fail on stdio errors2025-05-19T17:06:31ZDemi M. Obenourdemiobenour@gmail.com2020-12-28T23:33:22Zurn:sha1:1eb729ef1c795f6b5944dd217994f8d8279672bc
If there is an error writing to cout, cerr, or clog, APT should return a
non-zero exit code. This allows automated tools to reliably check for
warnings.
💬 Recommend use of `apt update` over `apt-get update`2025-05-19T16:29:45ZMax Coplanmchcopl@gmail.com2019-11-20T16:03:39Zurn:sha1:d493545484fbb100e559e39618b30a3b3a3526d1Remove unused variable in apt-private2025-04-04T20:13:45ZJulian Andres Klodejulian.klode@canonical.com2025-04-04T20:12:30Zurn:sha1:3beb3ba289ac92931268f54dd56a674dbf3a3c29solver3: Consider more upgrades more costly when not upgrading2025-04-04T13:28:40ZJulian Andres Klodejulian.klode@canonical.com2025-04-04T13:25:01Zurn:sha1:295ab44a3063fb7790d8a558a161fc1bd801f998
We inadvertently considered more upgrades as a better solution in
all cases, but if we are *installing* rather than upgrading, we
should count upgrades as a negative.
Change the code to accomodate that. This requires a few more
tricks:
- We remove the keep count check. This does not appear to work
correctly and would have prevented the fix. We are already
counting all possible changes, so why bother.
- We need to subtract the upgrade count from the install count
(upgrades are a class of installs) since we now allow comparing
solutions with different upgrade counts for install counts.
- After comparing the "new install count", we now compare upgrade
count too, in the opposite direction of upgrading.
To test, we abuse that solver 3.0 does not upgrade all packages
in a source package when using the install command.
LP: #2105395