Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.7.0_rc2 2018-09-20T19:04:11Z 2018-09-20T19:04:11Z Julian Andres Klode julian.klode@canonical.com 2018-09-20T19:04:11Z urn:sha1:e78844ba89fd15879333c1394fae9a65acebedc0 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-18T14:16:06Z Julian Andres Klode julian.klode@canonical.com 2018-09-18T14:15:35Z urn:sha1:e323a6bfffcb3119dc75dfa364e2488b8990fdb4 2018-09-18T14:10:03Z Julian Andres Klode jak@debian.org 2018-09-18T14:10:03Z urn:sha1:64efbcd06aa8038e47db7a8bea2d0f388a3e1bb5 http: Stop pipeline after close only if it was not filled before See merge request apt-team/apt!25 2018-09-18T14:07:24Z Julian Andres Klode julian.klode@canonical.com 2018-08-31T14:07:07Z urn:sha1:df696650b7a8c58bbd92e0e1619e956f21010a96 It is perfectly valid behavior for a server to respond with Connection: close eventually, even when pipelining. Turning off pipelining due to that is wrong. For example, some Ubuntu mirrors close the connection after 101 requests. If I have more packages to install, only the first 101 would benefit from pipelining. This commit introduces a new check to only turn of pipelining for future connections if the pipeline for this connection did not have 3 successful fetches before, that should work quite well to detect broken server/proxy combinations like in bug 832113. 2018-09-18T12:05:20Z Julian Andres Klode jak@debian.org 2018-09-18T12:05:20Z urn:sha1:252a0a5020726a7b1ee53f2ed5f00e1210f5f4d1 Process all of --status-fd and don't expect duplicate status msg See merge request apt-team/apt!26 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-09-11T11:08:58Z David Kalnischkies david@kalnischkies.de 2018-09-10T19:34:11Z urn:sha1:329c8d5e149465003ea9007661a7af1099c75c43 We are seeing 'processing' messages from dpkg first, so it makes sense to translate them to "Preparing" messages instead of using "Installing" and co to override these shortly after with the "Preparing" messages. The difference isn't all to visible as later messages tend to linger far longer in the display than the ealier ones, but at least in a listing it seems more logical. 2018-09-11T11:08:58Z David Kalnischkies david@kalnischkies.de 2018-09-10T16:43:34Z urn:sha1:f484906eff85c8c9eadc13ce817d8857abdd08e8 The progress reporting relies on parsing the status reports of dpkg which used to repeat being in the same state multiple times in the same run, but by fixing #365921 it will stop doing so. The problem is in theory just with 'config-files' in case we do purge as this (can) do remove + purge in one step, but we remove this also for the unpack + configure combination althrough we handle these currently in two independent dpkg calls. 2018-09-11T11:08:58Z David Kalnischkies david@kalnischkies.de 2018-09-09T17:45:42Z urn:sha1:2295de2c97e6d1290a86e0b160885212411510a5 Exiting the processing loop as soon as the dpkg process finishes might leave status-fd lines unprocessed which wasn't much of a problem in the past as the progress would just be slightly off, but now that we us the information also for skipping already done tasks and generate warnings if we didn't see all expected messages we should make sure we seem them all. We still need to exit "early" if dpkg exited unsuccessfully/crashed through as the (remaining) status lines we get could be incomplete.