Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.3_pre3 2016-07-22T14:05:10Z 2016-07-22T14:05:10Z David Kalnischkies david@kalnischkies.de 2016-07-10T12:14:43Z urn:sha1:8b21456acba3cbbc28f35eba684d8f21b0c290b4 APT doesn't know which packages will be triggered in the course of actions, so it can't plan to see them for progress beforehand, but if it sees that dpkg says that a package was triggered we can add additional states. This is pretty much magic – after all it sets back the progress – and there are cornercases in which this will result in incorrect totals (package in partial states may or may not loose trigger states), but the worst which can happen is that the progress is slightly incorrect and doesn't reach 100%, but so be it. Better than being stuck at 100% for a while as apt isn't realizing that a bunch of triggers still need to be processed. 2016-07-22T14:05:10Z David Kalnischkies david@kalnischkies.de 2016-07-21T13:54:22Z urn:sha1:84255101ee38693aea2fd456cf0da174434afa01 Hardcoding /var/crash means we can't test it properly and it isn't really our style. 2016-07-22T14:05:10Z David Kalnischkies david@kalnischkies.de 2016-07-21T09:34:08Z urn:sha1:e04a6ce61db5e5eaf4f954626c7833f00cdb5992 The progress reporting for a package sheduled for purging only included the states dpkg passes through while actually purging the package – if the package was fully installed before dpkg will pass first through all remove states before purging it, so in the interest of consistent reporting our progress reporting should do that, too. 2016-07-22T14:05:09Z David Kalnischkies david@kalnischkies.de 2016-07-08T13:59:23Z urn:sha1:92296fe4b0862a04ea3d965b4cd2d4a420e3be9f We support installing ./foo.deb (and ./foo.dsc for source) for a while now, but it can be a bit clunky to work with those directly if you e.g. build packages locally in a 'central' build-area. The changes files also include hashsums and can be signed, so this can also be considered an enhancement in terms of security as a user "just" has to verify the signature on the changes file then rather than checking all deb files individually in these manual installation procedures. 2016-07-22T14:04:36Z David Kalnischkies david@kalnischkies.de 2016-07-20T07:03:09Z urn:sha1:e8e5d464623f1c2e1ef96b14e622728bbf4b89af If a user explicitly requests the download of arch:all apt shouldn't get in the way and perform its detection dance if arch:all packages are (also) in arch:any files or not. This e.g. allows setting arch=all on a source with such a field (or one which doesn't support all at all, but has the arch:all files like Debian itself ATM) to get only the arch:all packages from there instead of behaving like a no-op. Reported-By: Helmut Grohne on IRC 2016-07-19T21:06:20Z David Kalnischkies david@kalnischkies.de 2016-07-19T21:06:20Z urn:sha1:36d5299aacb950aeb8cb117fa603abb21643d844 Moving code around into some more dedicated methods, no effective code change itself. Gbp-Dch: Ignore 2016-07-19T16:20:38Z David Kalnischkies david@kalnischkies.de 2016-07-19T16:20:38Z urn:sha1:475f75506db48a7fa90711fce4ed129f6a14cc9a Theoretically it should be enough to change the Dir setting and have apt pick the dpkg/status file from that. Also, it should be consistently effected by RootDir. Both wasn't really the case through, so a user had to explicitly set it too (or ignore it and have or not have expected sideeffects caused by it). This commit tries to guess better the location of the dpkg/status file by setting dir::state::status to a naive "../dpkg/status", just that this setting would be interpreted as relative to the CWD and not relative to the dir::state directory. Also, the status file isn't really relative to the state files apt has in /var/lib/apt/ as evident if we consider that apt/ could be a symlink to someplace else and "../dpkg" not effected by it, so what we do here is an explicit replace on apt/ – similar to how we create directories if it ends in apt/ – with dpkg/. As this is a change it has the potential to cause regressions in so far as the dpkg/status file of the "host" system is no longer used if you set a "chroot" system via the Dir setting – but that tends to be intended and causes people to painfully figure out that they had to set this explicitly before, so that it now works more in terms of how the other Dir settings work (aka "as expected"). If using the host status file is really intended it is in fact easier to set this explicitely compared to setting the new "magic" location explicitely. 2016-07-01T11:36:40Z David Kalnischkies david@kalnischkies.de 2016-07-01T11:17:03Z urn:sha1:e7edb2fef8370d54a4b8e5a01266e6eda81ef84e If we have a (e.g. locally built) deb file installed and do try to install it again apt complained about this being a downgrade, but it wasn't as it is the very same version… it was just confused into not merging the versions together which looks like a downgrade then. The same size assumption is usually good, but given that volatile files are parsed last (even after the status file) the base assumption no longer holds, but is easy to adept without actually changing anything in practice. 2016-06-29T14:10:12Z David Kalnischkies david@kalnischkies.de 2016-06-29T14:10:12Z urn:sha1:309f497b7280a45e3626493318adb6d39ba5c69b Writing first means that even in the event of a power-failure the autobit is saved for future processing instead of "forgotten" so that the package is treated as manually installed. In some cases we have to re-run the writing after dpkg is done through as dpkg can let packages disappear and in such cases apt will move autobits around (or in that case non-autobits) which we need to store. 2016-06-29T10:23:02Z David Kalnischkies david@kalnischkies.de 2016-06-29T09:00:04Z urn:sha1:cfc6566d5097ef5518e12f5c1e5f15a8f5b182cf This reverts commit 2b8221d66a8284042fc53c7bbb14bb9750e9137f. Avoiding the use of GCC >= 5 stuff lets use go back to 4.8 simplifying the travis setup again as well as reducing the backport requirements in general. This is possible because the std::get_time use requiring GCC >= 5 in 9febc2b238e1e322dce1f94ecbed46d595893b52 was replaced by handrolling it in 1d742e01470bba27715a8191c50adde4b39c2f19, so the remaining uses are just small conviniences we can do without. Gbp-Dch: Ignore