This bug was fixed in the package apt - 1.2.35
---------------
apt (1.2.35) xenial; urgency=medium
* Backport JSON hooks, version 0.2, to xenial (LP: #1926150). The JSON code
files are identical to that of 2.3.2, only the integration and test cases
needed minor adjustment to behave correctly, especially:
- In private-install.cc, exit before showing the list of packages to
upgrade/install/etc, in case an error is already set. This moves the
behavior closer to bionic.
* Backport zstd support for Launchpad zstd enablement (LP: #1926437)
* Fix indendation of changelog message in 1.2.34 changelog.
* Bug fixes needed for JSON hooks:
- private-install: Handle existing errors before showing lists
- Avoid duplicated error in `apt search`
* Bug fixes affecting CI / autopkgtest only:
- prepare-release: Ignore alternative build dependencies
- tests: Do not expect requested-by if sudo was invoked by root
- tests: Export TZ=UTC to work around test failures on non-UTC hosts
- tests: avoid time-dependent rebuild of caches
-- Julian Andres Klode <juli...@ubuntu.com> Wed, 28 Apr 2021 14:55:54
+0200
** Changed in: apt (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1926150
Title:
[SRU] Backport JSON hooks 0.2
Status in apt package in Ubuntu:
Fix Committed
Status in apt source package in Xenial:
Fix Released
Status in apt source package in Bionic:
New
Status in apt source package in Focal:
New
Status in apt source package in Hirsute:
New
Status in apt source package in Impish:
Fix Committed
Bug description:
[Impact]
We want to be able to use JSON hooks 0.2 in xenial and later releases to
display messages to users during dist-upgrade.
For xenial, we backport the JSON hook support in its entirety, whereas
for later releases, we only need to cherry-pick bugfixes and the v0.2
improvements.
[Test plan]
We have included unit and integration tests for the new JSON code to test the
writer and prevent regressions in future changes. Regressions in other parts of
the code should be caught by the test suite.
[Where problems could occur]
There may be bugs in the JSON code (apt-private/private-json-hooks.*) and in
the integration thereof. The JSON hook code is identical to 2.3.2, whereas the
integration code needed slight adjustments.
The integration changes are limited to adding the hooks, and (for
xenial, already in later releases) collecting all unknown package
names. We believe the regression potential of these changes to be
fairly limited.
However, errors in JSON hooks are fatal, so once JSON hooks are
running, they can cause apt to fail, which has to be kept in mind.
Existing JSON hooks might not expect the new notifications, and break,
but we are only aware of the snapd hook and it ignores any unknown
notifications, so that should not pose a problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926150/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
