Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.8.0_alpha2 2018-09-20T16:36:03Z 2018-09-20T16:36:03Z David Kalnischkies david@kalnischkies.de 2018-09-20T15:22:54Z urn:sha1:6f1d622c84b3b7f821683bf69b8fcdb6dcf272a2 The implementation of "apt-cache show" (not "apt show") incorrectly resets the currently used parser if the record itself and the description to show come from the same file (as it is the case if no Translation-* files are available e.g. after debootstrap). The code is more complex than you would hope to support some rather unusual setups involving Descriptions and their translations as tested for by ./test-bug-712435-missing-descriptions as otherwise this could be a one-line change. Regression-Of: bf53f39c9a0221b670ffff74053ed36fc502d5a0 Closes: #909155 2018-09-15T15:45:16Z David Kalnischkies david@kalnischkies.de 2018-09-15T15:45:16Z urn:sha1:32e0587d1819ca4b09cd146b0114a1c56ce4a8a9 The uniqueness in std::set containers is ensured by the ordering operator we provide, but it was not considering that different versions can have the same description like the different architectures for a version of a package. Closes: #908218 2018-08-07T13:51:13Z Julian Andres Klode jak@debian.org 2018-08-07T13:51:13Z urn:sha1:e165588b0b9bc7c484c91e324b6b9418b0a29457 Add support for dpkg frontend lock See merge request apt-team/apt!11 2018-08-07T13:07:52Z Julian Andres Klode jak@debian.org 2017-01-29T12:05:18Z urn:sha1:c2c8b4787b0882234ba2772ec7513afbf97b563a The dpkg frontend lock is a lock dpkg tries to acquire except if the frontend already acquires it. This fixes a race condition in the install command where the dpkg lock is not held for a short period of time between different dpkg invocations. For this reason we also define an environment variable DPKG_FRONTEND_LOCKED for dpkg invocations so dpkg knows not to try to acquire the frontend lock because it's held by a parent process. We can set DPKG_FRONTEND_LOCKED only if the frontend lock really is held; that is, if our lock count is greater than 0 - otherwise an apt client not using the LockInner family of functions would run dpkg without the frontend lock set, but with DPKG_FRONTEND_LOCKED set. Such a process has a weaker guarantee: Because dpkg would not lock the frontend lock either, the process is prone to the existing races, and, more importantly, so is a new style process. Closes: #869546 [fixups: fix error messages, add public IsLocked() method, and make {Un,}LockInner return an error on !debSystem] 2018-07-01T04:10:08Z Jean-Ralph Aviles jeanralph.aviles@gmail.com 2018-07-01T04:10:08Z urn:sha1:8a6caaf869ea87ade6043169076bda04a0dc6cb6 Makes the console output cleaner. 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 2018-05-11T15:58:46Z David Kalnischkies david@kalnischkies.de 2018-04-12T07:59:47Z urn:sha1:6085ab7488326cfed8f82e07eefcbc2dc40d4bea Now that --with-source is supported in show we can go a little further and add the "syntactic sugar" of supporting deb-files on the commandline directly to give users an alternative to remembering dpkg -I for deb files & as a bonus apt also works on changes files. Most of the code churn is actually to deal with cases probably not too common in reality like mixing packages and deb-files on the commandline and getting the right order for these multiple records. Closes: 883206 2018-05-11T15:58:46Z David Kalnischkies david@kalnischkies.de 2018-04-11T10:59:06Z urn:sha1:bf53f39c9a0221b670ffff74053ed36fc502d5a0 2018-05-11T15:58:46Z David Kalnischkies david@kalnischkies.de 2018-01-26T22:33:25Z urn:sha1:ce9223cc4e4ffcc43d17ae97ff8c57fb759a2c49 The syntax is a bit awkward, but it is the same as for a package name and introducing another syntax wouldn't really help usability, so with apt install ./foo.deb/experimental you will get the dependencies of foo satisfied by your default release, but if this wouldn't satisfy the version requirements the candidate for this dependency is switched to the version from the experimental release. The same applies for apt build-dep ./foo.dsc/stable-backports which was the initial request. 2018-05-11T15:58:46Z David Kalnischkies david@kalnischkies.de 2018-01-26T15:15:13Z urn:sha1:9169cd5049bd7f0d5dcc56c40d567a766cf5b851 apt install pkg/release follows versioned dependencies in the candidate switching if the current candidate does not satisfy the dependency, so for uniformity the same should be supported in build-dep.