apt/apt-pkg/contrib, branch 2.0.1Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.0.12020-03-24T09:24:39ZAdd color highlighting to E:/W:/N: prefixes2020-03-24T09:24:39ZJulian Andres Klodejulian.klode@canonical.com2020-03-10T21:26:52Zurn:sha1:768f0031930a994ecfab84ecd6478852275a98c3
This matches the definitions used by dpkg.
Closes: #953527
error: Extract operator<< into error.cc (de-inline it)2020-03-10T21:29:46ZJulian Andres Klodejulian.klode@canonical.com2020-03-10T21:24:20Zurn:sha1:b0e2c9de13ff1df2f0f1cba2ceed88c710efea3a
Extract the code, and reformat it with clang-format so we can
modify it.
Show absolute time while waiting for lock instead of %, rework message2020-03-06T12:14:37ZJulian Andres Klodejulian.klode@canonical.com2020-03-06T12:10:04Zurn:sha1:1b81f6bd13bb31e59da3f53cfdc7caab43abf887
Showing a percentage for a timeout is pretty non-standard. Rework the
progress class so it can show an absolute progress (currently hardcoded
to use seconds as a unit). If there is a timeout (aka if it's not the
maximum long long unsigned -1llu), then show the timeout, otherwise
just count up seconds, e.g.
Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 33842 (apt)... 1/120s
or
Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 33842 (apt)... 1s
Also improve the error message to use "Waiting for cache lock: %s" instead of "... (%s)", as having
multiple sentences inside parenthesis is super weird, as is having two closing parens.
We pass the information via _config, as that's reasonably easy and avoids
ABI hackage. It also provides an interesting debugging tool for other
kinds of progress.
GetLock: No strerror if it's just another process holding the lock2020-03-06T12:07:55ZJulian Andres Klodejulian.klode@canonical.com2020-03-06T12:07:55Zurn:sha1:68a83a64cd424385b613f58e23c03e262d840b91
This improves the locking message, getting rid of useless details. If
we have a process holding the lock, we got that because the lock is
being hold by it, so there's no point telling the people the reason
for not getting the lock is the EAGAIN error and displaying its
strerrror().
apt-pkg: default visibility to hidden2020-02-26T19:34:54ZJulian Andres Klodejulian.klode@canonical.com2019-08-13T17:15:19Zurn:sha1:db678df196ccd8f9f6fb336706cf5701d1e53aa6Fix various compiler warnings2020-02-26T17:59:31ZJulian Andres Klodejulian.klode@canonical.com2020-02-26T17:26:13Zurn:sha1:d36b06d7eb300ca5cbee22b4fcedaefc80585da1Merge CommandLine::DispatchArg2020-02-26T12:56:45ZJulian Andres Klodejulian.klode@canonical.com2020-02-26T12:56:45Zurn:sha1:b2eec2572ce1c8e79ac3a270161cc5d415169840Remove left-over SummationImplementation class2020-02-25T19:48:01ZJulian Andres Klodejulian.klode@canonical.com2020-02-25T19:48:01Zurn:sha1:927c08f2d378e8be9eba97fc1a3c790557d8fb70Initialize libgcrypt on first use2020-02-25T18:07:15ZJulian Andres Klodejulian.klode@canonical.com2020-02-25T18:03:12Zurn:sha1:65b77c941780c8e1819f527879b0b8e2642839dd
This is not supposed to be done this way, but frankly, since we
abstract away the backend, there's not much else we can do here.
Closes: #949074
Remove CRC-16 implementation2020-02-18T12:40:22ZJulian Andres Klodejulian.klode@canonical.com2020-01-17T13:35:04Zurn:sha1:237ef6d210a0370131deb58277e77d579d58d15a