Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.5 2017-09-13T17:16:06Z 2017-09-13T17:16:06Z Julian Andres Klode jak@debian.org 2017-09-13T17:16:06Z urn:sha1:e9db5ba7c7631d51359967afb1d563da7637be11 In commit Do not warn about duplicate "legacy" targets, we we added an if, that changed the .po files... 2017-09-09T17:47:59Z Julian Andres Klode jak@debian.org 2017-09-09T17:43:08Z urn:sha1:5a747462baef6cecf6ed389c7b7492443930f7ed If a source has a legacy Contents file, and two lines mention the same archive but different components, a warning would be issued that is confusing. So, as the field is named Contents-deb-legacy, let's just not print warnings for fields containing "legacy". LP: #1697120 Closes: #839259 2017-09-09T15:22:11Z David Kalnischkies david@kalnischkies.de 2017-08-14T15:31:05Z urn:sha1:923522367a28be7235bf6459abfeae89fafffcf1 The relevant calling code as well as the implementation for the deb system was removed 2 years ago with the refactoring of release information storage (b07aeb1a6e24825e534167a737043441e871de9f). This commit removes the the unused remains of this change with no practical effect on anybody (expect codesize) as the methods were declared as hidden and hence only libapt could have called it. Gbp-Dch: Ignore 2017-09-09T15:19:48Z David Kalnischkies david@kalnischkies.de 2017-08-05T10:55:11Z urn:sha1:149ee4017c7d21b420b7109ea7606012c9051d15 APT by default logs terminal (term.log) and actions (history.log), but if either or Dir::Log directly is set to /dev/null it continues to do so, which isn't too bad – just wasted effort – but term.log is chmodded to protect it from the general public (as it may contain otherwise private data the admin entired in the terminal) which shouldn't happen for /dev/null. 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-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-12T09:09:00Z Apollon Oikonomopoulos apoikos@debian.org 2017-07-12T07:41:58Z urn:sha1:5caf6ee2db1ebf294fb0412fddf7d187840cce70 Commit d7c92411dc1f4c6be098d1425f9c1c075e0c2154 parses the Components section of (In)Release and attempts to detect the distribution's supported components. While doing so, it handles component names with slashes in a special manner, assuming that the actual component is only the part after the final slash. This is done to handle security.debian.org, which usually appears in sources.list as follows: deb http://s.d.o/debian-security stretch/updates main contrib non-free while the actual release file has: Codename: stretch Components: updates/main updates/contrib updates/non-free While this special handing on APTs part indeed works for debian-security, it emits spurious warnings on repositories that actually use slashes in the component names *and* appear so in sources.list. We fix this by adding both component versions (whole and final part) to the SupportedComponents array. Closes: #868127 2017-06-28T17:50:26Z Julian Andres Klode jak@debian.org 2017-06-26T16:44:56Z urn:sha1:6edfda8b45dee7e1202f723b98fa962c38554c51 This should fix some issues with dpkg normalizing such values. Suprisingly enough apt treats the Version: field the same, even with epoch vs without, but not when searching, and does not strip the 0: from the output. 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).