Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.2.0 2018-05-11T15:58:46Z 2018-05-11T15:58:46Z David Kalnischkies david@kalnischkies.de 2018-01-26T22:33:25Z urn:sha1:ce9223cc4e4ffcc43d17ae97ff8c57fb759a2c49 The syntax is a bit awkward, but it is the same as for a package name and introducing another syntax wouldn't really help usability, so with apt install ./foo.deb/experimental you will get the dependencies of foo satisfied by your default release, but if this wouldn't satisfy the version requirements the candidate for this dependency is switched to the version from the experimental release. The same applies for apt build-dep ./foo.dsc/stable-backports which was the initial request. 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. 2016-07-22T14:05:09Z David Kalnischkies david@kalnischkies.de 2016-07-08T13:59:23Z urn:sha1:92296fe4b0862a04ea3d965b4cd2d4a420e3be9f We support installing ./foo.deb (and ./foo.dsc for source) for a while now, but it can be a bit clunky to work with those directly if you e.g. build packages locally in a 'central' build-area. The changes files also include hashsums and can be signed, so this can also be considered an enhancement in terms of security as a user "just" has to verify the signature on the changes file then rather than checking all deb files individually in these manual installation procedures. 2015-11-04T17:04:01Z David Kalnischkies david@kalnischkies.de 2015-10-12T13:57:53Z urn:sha1:14341a7ee1ca3dbcdcdbe10ad19b947ce23d972d The main part is refactoring through to allow hiding the magic needed to support .deb files in deeper layers of libapt so that frontends have less exposure to Debian specific classes like debDebPkgFileIndex. 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 2014-03-13T12:58:45Z David Kalnischkies david@kalnischkies.de 2014-03-05T21:11:25Z urn:sha1:453b82a388013e522b3a1b9fcd6ed0810dab1f4f Beside being a bit cleaner it hopefully also resolves oddball problems I have with high levels of parallel jobs. Git-Dch: Ignore Reported-By: iwyu (include-what-you-use) 2014-01-24T19:33:02Z Michael Vogt mvo@debian.org 2014-01-24T19:33:02Z urn:sha1:59e81cec3e2277e367f14f113168421909c42035 There is a new "apt full-upgrade" that performs a apt-get dist-upgrade. "apt dist-upgrade" is still supported as a alias. The "apt upgrade" code is changed so that it mirrors the behavior of "apt-get upgrade --with-new-pkgs" and also honors "apt uprade --no-new-pkgs". 2013-10-05T10:30:26Z Michael Vogt mvo@debian.org 2013-10-05T10:30:26Z urn:sha1:3f506f684c6199a9a2bc68365732a9c00dc551c1