Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.6_alpha2 2017-08-24T14:56:52Z 2017-08-24T14:56:52Z Julian Andres Klode jak@debian.org 2017-08-24T14:55:15Z urn:sha1:0e4ac8334d02ea256f750ad61689f28ff1ebdf6c As a follow up to the last commit, let's replace APT_CONST with APT_PURE everywhere to clean stuff up. 2017-07-26T17:07:55Z David Kalnischkies david@kalnischkies.de 2017-07-23T23:15:55Z urn:sha1:8df85a4fb91bed6c79a3cb9c2000881cc5b42ea7 The comment says this is intended, but looking at the history reveals that the comment comes from a different era. Nowadays we don't really need it anymore (and even back then it was disputeable) as we haven't used that file for our update in the end and nothing really needs this file after the update. Triggered is this by 188f297a2af4c15cb1d502360d1e478644b5b810 which moves various error conditions forward including this code expecting the file to exist – but it doesn't need to as download could have failed. We could fix that by simple checking if the file exists and only stage it if it does, but instead we don't stage it and instead even rename it out of the way with our conventional FAILED name (if it exists). That restores support for partial mirrors (= in this case mirrors which don't ship pdiff files). Note that apt heals itself even if only such a mirror is used as the update is successful even if that error is shown. Closes: 869425 2017-07-26T17:07:55Z David Kalnischkies david@kalnischkies.de 2017-07-23T23:00:22Z urn:sha1:245b9b077f907f2a1a587e5f66964ab6e4becac8 RenameOnError does the rename already, so the check for existence will always fail making this some completely harmles but also completely pointless two lines of code we are better of removing. Gbp-Dch: Ignore 2017-07-17T10:15:29Z Julian Andres Klode jak@debian.org 2017-07-17T10:11:18Z urn:sha1:e0204f0236697bdc1b2392be5e141de9ec0c184e Minor grammar fix [jak@d.o: Fixed up po/] 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-07-07T14:25:44Z David Kalnischkies david@kalnischkies.de 2017-07-06T09:04:24Z urn:sha1:d10502c803c988c8a5459b191c35acb12809b343 Progress only shows if we have an idea of how much files we will acquire, but if a transaction fails before we have got an idea we ended up never showing progress even through we know that a failed transaction will not download additional files. 2017-06-28T17:18:47Z David Kalnischkies david@kalnischkies.de 2017-05-28T14:55:45Z urn:sha1:ca8da1bf83ecc90ba882520b79c1cda03ee7485d Having messages being printed on the error stack and confirm them by commandline flags is an okayish first step, but some frontends will probably want to have a more interactive feeling here with a proper question the user can just press yes/no for as for some frontends a commandline flag makes no sense… 2017-06-28T17:18:47Z David Kalnischkies david@kalnischkies.de 2017-05-28T11:24:33Z urn:sha1:96ebab48c25fcd1ee83729cdba4be8a6343a8766 This gives the repository owner a chance to explain why this change was needed – e.g. explaining the organisational changes or simply detailing the changes in the new release made. Note that this URI is also shown if the change is accepted, so it also draws attention to release notes of minor updates (if users watch apt output closely). 2017-06-28T17:18:47Z David Kalnischkies david@kalnischkies.de 2017-04-12T15:39:06Z urn:sha1:081fbea14d12f79c8d91ce4fe1f1004c7bc08656 The value of Origin, Label, Codename and co can be used in user configuration from apts own pinning to unattended upgrades. A repository changing this values can therefore have serious effects on the behaviour of apt and other tools using these values. In a first step we will generate error messages for these changes now explaining the need for explicit confirmation and provide config options and commandline flags to accept them.