Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.3.3 2021-04-29T08:42:59Z 2021-04-29T08:42:59Z Julian Andres Klode julian.klode@canonical.com 2021-04-29T08:42:59Z urn:sha1:b60cda7992d316123b036a4a0eb5f472d21e9cdd This reverts commit 64127478630b676838735b509fec5cdfa36874c8. 2021-04-29T08:28:08Z Julian Andres Klode jak@debian.org 2021-04-29T08:28:08Z urn:sha1:a6cb741a2cd1fa132705f8f5644872fc9708fb68 Count uninstallable packages in "not upgraded" See merge request apt-team/apt!169 2021-04-26T11:00:24Z David Kalnischkies david@kalnischkies.de 2021-03-18T16:37:49Z urn:sha1:d6f3458badf2cfea3ca7de7632ae31daff5742be An interactive tool like aptitude needs these flags current far more often than we do as a user can see them in apt only in one very well defined place – the autoremove display block – so we don't need to run it up to four times while a normal "apt install" is processed as that is just busywork. The effect on runtime is minimal, as a single run doesn't take too long anyhow, but it cuts down tremendously on debug output at the expense of requiring some manual handholding. This is opt-in so that aptitude doesn't need to change nor do we need to change our own tools like "apt list" where it is working correctly as intended. A special flag and co is needed as we want to prevent the ActionGroup inside pkgDepCache::Init to be inhibited already so we need to insert ourselves while the DepCache is still in the process of being built. This is also the reason why the debug output in some tests changed to all unmarked, but that is fine as the marking could have been already obsoleted by the actions taken, just inhibited by a proper action group. 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 2021-04-23T13:04:32Z Julian Andres Klode julian.klode@canonical.com 2021-04-23T13:01:07Z urn:sha1:94cf53979640ff8a29d445a2b056a6b17c7b3e49 The code missed a break, so it was looping infinitely because the while loop condition only checked for '\n' and '\r', but not end of file. 2021-04-23T10:26:46Z Julian Andres Klode julian.klode@canonical.com 2021-04-23T09:39:15Z urn:sha1:64127478630b676838735b509fec5cdfa36874c8 2021-04-23T10:26:46Z Julian Andres Klode julian.klode@canonical.com 2021-04-23T09:37:28Z urn:sha1:80dd1447595c536d31912c486ac5e96f983ccc7a Hook protocol 0.2 makes the new fields we added mandatory, and replaces `install` mode with `upgrade`, `downgrade`, `reinstall` where appropriate. Hook negotiation is hacky, but it's the best we can do for now. Users are advised to upgrade to 0.2 2021-04-23T10:26:46Z Julian Andres Klode julian.klode@canonical.com 2021-04-23T08:36:18Z urn:sha1:dc11a4422d99cb49817c827b9f827617b5880600 This enables hooks to output additional information. 2021-04-23T10:26:46Z Julian Andres Klode julian.klode@canonical.com 2021-04-22T10:53:54Z urn:sha1:de86a4b076a37db2f70ee5fbfbb295cc71c344df 2021-04-23T10:26:46Z Julian Andres Klode julian.klode@canonical.com 2021-04-22T08:45:45Z urn:sha1:4b5215e8e2e31637cb0998ecb80d3c3146760579 Provide access to the origins of a package, such that tools can display information about them; for example, you can write a hook counting security upgrades.