Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.4_beta3 2016-06-08T11:09:42Z 2016-06-08T11:09:42Z David Kalnischkies david@kalnischkies.de 2016-06-08T09:34:53Z urn:sha1:3a487cc03dec3488d0fa3008d04747bb1b4b0baf Create and log the EDSP(like) request even if we use the internal resolver. 2016-06-08T11:07:21Z David Kalnischkies david@kalnischkies.de 2016-06-08T08:56:14Z urn:sha1:4dc619c0435d44a6a03cfda357654d3d76833b68 It wasn't noticeable before, but now with the (optional) logging it can be observed that we decide in the internal path two times if an internal or external solver should be used (and hence with logging, it is attempted twice), so if we are in the internal path call the internal resolver directly, which means those internal methods need to be public – but we can hide them based on the symbol at least. 2016-05-20T12:18:36Z David Kalnischkies david@kalnischkies.de 2016-05-06T12:21:02Z urn:sha1:43c71fad3a51d841132ba15a7a5930e1ee4126ed This allows to differentiate properly between 'apt-get upgrade', 'apt upgrade' and 'apt full-upgrade'. 2016-04-13T19:33:32Z David Kalnischkies david@kalnischkies.de 2016-04-08T10:50:08Z urn:sha1:40703260cdb40409e930a53a04a4061cf2173f42 There is a good chance that the attempt will fail, but if a user mentions certain packages explicitly on the commandline there is a chance that this will consist of a broken system which is resolved by upgrading more packages then just the mentioned. This limitation was not effecting external resolvers. 2015-08-10T15:27:58Z David Kalnischkies david@kalnischkies.de 2015-07-15T11:21:21Z urn:sha1:4dc77823d360158d6870a5710cc8c17064f1308f We aren't and we will not be really compatible again with the previous stable abi, so lets drop these markers (which never made it into a released version) for good as they have outlived their intend already. Git-Dch: Ignore 2014-11-08T13:29:25Z David Kalnischkies david@kalnischkies.de 2014-11-07T17:18:14Z urn:sha1:fa5404ab01bdf06eaf147d9f133139e6c89b906a Adding a new parameter (with a default) is an ABI break, but you can overload a method, which is "just" an API break for everyone doing references to this method (aka: nobody). Git-Dch: Ignore 2014-11-08T13:26:00Z David Kalnischkies david@kalnischkies.de 2014-10-26T22:17:03Z urn:sha1:586d8704716a10e0f8b9c400cab500f5353eebe6 For compatibility we use/provide and fill quiet some deprecated methods and fields, which subsequently earns us a warning for using them. These warnings therefore have to be disabled for these codeparts and that is what this change does now in a slightly more elegant way. Git-Dch: Ignore 2014-09-26T22:10:14Z David Kalnischkies david@kalnischkies.de 2014-08-17T11:27:59Z urn:sha1:67caa2e6538f13ff7a0d77e98ad6c58af998376d The comment above their definition marks them already as such, so this is only a formalisation of the deprecation and fixes the occurances we have in our own code together with removing a magic number. Git-Dch: Ignore 2014-09-26T22:10:05Z David Kalnischkies david@kalnischkies.de 2014-08-17T10:30:21Z urn:sha1:2a884c612b10b27f4be2cc6dd689bfe448d9361a Previously, we had a start and a done of the calculation printed by higher-level code, but this got intermixed by progress reporting from an external solver or the output of autoremove code… The higherlevel code is now only responsible for instantiating a progress object of its choosing (if it wants progress after all) and the rest will be handled by the upgrade code. Either it is used to show the progress of the external solver or the internal solver will give some hints about its overall progress. The later isn't really a proper progress as it will jump forward after each substep, but that is at least a bit better than before without any progress indication. Fixes also the 'strange' non-display of this progress line in -q=1, while all others are shown, which is reflected by all testcase changes. 2014-06-18T09:17:18Z David Kalnischkies david@kalnischkies.de 2014-06-17T17:05:53Z urn:sha1:172947cd7dc5c88c94c6ad269dc6c6be002ee958