Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.7.7 2022-08-08T08:22:50Z 2022-08-08T08:22:50Z David Kalnischkies david@kalnischkies.de 2022-06-09T07:38:04Z urn:sha1:dc25210d889ebbcdfe96bd814a355961e80bccb3 Support for envvar NO_COLOR was added in 2.3.11, but with our own options we can also be a tiny bit more sensible in not overriding an explicit choice to disable colors. References: 400a6895566b67d70bcde43dc8a1cc1c7121f87d 2021-11-17T16:21:03Z Julian Andres Klode julian.klode@canonical.com 2021-11-17T16:20:29Z urn:sha1:21cc694f55de7caede8dcef3831236b6ca855cd7 Let's make this one step harder. 2021-10-19T13:38:22Z Julian Andres Klode julian.klode@canonical.com 2021-10-19T13:31:22Z urn:sha1:400a6895566b67d70bcde43dc8a1cc1c7121f87d When color has not been turned on explictly in the configuration file or options, only turn it on if NO_COLOR is not set. 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 2017-11-19T17:26:19Z David Kalnischkies david@kalnischkies.de 2017-11-18T02:48:59Z urn:sha1:3f8664036e63d2a2d58120ab6c1e8a0a09937c71 apt usually gets the width of the window from the terminal or failing that has a default value, but especially for testing it can be handy to control the size as you can't be sure that variable sized content will always be linebreaked as expected in the testcases. 2017-07-12T11:57:51Z Julian Andres Klode jak@debian.org 2017-07-12T11:40:41Z urn:sha1:87274d0f22e1dfd99b2e5200e2fe75c1b804eac3 This makes it easier to see which headers includes what. The changes were done by running git grep -l '#\s*include' \ | grep -E '.(cc|h)$' \ | xargs sed -i -E 's/(^\s*)#(\s*)include/\1#\2 include/' To modify all include lines by adding a space, and then running ./git-clang-format.sh. 2017-07-12T11:56:05Z Julian Andres Klode jak@debian.org 2017-07-12T11:42:18Z urn:sha1:c46f94aa48a9707668c46118b3eec77ff318b78c Including cacheiterators.h before pkgcache.h fails because pkgcache.h depends on cacheiterators.h. 2017-06-28T17:18:47Z David Kalnischkies david@kalnischkies.de 2017-05-28T15:44:11Z urn:sha1:24b5bc4e41ed527799a9fa01dec9c29294d0a3f2 If we have a user sitting around we can let 'apt' ask the user for a confirmation rather than print errors at the end and require the user to figure out which commandline flags are needed to confirm the changes non-interactively. 2017-01-19T14:59:38Z David Kalnischkies david@kalnischkies.de 2017-01-19T14:14:19Z urn:sha1:93cff633a830e222693fc0f3d78e6e534d1126ee Most of them in (old) code comments. The two instances of user visible string changes the po files of the manpages are fixed up as well. Gbp-Dch: Ignore Reported-By: spellintian 2016-05-16T14:17:54Z David Kalnischkies david@kalnischkies.de 2016-05-13T14:59:09Z urn:sha1:fd78974020e23679e9e810cf01dc5c8f3012bb8a Errors cause a kind of automatic no already, but warnings and notices are only displayed at the end of the apt execution even through they could effect the choice of saying yes/no to questions: E.g. if a configuration (file) was ignored you wanted to have an effect or if an external solver you used generated warnings suggesting that the solution might be valid, but bogus non-the-less and similar things. Note that this only moves those messages up to the question if the answer is interactive – not if e.g. -y is used or no question is asked at all so this has an effect only on interactive usage of apt(-get), not script who might be parsing apt output.