Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.3.1 2021-04-13T15:26:59Z 2021-04-13T15:26:59Z Julian Andres Klode julian.klode@canonical.com 2021-04-13T15:26:59Z urn:sha1:8f84d45b7b7fcefb622314b74ac103dba347fb7c 2021-04-13T15:23:03Z Julian Andres Klode julian.klode@canonical.com 2021-04-13T15:23:03Z urn:sha1:e59d47fbde4ee9372a91360d5e9af34f23dea4b8 2021-04-13T15:22:37Z Julian Andres Klode jak@debian.org 2021-04-13T15:22:37Z urn:sha1:734c6ce0d3250d0b35cf3d0dd54e8baae3774fa8 Fix downloads of unsized files that are largest in pipeline See merge request apt-team/apt!161 2021-04-13T14:13:24Z Julian Andres Klode jak@debian.org 2021-04-13T14:13:24Z urn:sha1:7a3b13832bf60d8d086c07ea96aa656ac9439f66 add vendor information for Procursus. https://github.com/ProcursusTeam/Procursus is a project to get an updated \*nix environment on Darwin platforms such as iOS and x86_64/arm64 macOS. See merge request apt-team/apt!163 2021-04-13T14:00:41Z Julian Andres Klode julian.klode@canonical.com 2021-04-09T16:16:10Z urn:sha1:1412cf51403286e9c040f9f86fd4d8306e62aff2 Repositories without Size information for packages are not proper and need fixing. This ensures people see an error in CI, and get notifications and hence the ability to fix it. It can be turned off by setting Acquire::AllowUnsizedPackages to true. 2021-04-13T14:00:41Z Julian Andres Klode julian.klode@canonical.com 2021-04-09T16:11:02Z urn:sha1:27a4fb3a9ac67a13ed516c75feefdc1fd426520a The maximum request size is accidentally set to any sized file, so if an unsized file is present, and it turns out to be larger than the maximum size we set, we'd error out when checking if its size is smaller than the maximum request size. LP: #1921626 2021-04-13T12:34:36Z Cameron Katri me@cameronkatri.com 2021-04-13T12:34:36Z urn:sha1:76012b5cf8a0d51398992909878ec2bbcecc1536 2021-04-13T12:30:19Z Julian Andres Klode jak@debian.org 2021-04-13T12:30:19Z urn:sha1:aa6cbf09c24ae135ea3547c94869f28f8dec2b5a Replace macro and manual management with lambda and RAII See merge request apt-team/apt!160 2021-03-31T13:29:09Z Julian Andres Klode julian.klode@canonical.com 2021-03-31T13:25:18Z urn:sha1:8613225f314e2524d9178e232940059a8687cc69 MaybeAddAuth() here tells us that it refused to use the credentials for an http source; but that caused the test suite to fail at a later stage because we checked if there were any errors/warning. Strangely, this is only triggered with LTO enabled. Actually check that the warning is being set and then reject it. 2021-03-11T13:05:41Z David Kalnischkies david@kalnischkies.de 2021-03-11T12:38:53Z urn:sha1:0d25ce3d466ecddea02d171981f011f7dbf95e08 If a transaction is doomed we want to gracefully shutdown our zoo of worker processes. As explained in the referenced commit we do this by stopping the main process from handing out new work and ignoring the replies it gets from the workers, so that they eventually run out of work. We tested this previously by checking if a rred worker was given work items at all, but depending on how lucky the stars of the machine working on this are the worker would have already gotten work before the transaction was aborted – so we tried this 25 times a row (f35601e5d2). No machine can be this lucky, right? Turns out the autopkgtest armhf machine is very lucky. I feel a bit sorry for feeding grep such a long "line" to work with, but it seems to work out. Porterbox amdahl (who is considerably less lucky; had to turn down to 1 try to get it to fail sometimes) is now happily running the test in an endless loop. Of course, I could have broken the test now, but its still a rather generic grep (in some ways more generic even) and the main part of the testcase – the update process finishes and fails – is untouched. References: 38f8704e419ed93f433129e20df5611df6652620 Closes: #984966