apt/test/integration/test-apt-cli-json-hooks, branch 2.9.1 Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=2.9.1 2022-09-02T14:55:45Z Avoid dealing with a fake dpkg stanza in the tests 2022-09-02T14:55:45Z David Kalnischkies david@kalnischkies.de 2022-08-31T19:49:33Z urn:sha1:3498fbedafbf30e5c91deeaefa6a60d1e387593a We needed a fake dpkg in our status file for dpkg --assert-multi-arch to work in the past, but recent dpkg versions do not require this anymore, so we can remove this somewhat surprising hackery in favour of better hidden hackery we only use if we work with an older dpkg (e.g. on current Debian stable). Temporarily Revert "2.3-only: Warn that the 0.1 protocol is deprecated" 2021-04-29T08:42:59Z Julian Andres Klode julian.klode@canonical.com 2021-04-29T08:42:59Z urn:sha1:b60cda7992d316123b036a4a0eb5f472d21e9cdd This reverts commit 64127478630b676838735b509fec5cdfa36874c8. test/json: Make the test hook more reliable 2021-04-23T13:20:45Z Julian Andres Klode julian.klode@canonical.com 2021-04-23T13:15:56Z urn:sha1:329f0cc3654f8d13bbaff71cc400cb9c4154ad53 Ugh, this was super flaky under -j 16 and -j 4, each behaving in slightly different ways. This seems to be stable now. No real bug though, all behaviors were OK. 2.3-only: Warn that the 0.1 protocol is deprecated 2021-04-23T10:26:46Z Julian Andres Klode julian.klode@canonical.com 2021-04-23T09:39:15Z urn:sha1:64127478630b676838735b509fec5cdfa36874c8 json: Hook protocol 0.2 (added upgrade,downgrade,reinstall modes) 2021-04-23T10:26:46Z Julian Andres Klode julian.klode@canonical.com 2021-04-23T09:37:28Z urn:sha1:80dd1447595c536d31912c486ac5e96f983ccc7a Hook protocol 0.2 makes the new fields we added mandatory, and replaces `install` mode with `upgrade`, `downgrade`, `reinstall` where appropriate. Hook negotiation is hacky, but it's the best we can do for now. Users are advised to upgrade to 0.2 json: Add `package-list` and `statistics` install hooks 2021-04-23T10:26:46Z Julian Andres Klode julian.klode@canonical.com 2021-04-23T08:36:18Z urn:sha1:dc11a4422d99cb49817c827b9f827617b5880600 This enables hooks to output additional information. upgrade: Add JSON hook support (AptCli::Hooks::Upgrade) 2021-04-23T10:26:46Z Julian Andres Klode julian.klode@canonical.com 2021-04-22T10:53:54Z urn:sha1:de86a4b076a37db2f70ee5fbfbb295cc71c344df json: Add origins fields to version 2021-04-23T10:26:46Z Julian Andres Klode julian.klode@canonical.com 2021-04-22T08:45:45Z urn:sha1:4b5215e8e2e31637cb0998ecb80d3c3146760579 Provide access to the origins of a package, such that tools can display information about them; for example, you can write a hook counting security upgrades. test: Set -e in our test hook 2021-04-23T10:25:40Z Julian Andres Klode julian.klode@canonical.com 2021-04-23T09:36:37Z urn:sha1:949f3821268943149ddc26d4eaee3bfbaa1255a9 Gbp-Dch: ignore Handle JSON hooks that just close the file/exit and fix some other errors 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