Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.3.9 2021-08-28T20:21:35Z 2021-08-28T20:21:35Z David Kalnischkies david@kalnischkies.de 2021-08-28T13:55:09Z urn:sha1:c7e368aafe099dcd966cf5994ae7fb418d268278 fullyExplored is needed to keep track of having explored all providers of a package name, while Marked is tracking if we have explored a given real package (along its chosen version), so we should stop MarkPackage from exploring a (real) package if it is marked and let fullyExplored only guard the looping over the individual dependencies. The testcase is deceptively simple, but in practice only an ecosystem like rust who makes heavy use of cyclic dependency relations intermixed with versioned provides actually triggers this as seen by the buggy code being in use for four months in Debian and Ubuntu development releases. (easier to trigger if most packages are marked manual installed) Note that the testcase is successful already due to the earlier changes as we exit the recursion eventually and all packages are marked as they need to be already, but this fix does work standalone as well. Closes: #992993 2021-08-28T19:11:33Z David Kalnischkies david@kalnischkies.de 2021-04-25T20:26:42Z urn:sha1:255ec5a46aa55ad96e7dc7f9d43d5cdf71627812 If the system tells us that a core dump was created we should try to display the contained info as that system might not be easily available when we see the error (like C-I or autopkgtest). Gbp-Dch: Ignore 2021-07-29T09:50:16Z Julian Andres Klode julian.klode@canonical.com 2021-07-29T09:49:05Z urn:sha1:3ca5e18b1f0bb05697ccca7c98ced1176166024a This delay of 4+2+1=7 seconds in unnecessary. 2021-07-29T09:49:59Z Julian Andres Klode julian.klode@canonical.com 2021-07-29T09:46:47Z urn:sha1:70ee96670bbc09e724aeeb6263ee6a3bdde8afdc This is subject to clock skew, unfortunately, as we cannot read monotonic time in shell. We check for >=5s out of the 7s it should take to reduce the risk of skew a bit. 2021-07-28T11:08:35Z Julian Andres Klode julian.klode@canonical.com 2021-07-28T10:43:56Z urn:sha1:4001af8920389e2bb2672b673b181c4e92515872 This is very basic support on the testing side, we just test the debug output but not how long it actually took. Would be nice to check time really. 2021-07-05T09:50:05Z Julian Andres Klode jak@debian.org 2021-07-05T09:50:05Z urn:sha1:544d81a26f8c97a2a45262aecbaef4a5b43fb325 Restore dpkg::chroot-directory functionality See merge request apt-team/apt!178 2021-07-05T09:50:02Z Julian Andres Klode jak@debian.org 2021-07-05T09:50:02Z urn:sha1:b1a384c646427e52abef5bdb799f7bbdbb505bb6 Allow packages from volatile sources to be reinstalled See merge request apt-team/apt!177 2021-07-01T09:34:04Z Julian Andres Klode julian.klode@canonical.com 2021-07-01T09:34:04Z urn:sha1:690f6191a4332123a912c812a19a37cef253e90c We just used the pointer returned which might be nullptr, properly call BuildSourceList() and check the result first. Closes: #990518 2021-06-10T17:25:17Z David Kalnischkies david@kalnischkies.de 2021-06-10T16:06:14Z urn:sha1:8083d4019844f764058efa2a950ed16975178bff If we call dpkg inside a chroot we have to ensure that the temporary directory we construct to call dpkg --recursive is inside the chroot and that we strip the path to the chroot from the directory name we pass to dpkg. Note that the added test succeeds before and (hopefully) after as we can't really chroot here or fiddle with the needed settings as we are already setting up apt to work with a quasi-chroot. The test perhaps helps in ensuring we don't break it too much in the future though. (Broken five years (and one day) ago this seems to have an immense user base at the moment, but it might in the future via mmdebstrap) References: f495992428a396e0f98886c9a761a804aa161c68 Reported-By: Johannes Schauer Marin Rodrigues on IRC Tested-By: Johannes Schauer Marin Rodrigues 2021-06-10T14:41:04Z David Kalnischkies david@kalnischkies.de 2021-06-10T14:41:04Z urn:sha1:e6056cbc8faf82c368d4439b0fcdcf4f46047d59 Just because two packages have the same version number doesn't mean it is the same package. APT can detect rebuilds and other "inconsistencies", but we had no explicit test for it so far. It turned out to be the wrong track in this branch, but as I wrote it already, lets add it at least. Gbp-Dch: Ignore