apt/test, branch 1.7.0_alpha2 Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.7.0_alpha2 2018-06-27T13:09:45Z Handle JSON hooks that just close the file/exit and fix some other errors 2018-06-27T13:09:45Z Julian Andres Klode julian.klode@canonical.com 2018-06-27T09:31:21Z urn:sha1:1d53cffad22c92645090e0e6ddde31fe4f7c3b05 JSON hooks might disappear and the common idiom to work around hooks disappearing is to check for the hook in the shell snippet that is in the apt.conf file and if it does not exist, do nothing. This caused APT to fail however, expecting it to acknowledge the handshake. Ignoring ECONNRESET on handshakes solves the problem. The error case, and the other error cases also did not stop execution of the hook, causing more errors to pile up. Fix this by directly going to the closing part of the code. LP: #1776218 Don't show acquire warning for "hidden" components 2018-05-28T15:57:25Z David Kalnischkies david@kalnischkies.de 2018-05-28T15:02:17Z urn:sha1:484babb7d00f7550cbaa592b7cb0022d38217fad Commit d7c92411dc1f4c6be098d1425f9c1c075e0c2154 introduced a warning for non-existent files from components not mentioned in Components to hint users at a mispelling or the disappearance of a component. The debian-installer subcomponent isn't actively advertised in the Release file through, so if apt ends up in acquiring a file which doesn't exist for this component (like Translation files) apt would produce a warning: W: Skipping acquire of configured file 'main/debian-installer/i18n/Translation-en' as repository 'http://deb.debian.org/debian buster InRelease' doesn't have the component 'main/debian-installer' (component misspelt in sources.list?) We prevent this in the future by checking if any file exists from this component which results in the warning to be produced still for the intended cases and silence it on the d-i case. This could potentially cause the warning not to be produced in cases it should be if some marginal file remains, but as this message is just a hint and the setup a bit pathological lets ignore it for now. There is also the possibility of having no file present as they would all be 0-length files and being a "hidden" component, but that would be easy to workaround from the repository side and isn't really actively used at the moment in the wild. Closes: #879591 tests: Prevent stunnel4 from binding on IPv6 2018-05-28T15:57:20Z David Kalnischkies david@kalnischkies.de 2018-05-26T14:28:03Z urn:sha1:c94988e75ea923afe0daae5747f974927325b186 Hardcoding the IPv4 address 127.0.0.1 stops stunnel4 from also binding on IPv6 as well which not only binds on another port but confuses our crude port extraction by splitting on ':' with ::1. Gbp-Dch: Ignore Merge branch 'feature/morevolatilesupport' into 'master' 2018-05-24T13:04:22Z Julian Andres Klode jak@debian.org 2018-05-24T13:04:22Z urn:sha1:6eaeec549241677335813af78f394010e5b3eefb more volatile: build-dep foo.deb/release & show foo.deb See merge request apt-team/apt!14 Merge branch 'feature/byhashviaalturl' into 'master' 2018-05-24T12:54:34Z Julian Andres Klode jak@debian.org 2018-05-24T12:54:34Z urn:sha1:b367f2d393fa95a386feb03a64d4bf5e32cc28a4 Don't force the same mirror for by-hash URIs See merge request apt-team/apt!15 Extend test-apt-get-autoremove to check debug output 2018-05-21T16:19:33Z Filipe Brandenburger filbranden@google.com 2018-05-16T05:24:29Z urn:sha1:5d263a39d6106f6d20b2b447ffc14ef0c096ea22 Run `apt-get autoremove -o Debug::pkgAutoRemove=yes` and confirm the logged reason for packages to be kept is correct. Only check for specific debug lines containing 'MarkPackage:' in order to prevent new debug logging to break the test case. Fix hidden test failure if not called via sudo 2018-05-19T19:39:08Z David Kalnischkies david@kalnischkies.de 2018-05-19T19:10:17Z urn:sha1:ea901a491bcfe406267c7c38c227c5caabf017a0 id: '': no such user ./test-bug-611729-mark-as-manual: 59: [: Illegal number: Regression-of: 68842e1741a5005b1e3f0a07deffd737c65e3294 Gbp-Dch: Ignore tests: Do not expect requested-by if sudo was invoked by root 2018-05-16T10:10:52Z Julian Andres Klode julian.klode@canonical.com 2018-05-16T10:09:47Z urn:sha1:68842e1741a5005b1e3f0a07deffd737c65e3294 If sudo was invoked by root, SUDO_UID will be 0, and apt will not print a Requested-By line. Handle by-hash URI construction more centrally 2018-05-11T16:28:29Z David Kalnischkies david@kalnischkies.de 2018-01-15T11:04:45Z urn:sha1:ed0e9eadeb3003f4f150da3c463b28cfa5e54b6f Individual items shouldn't concern themselves with these alternative locations, we can deal with this more efficiently within the infrastructure created for other alternative URIs now avoiding the need to implement this in each item. Drop alternative URIs we got a hash-based fail from 2018-05-11T16:28:19Z David Kalnischkies david@kalnischkies.de 2018-01-13T23:07:20Z urn:sha1:2d6c6c8809c7b4c1a009df48387ba15066fda7e2 If we got a file but it produced a hash error, mismatched size or similar we shouldn't fallback to alternative URIs as they likely result in the same error. If we can we should instead use another mirror. We used to be a lot stricter by stopping all trys for this file if we got a non-404 (or a hash-based) failure, but that is too hard as we really want to try other mirrors (if we have them) in the hope that they have the expected and correct files.