<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test, branch 2.3.2</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=2.3.2</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=2.3.2'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2021-04-23T15:13:55Z</updated>
<entry>
<title>Support deconfiguring Essential packages</title>
<updated>2021-04-23T15:13:55Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2021-04-23T15:06:40Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=a7f2152f0ce46322791f0574d76aadfdfbde6bec'/>
<id>urn:sha1:a7f2152f0ce46322791f0574d76aadfdfbde6bec</id>
<content type='text'>
dpkg 1.20.8 also made --force-remove-essential optional for
deconfiguring essential packages, so let's do this.

Also extend the test case to make sure we actuall pass
auto-deconfigure and do not make any --remove calls, or
pass --force-remove to dpkg.
</content>
</entry>
<entry>
<title>test/json: Make the test hook more reliable</title>
<updated>2021-04-23T13:20:45Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2021-04-23T13:15:56Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=329f0cc3654f8d13bbaff71cc400cb9c4154ad53'/>
<id>urn:sha1:329f0cc3654f8d13bbaff71cc400cb9c4154ad53</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>2.3-only: Warn that the 0.1 protocol is deprecated</title>
<updated>2021-04-23T10:26:46Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2021-04-23T09:39:15Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=64127478630b676838735b509fec5cdfa36874c8'/>
<id>urn:sha1:64127478630b676838735b509fec5cdfa36874c8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>json: Hook protocol 0.2 (added upgrade,downgrade,reinstall modes)</title>
<updated>2021-04-23T10:26:46Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2021-04-23T09:37:28Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=80dd1447595c536d31912c486ac5e96f983ccc7a'/>
<id>urn:sha1:80dd1447595c536d31912c486ac5e96f983ccc7a</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>json: Add `package-list` and `statistics` install hooks</title>
<updated>2021-04-23T10:26:46Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2021-04-23T08:36:18Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=dc11a4422d99cb49817c827b9f827617b5880600'/>
<id>urn:sha1:dc11a4422d99cb49817c827b9f827617b5880600</id>
<content type='text'>
This enables hooks to output additional information.
</content>
</entry>
<entry>
<title>upgrade: Add JSON hook support (AptCli::Hooks::Upgrade)</title>
<updated>2021-04-23T10:26:46Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2021-04-22T10:53:54Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=de86a4b076a37db2f70ee5fbfbb295cc71c344df'/>
<id>urn:sha1:de86a4b076a37db2f70ee5fbfbb295cc71c344df</id>
<content type='text'>
</content>
</entry>
<entry>
<title>json: Add origins fields to version</title>
<updated>2021-04-23T10:26:46Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2021-04-22T08:45:45Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4b5215e8e2e31637cb0998ecb80d3c3146760579'/>
<id>urn:sha1:4b5215e8e2e31637cb0998ecb80d3c3146760579</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>test: Set -e in our test hook</title>
<updated>2021-04-23T10:25:40Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2021-04-23T09:36:37Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=949f3821268943149ddc26d4eaee3bfbaa1255a9'/>
<id>urn:sha1:949f3821268943149ddc26d4eaee3bfbaa1255a9</id>
<content type='text'>
Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>json: Encode NULL strings as null</title>
<updated>2021-04-23T10:25:40Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2021-04-21T10:21:41Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=b5211b9b213273c642a790ae3c3f3bbe1a4cf51e'/>
<id>urn:sha1:b5211b9b213273c642a790ae3c3f3bbe1a4cf51e</id>
<content type='text'>
This is the only nullable thing we have here.
</content>
</entry>
<entry>
<title>json: Actually pop states</title>
<updated>2021-04-23T10:25:40Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2021-04-21T10:17:55Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=09e3c0c855e339216784a1d43715c3ae2d79ec23'/>
<id>urn:sha1:09e3c0c855e339216784a1d43715c3ae2d79ec23</id>
<content type='text'>
The JSON encoder only looked at the top state, but did not
pop it, so if we nested objects, we got stuck in whatever
the last state we pushed aside was, so in our example, we
wrongly get a comma inserted _after_ key "b":

{"a":[{}],
 "b":,[{}]
}
</content>
</entry>
</feed>
