Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.4_beta2 2016-11-24T23:15:13Z 2016-11-24T23:15:13Z David Kalnischkies david@kalnischkies.de 2016-11-24T11:14:39Z urn:sha1:e1ae0531bfad0fce8590c26d1e38825df22d812a The test test-handle-redirect-as-used-mirror-change serves multiple clients at the same time, so the order of the output is undefined and once in a while the two clients will intermix their lines causing the grep we perform on it later to fail making our tests fail. Solved by introducing client-specific logfiles which we all grep and sort the result to have the results more stable. Git-Dch: Ignore 2016-11-24T23:15:13Z David Kalnischkies david@kalnischkies.de 2016-11-18T11:12:51Z urn:sha1:0123ce7171b09ead5a07567fbd33c53f609f6560 2016-11-24T23:15:12Z David Kalnischkies david@kalnischkies.de 2016-11-13T19:52:18Z urn:sha1:2906182db398419a9c59a928b7ae73cf7c7aa307 Having binary files in /etc is kinda annoying – not that the armored files are much better – but it is hard to keep tabs on which format the file has ("simple" or "keybox") and different gnupg versions have different default binary formats which can be confusing for users to work with (beside that it is binary). Adding support for this now will enable us in some distant future to move to armored later on, much like we added trusted.gpg.d years before the world picked it up. 2016-11-23T23:21:35Z David Kalnischkies david@kalnischkies.de 2016-11-23T18:02:51Z urn:sha1:53f3fc59f4eb37eea57bbde53fb75f2e15af0378 dpkg stumbles over these (#844300) and we haven't dropped 'easier' removes to be implicit and to be scheduled by dpkg by default so far so we shouldn't push the decision in such cases to dpkg either. 2016-11-23T23:21:35Z David Kalnischkies david@kalnischkies.de 2016-11-23T16:32:20Z urn:sha1:4b10240cca0dc0a4e82e42959545d2ae7e622d29 Our old idea was to look for the first package which would be "touched" and take this as the package dpkg is talking about, but that is incorrect in complicated situations like a package upgraded to/from multiple M-A:same siblings installed. As we us the progress report to decide what is still needed we have to be reasonabily right about the package dpkg is talking about, so we jump to quite a few loops to get it. 2016-11-23T15:37:39Z David Kalnischkies david@kalnischkies.de 2016-11-12T10:32:13Z urn:sha1:dabe9e2482180ada77d2adda2b3c03db22059fb8 Given that we use the progress information to skip over actions dpkg has already done like not purging a package which was already removed and had no config files or not acting on disappeared packages and such it is important that apt and dpkg agree on which states the package has to pass through. To ensure that we keep tabs on this in the future a warning is added at the end if apt hasn't seen all the action it was supposed to see. I can't wait for the first bugreporters to wonder about this… 2016-11-11T22:40:39Z James Clarke jrtc27@jrtc27.com 2016-11-11T16:33:25Z urn:sha1:a658ffbf1911ae9b9838615d0a60f4613e642553 This also changes Acquire-By-Hash to be "yes" rather than "true", so it is consistent with dak's output. Closes: #272557 2016-11-11T22:40:39Z David Kalnischkies david@kalnischkies.de 2016-11-11T12:15:27Z urn:sha1:7434f15cb688f3a394accba2ce10615adcb9c48a We have the last Release file around for other checks, so its trivial to look if the new Release file contains a new codename (e.g. the user has "testing" in the sources and it flipped from stretch to buster). Such a change can be okay and expected, but also be a hint of problems, so a warning if we see it happen seems okay. We can only print it once anyhow and frontends and co are likely to ignore/hide it. 2016-11-11T22:40:39Z David Kalnischkies david@kalnischkies.de 2016-11-11T12:05:38Z urn:sha1:d0c7d4d6328418b7c9f434a3398e5f7e08b7359c A suite or codename entry in the Release file is checked against the distribution field in the sources.list entry that lead to the download of that Release file. This distribution entry can contain slashes in the distribution field: deb http://security.debian.org/debian wheezy/updates main However, the Release file may only contain "wheezy" in the Codename field and not "wheezy/updates". So a transformation needs to take place that removes the last / and everything that comes after (e.g. "/updates"). This fails, however, for valid cases like a reprepro snapshot where the given Codename contains slashes but is perfectly fine and doesn't need to be transformed. Since that transformation is essentially just a workaround for special cases like the security repository, it should be checked if the literal Codename without any transformations happened is valid and only if isn't the dist should be checked against the transformated one. This way special cases like security.debian.org are handled and reprepro snapshots work too. The initial patch was taken as insperationto move whole transformation to CheckDist() which makes this method more accepting & easier to use (but according to codesearch.d.n we are the only users anyhow). Thanks: Lukas Anzinger for initial patch Closes: 644610 2016-11-11T22:40:39Z David Kalnischkies david@kalnischkies.de 2016-11-11T10:58:56Z urn:sha1:a9b724eedd0c9d8c36725c5b8f57d51ea9f7dcd1 You can pretty much achieve the same with a local dummy package if you want to, but libapt has an inbuilt setting for essential: "apt" which can be overridden with this option as well – it could be helpful in quick tests and what not so adding this alternative shouldn't really hurt much. We aren't going to document them much through as care must be taken in regards to the binary caches as they aren't invalidated by config options alone, so the effects of old settings could still be in them, similar to the other already existing pkgCacheGen option(s). Closes: 767891 Thanks: Anthony Towns for initial patch