[Bug 1926150] Re: [SRU] Backport JSON hooks 0.2
Brian Murray
1926150 at bugs.launchpad.net
Thu Jun 17 18:05:53 UTC 2021
Hello Julian, or anyone else affected,
Accepted apt into hirsute-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.2.4ubuntu0.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: apt (Ubuntu Hirsute)
Status: New => Fix Committed
** Tags removed: verification-done
** Tags added: verification-needed verification-needed-hirsute
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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 Released
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:
Fix Committed
Status in apt source package in Impish:
Fix Released
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
More information about the foundations-bugs
mailing list