Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.3_rc4 2016-09-02T15:16:36Z 2016-09-02T15:16:36Z Julian Andres Klode jak@debian.org 2016-06-15T21:13:43Z urn:sha1:2a440328ea19e9646a93f847dd9eff21e03ad16d Employ a priority queue instead of a normal queue to hold the items; and only add items to the running pipeline if their priority is the same or higher than the priority of items in the queue. The priorities are designed for a 3 stage pipeline system: In stage 1, all Release files and .diff/Index files are fetched. This allows us to determine what files remain to be fetched, and thus ensures a usable progress reporting. In stage 2, all Pdiff patches are fetched, so we can apply them in parallel with fetching other files in stage 3. In stage 3, all other files are fetched (complete index files such as Contents, Packages). Performance improvements, mainly from fetching the pdiff patches before complete files, so they can be applied in parallel: For the 01 Sep 2016 03:35:23 UTC -> 02 Sep 2016 09:25:37 update of Debian unstable and testing with Contents and appstream for amd64 and i386, update time reduced from 37 seconds to 24-28 seconds. Previously, apt would first download new DEP11 icon tarballs and metadata files, causing the CPU to be idle. By fetching the diffs in stage 2, we can now patch our contents and Packages files while we are downloading the DEP11 stuff. 2016-09-02T12:34:37Z Julian Andres Klode jak@debian.org 2016-09-02T12:09:52Z urn:sha1:99ba7cc1901c761c97d67775f23858b86594f2ba If a non-existing source directory is specified, try finding the system gtest library. Debian derived distributions are a bit strange because they only ship the source code and not the library... 2016-09-01T17:24:26Z David Kalnischkies david@kalnischkies.de 2016-09-01T16:55:20Z urn:sha1:6dc85f53d92b9763a1509a6472227c54bc70b01d In gpgv1 GOODSIG (and the other messages of status-fd) are documented as sending the long keyid. In gpgv2 it is documented to be either long keyid or the fingerprint. At the moment it is still the long keyid, but the documentation hints at the possibility of changing this. We care about this for Signed-By support as we detect this way if the right fingerprint has signed this file (or not). The check itself is done via VALIDSIG which always is a fingerprint, but there must also be a GOODSIG (as expired sigs are valid, too) found to be accepted which wouldn't be found in the fingerprint-case and the signature hence refused. 2016-09-01T14:13:32Z David Kalnischkies david@kalnischkies.de 2016-09-01T06:49:22Z urn:sha1:d8a57c1953b876917a9deb098d1ef3d2b093f3dc Gbp-Dch: Ignore Reported-By: gcc -Wmissing-declarations 2016-09-01T09:00:10Z Julian Andres Klode jak@debian.org 2016-09-01T08:57:49Z urn:sha1:0343b48e06fb990ee15a020bc6716b1a5a984e14 gpg annoyingly changed its output and broke our test suite again by adding two extra lines about key type and issuer. Really annoying. Those lines also have more than one space after the colon, so let's use \s* there - and also change the other lines to support variable length whitespace in case gpg decides to break things there too. 2016-08-31T10:26:39Z Julian Andres Klode jak@debian.org 2016-08-31T10:25:38Z urn:sha1:832f95f4d018f18ff7b3d0381206f25b5a4373a6 I actually tried to amend the previous commit, but apparently I forgot to add the file mode change. Gbp-Dch: ignore 2016-08-31T10:12:56Z Julian Andres Klode jak@debian.org 2016-08-31T09:36:44Z urn:sha1:ce6cd75dc367b92f65e4fb539dd166d0f3361f8c If a Binary field contains one or more spaces before a comma, the code produced a segmentation fault, as it accidentally set a pointer to 0 instead of the value of the pointer. If the comma is at the beginning of the field, the code would create a binStartNext that points one element before the start of the string, which is undefined behavior. We also need to check that we do not exit the string during the replacement of spaces before commas: A string of the form " ," would normally exit the boundary of the Buffer: binStartNext = offset 1 ',' binEnd = offset 0 ' ' isspace_ascii(*binEnd) = true => --binEnd => binEnd = - 1 We get rid of the problem by only allowing spaces to be eliminated if they are not the first character of the buffer: binStartNext = offset 1 ',' binEnd = offset 0 ' ' binEnd > buffer = false, isspace_ascii(*binEnd) = true => exit loop => binEnd remains 0 2016-08-30T15:37:59Z Julian Andres Klode jak@debian.org 2016-08-30T15:37:59Z urn:sha1:9109c3c309e95a6d99a88f945f17c37e5c04c105 This works around an issue on Fedora where dpkg complains about missing build-essential: dpkg-checkbuilddeps: Unmet build dependencies: build-essential:native Gbp-Dch: ignore 2016-08-29T13:42:06Z Julian Andres Klode jak@debian.org 2016-08-19T18:37:28Z urn:sha1:30ea7a60404ee53393235827202968393951d106 Introduce a new -qq mode for our integration test framework, and make travis use it. The new -qq mode sets MSGLEVEL to 1. In MSGLEVEL=1, no messages are generated for passed tests, and all testcase filenames are printed in the same line. Also install first in travis, do not ls the installed output and run the install with chronic, so we only get output if it failed. Gbp-Dch: ignore 2016-08-29T07:22:25Z David Kalnischkies david@kalnischkies.de 2016-08-28T20:56:17Z urn:sha1:e950b7e2f89b5e48192cd469c963a44fff9f1450 An absolute filename for a *.deb file starts with a /. A package with the name of the file is inserted in the cache which is provided by the "real" package for internal reasons. The pinning code detects a regex based wildcard by having the regex start with /. That is no problem as a / can not be included in a package name… expect that our virtual filename package can and does. We fix this two ways actually: First, a regex is only being considered a regex if it also ends with / (we don't support flags). That stops our problem with the virtual filename packages already, but to be sure we also do not enter the loop if matcher and package name are equal. It has to be noted that the creation of pins for virtual packages like the here effected filename packages is pointless as only versions can be pinned, but checking that a package is really purely virtual is too costly compared to just creating an unused pin. Closes: 835818