Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.2 2016-01-15T01:45:35Z 2016-01-15T01:45:35Z David Kalnischkies david@kalnischkies.de 2016-01-15T01:45:35Z urn:sha1:feb674aba51dcb26f5281b5b38fbc5893f757170 Introduced in 9d2a8a7388cf3b0bbbe92f6b0b30a533e1167f40 apt tries to merge actions like downloading the same (as judged by hashes) file into doing it once. The implementation was very simple in that it isn't planing at all. Turns out that it works 90% of the time just fine, but has issues in more complicated situations in which items can be in different stages downloading different files emitting potentially the "wrong" hash – like while pdiffs are worked on we might end up copying the patch instead of the result file giving us very strange errors in return. Reverting the change until we can implement a better planing solution seems to be the best course of action even if its sad. Closes: 810046 2016-01-14T22:08:02Z David Kalnischkies david@kalnischkies.de 2016-01-14T19:13:16Z urn:sha1:62428dbc17ffa7b5b8188e88609a9438428d6024 Architectures for packages which do not belong to the native nor a foreign architecture (dubbed barbarian for now) which are marked M-A:foreign still provide in their own architecture even if not for others. Also, other M-A:foreign (and allowed) packages provide in these barbarian architectures. 2016-01-14T08:28:47Z Michael Vogt mvo@ubuntu.com 2016-01-14T08:28:47Z urn:sha1:b0ce7c65309585d4b9752bb571a0e616036eb162 Closes: #734922 2016-01-12T22:59:35Z Julian Andres Klode jak@debian.org 2016-01-12T22:45:59Z urn:sha1:7d2794a20bdab9b848bf5b4e88d73527405bad54 This prevents a test suite failure on systems with weird umasks. Also set umask 000 at the beginning so we can actually check for that anywhere. Gbp-Dch: ignore 2016-01-12T22:40:59Z Julian Andres Klode jak@debian.org 2016-01-12T14:18:12Z urn:sha1:b6d88f39aceda2e093e1bf8751f07236b7d9e483 Just enabling it for anyone breaks with HTTP/1.0 servers and proxies sometimes. Closes: #810796 2016-01-08T16:51:23Z David Kalnischkies david@kalnischkies.de 2016-01-08T16:51:23Z urn:sha1:ef3c549e00b2a0487ddee0aeb70e3a29f76c2fbb The code already deals with compressed leftovers, but forgot the uncompressed files. The opertunity is picked to reorder this code and add debug messages about the actions taken as well as produce such a leftover file in the associated testcase. 2016-01-08T14:40:01Z David Kalnischkies david@kalnischkies.de 2016-01-08T14:30:05Z urn:sha1:4e6219da0dd1e68fad7db972f7ddd76598645228 With the addition of the $HASH-Download field in the .diff/Index we got the size of the compressed patches for 'free', so if that information is available we can use it for a more fitting calculation of the size requirements of the patches vs. the complete file. Note that this predicts a too small size in the transition case in which the information isn't available for all patches, but figuring this out would be a lot of code for practically nothing as only one update can ever be in such a transition phase. 2016-01-08T14:40:01Z David Kalnischkies david@kalnischkies.de 2016-01-08T12:08:19Z urn:sha1:896f0ae857b693782658145e16e21a3054dd5280 Some (older) versions of bash seem to be allergic to a method named "aptautotest_grep_^apt" (note the caret). Unlikely that we are going to write autotests for such commands so we could just skip those, but lets instead just use "normal" characters in the names and strip the rest as we already did with the (arguable more common) '-'. 2016-01-08T14:40:01Z David Kalnischkies david@kalnischkies.de 2016-01-07T23:35:39Z urn:sha1:abec2980ef1ff051be14c26097a76b6429b3b7bc This way it works more similar to the compressor binaries, which we can relief in this way from their job in the test framework avoiding the need of adding e.g. liblz4-tool to the test dependencies. 2016-01-08T14:40:01Z David Kalnischkies david@kalnischkies.de 2016-01-07T19:32:09Z urn:sha1:0179cfa83cf0042235eda41db7f35c420781c63e Downloading and storing are two different operations were different compression types can be preferred. For downloading we provide the choice via Acquire::CompressionTypes::Order as there is a choice to be made between download size and speed – and limited by whats available in the repository. Storage on the other hand has all compressions currently supported by apt available and to reduce runtime of tools accessing these files the compression type should be a low-cost format in terms of decompression. apt traditionally stores its indexes uncompressed on disk, but has options to keep them compressed. Now that apt downloads additional files we also deal with files which simply can't be stored uncompressed as they are just too big (like Contents for apt-file). Traditionally they are downloaded in a low-cost format (gz) as repositories do not provide other formats, but there might be even lower-cost formats and for download we could introduce higher-cost in the repositories. Downloading an entire index potentially requires recompression to another format, so an update takes potentially longer – but big files are usually updated via pdiffs which has to de- and re-compress anyhow and does it on the fly anyhow, so there is no extra time needed and in general it seems to be benefitial to invest the time in update to save time later on file access.