The libunwind SRU for Bionic and Focal have now been released to -updates. Their versions are 1.2.1-8ubuntu0.1 for Bionic, and 1.2.1-9ubuntu0.1 for Focal.
I just want to apologise for the significant delay in getting libunwind released. It really was a exceptional amount of time, and I'm sorry it took so long.
Since I wrote to you last, I root caused the issue and worked with Paride to resolve the regression that was introduced into autopkgtest itself.
The bug in autopkgtest was quite obscure, and it required the following to occur:
1. an all-proposed build (--apt-pocket=proposed with no package pinning)
2. multiple tests defined in d/t/control
3. the tests do not allow reusing the same testbed system
All these conditions were present in the kernel autopkgtests, and the result was that the change to allow apt pinning for -proposed caused _create_apt_pinning_for_packages() to be called incorrectly and it set a pinning for the -release pocket at 990, over -updates and -proposed, at 500 each, which meant that -release was being favoured over -proposed, and it caused all sorts of apt resolve issues.
The fix is in place on the Launchpad build infrastructure, and we re-ran all autopkgtests around libunwind and its reverse dependencies, and they all passed, leading us clear to release libunwind to -updates.
Again, I sincerely apologise for keeping you waiting for so long, and I thank you for your patience and understanding while I debugged autopkgtest.
Hi William.
The libunwind SRU for Bionic and Focal have now been released to -updates. Their versions are 1.2.1-8ubuntu0.1 for Bionic, and 1.2.1-9ubuntu0.1 for Focal.
I just want to apologise for the significant delay in getting libunwind released. It really was a exceptional amount of time, and I'm sorry it took so long.
Since I wrote to you last, I root caused the issue and worked with Paride to resolve the regression that was introduced into autopkgtest itself.
The bug in autopkgtest was quite obscure, and it required the following to occur:
1. an all-proposed build (--apt- pocket= proposed with no package pinning)
2. multiple tests defined in d/t/control
3. the tests do not allow reusing the same testbed system
All these conditions were present in the kernel autopkgtests, and the result was that the change to allow apt pinning for -proposed caused _create_ apt_pinning_ for_packages( ) to be called incorrectly and it set a pinning for the -release pocket at 990, over -updates and -proposed, at 500 each, which meant that -release was being favoured over -proposed, and it caused all sorts of apt resolve issues.
The issue was introduced in:
commit 1c018c78de9d942 1c0c358c900a37e 545334cc66 /salsa. debian. org/ci- team/autopkgtes t/-/commit/ 1c018c78de9d942 1c0c358c900a37e 545334cc66
From: Paride Legovini <email address hidden>
Date: Thu, 15 Dec 2022 21:47:02 +0100
Subject: Pin pockets with Pin-Priority: 500
Link: https:/
The full explanation of the autopkgtest issues can be found in the below emails:
From myself to Paride /paste. ubuntu. com/p/44yFTBNBH h/
https:/
From Paride to myself: /paste. ubuntu. com/p/jtt5wh6BB 2/
https:/
Paride's merge request; /salsa. debian. org/ci- team/autopkgtes t/-/merge_ requests/ 218
https:/
Final fix commit: /salsa. debian. org/ci- team/autopkgtes t/-/commit/ 94b9bb8db305112 3d7b29a78804203 40a76c7b7e
https:/
The fix is in place on the Launchpad build infrastructure, and we re-ran all autopkgtests around libunwind and its reverse dependencies, and they all passed, leading us clear to release libunwind to -updates.
Again, I sincerely apologise for keeping you waiting for so long, and I thank you for your patience and understanding while I debugged autopkgtest.
Thanks,
Matthew