Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.3 2016-09-20T21:54:19Z 2016-09-20T21:54:19Z Julian Andres Klode jak@debian.org 2016-09-20T21:54:19Z urn:sha1:1f7c56acc6b36b7869294941c8eba2b026eaaeb1 2016-09-18T12:17:17Z Julian Andres Klode jak@debian.org 2016-09-18T11:24:35Z urn:sha1:708e2f1fe99e6f067292bc909f03f12c181e4798 If the dependency line does not contain spaces in the repository but does in the dpkg status file (because dpkg normalized the dependency list), the dpkg line might be longer than the line in the repository. If it now happens to be longer than 1024 characters, it would be skipped, causing the hashes to be out of date. Note that we have to bump the minor cache version again as this changes the format slightly, and we might get mismatches with an older src cache otherwise. Fixes Debian/apt#23 2016-09-11T15:45:20Z Julian Andres Klode jak@debian.org 2016-09-11T15:45:20Z urn:sha1:acddd9188c21c2e13aff5cea3a82f2d01aff788b This allows fully automated code coverage testing, which is basically awesome. To allow the methods and solvers and stuff which run as _apt to write to our build directory, we need to adjust the permissions a bit, but otherwise it's OK. Gbp-Dch: ignore 2016-09-11T15:44:17Z Julian Andres Klode jak@debian.org 2016-09-11T11:58:40Z urn:sha1:bccb344412a0e97afdf0aaaf41a31124c84f6eaa We need to ignore messages from gcov. All those messages start with profiling: and are printed using vfprintf(), so the only thing we can do is add a library overriding those functions and linking apt-pkg to it. 2016-09-11T11:53:49Z Julian Andres Klode jak@debian.org 2016-09-11T11:53:49Z urn:sha1:422a2eba84361a8dfd84b549c13037512779c572 This allows us to easily test coverage 2016-09-11T11:49:23Z Julian Andres Klode jak@debian.org 2016-09-11T11:49:23Z urn:sha1:e09a8a611e27e1f08dbe8415dafa4679e5ab23fc This cleans up the output a bit, it should also improve performance, but unfortunately, this does not really seem to be the case. Gbp-Dch: ignore 2016-09-07T12:00:38Z Julian Andres Klode jak@debian.org 2016-09-07T11:35:40Z urn:sha1:561a3557e7fa6c4ed693c3bb486d189a468a8080 Even if we only configure a single architecture, install dpkg, so dpkg can assert multi arch correctly. This also has the nice side effect of making single architecture and multiple architecture test cases more uniform. This fixes a regression from f878d3a862128bc1385616751ae1d78246b1bd01 ("test: Assert multi-arch in the chroot"). 2016-09-07T12:00:37Z Julian Andres Klode jak@debian.org 2016-09-07T11:23:26Z urn:sha1:c382e0dff11beb00632d67d9361831358a38e465 If we copied one of the existing status files, we might not have a trailing newline, so let's add one. Gbp-Dch: ignore 2016-09-07T08:21:01Z David Kalnischkies david@kalnischkies.de 2016-09-07T08:21:01Z urn:sha1:12b201da7c1d5e2beceae796151e4ebedc5bae97 Commit b60c8a89c281f2bb945d426d2215cbf8f5760738 improved the situation, but due to inconsistency mostly for planners, not for solvers. As the idea of hiding errors if we show another error is a bit scary (as the extern error might be a followup of our intern error, rather than the reason for our intern error as it is at the moment) we don't discard the errors, but if we got an extern error we show them directly removing them from the error list at the end of the run – that list will contain the extern error which hopefully gives us the best of both worlds. The problem itself is the same as before: The externals exiting before apt is done talking to them. Reported-By: Johannes 'josch' Schauer on IRC 2016-09-04T20:00:48Z David Kalnischkies david@kalnischkies.de 2016-09-04T16:53:26Z urn:sha1:99fdd8034b4a5cdb0100a33d0b3d5e26079c1695 Commit 3af3ac2f5ec007badeded46a94be2bd06b9917a2 (released in 1.3~pre1) implements proper fallback for SRV, but that works actually too good as the RFC defines that such an SRV record should indicate that the server doesn't provide this service and apt should respect this. The solution is hence to fail again as requested even if that isn't what the user (and perhaps even the server admins) wanted. At least we will print a message now explicitly mentioning SRV to point people in the right direction. Reported-In: https://bugs.kali.org/view.php?id=3525 Reported-By: Raphaël Hertzog