Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.9.2 2024-02-20T12:49:04Z 2024-02-20T12:49:04Z Julian Andres Klode julian.klode@canonical.com 2024-02-20T12:43:08Z urn: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. 2024-01-03T13:53:09Z David Kalnischkies david@kalnischkies.de 2024-01-03T13:53:09Z urn:sha1:c82f96210eb62c92d31ded7073f4cf5371cc9485 The implementation as-is as various smaller/esoteric bugs and inconsistencies like apt-get not supporting them, the option -s being supported in code but not accepted on the command line, the regex not escaping the dot before the file extension and exposing more implementation details to public headers than we actually need. Also comes with a small test case to ensure it actually works. References: bd7c126e3fb1b94e76e0e632c657cea854586844 2022-10-28T18:36:16Z quazgar quazgar@posteo.de 2022-10-28T18:36:16Z urn:sha1:bbde59e804ee6d5bb5547071c0c59fd6cfb02d99 2021-04-25T14:25:57Z David Kalnischkies david@kalnischkies.de 2021-03-06T13:12:01Z urn:sha1:f90b892e6acc0ca725811ef0dd9be3fed66c444f If a first step of the solver can figure out that a package is uninstallable it might reset the candidate so that later steps are prevented from exploring this dead end. While that helps the resolver it can confuse the display of the found solution as this will include an incorrect count of packages not upgraded in this solution. It was possible before, but happens a fair bit more with the April/May resolver changes last year so finally doing proper counting is a good idea. Sadly this is a bit harder than just getting the number first and than subtracting the packages we upgraded from it as the user can influence candidates via the command line and a package which could be upgraded, but is removed instead shouldn't count as not upgraded as we clearly did something with it. So we keep a list of packages instead of a number which also help in the upgrade cmds as those want to show the list. Closes: #981535 2020-01-14T12:10:36Z Julian Andres Klode julian.klode@canonical.com 2020-01-07T20:21:35Z urn:sha1:8c1a37e12790a23f3b132899485e011f9134b483 Remove it everywhere, except where it is still needed. 2019-07-08T13:51:17Z David Kalnischkies david@kalnischkies.de 2019-07-08T13:48:59Z urn:sha1:2b734a7ec429825c7007c1093883229e069d36c7 Reported-By: cppcheck 2019-06-11T14:49:03Z Julian Andres Klode julian.klode@canonical.com 2019-05-09T20:23:17Z urn:sha1:9244f712396c10b674740cc79fdab61c47173d04 Allow to satisfy dependency strings supplied on the command line, optionally prefixed with "Conflicts:" to satisfy them like Conflicts. Build profiles and architecture restriction lists, as used in build dependencies, are supported as well. Compared to build-dep, build-essential is not installed automatically, and installing of recommended packages follows the global default, which defaults to yes. Closes: #275379 See merge request apt-team/apt!63 2019-02-26T15:31:20Z Julian Andres Klode julian.klode@canonical.com 2019-02-26T12:21:07Z urn:sha1:29465ea9555a453ca733280955505de8bfcce935 Please use the standard C++ variants instead. 2019-01-27T07:27:33Z Josh Triplett josh@joshtriplett.org 2019-01-27T07:27:33Z urn:sha1:0eceebbdfdc2c5e1d677bff95a9ac1ef2f728337 aptitude has a similar "reinstall" command for precedent. 2018-12-03T16:21:39Z Julian Andres Klode julian.klode@canonical.com 2018-12-03T08:19:46Z urn:sha1:14535446557cb8b4125e7badc5e67a9f7790ab53 This adds a new "autopurge" command that will is a shortcut for "autoremove --purge" Thanks: Michael Vogt for the initial work