And search for "libunwind" you will see entries for Bionic and Focal.
It is SRU policy to not release a package with current autopkgtest regressions.
Now, I have spent more time than I am willing to admit on trying to debug these failures, and I have also asked the Kernel Team, several which took a look, and some Launchpad admins, and we are still a bit stuck. The problem does not reproduce locally, only on Launchpad builders.
It rebuilds fine, but then runs into apt resolver trouble when running the kernel testsuite.
autopkgtest makes a dummy package, that contains the list of necessary dependencies to run the testsuite, dpkg -i to install the package, and then does an apt install -f to force dependency resolution. The dummy package is called autopkgtest-satdep.
Hi William,
I sincerely apologise for the delay.
Currently libunwind is stuck in -proposed due to benign autopkgtest regressions in the kernel packages.
If you go to the below page:
https:/ /people. canonical. com/~ubuntu- archive/ pending- sru.html
And search for "libunwind" you will see entries for Bionic and Focal.
It is SRU policy to not release a package with current autopkgtest regressions.
Now, I have spent more time than I am willing to admit on trying to debug these failures, and I have also asked the Kernel Team, several which took a look, and some Launchpad admins, and we are still a bit stuck. The problem does not reproduce locally, only on Launchpad builders.
For example, take the 4.15 Bionic Kernel:
https:/ /autopkgtest. ubuntu. com/packages/ l/linux/ bionic/ amd64
(it is a reverse dependency of libunwind, which is why it is selected for autopkgtest)
https:/ /autopkgtest. ubuntu. com/results/ autopkgtest- bionic/ bionic/ amd64/l/ linux/20230110_ 115614_ 09e98@/ log.gz
It rebuilds fine, but then runs into apt resolver trouble when running the kernel testsuite.
autopkgtest makes a dummy package, that contains the list of necessary dependencies to run the testsuite, dpkg -i to install the package, and then does an apt install -f to force dependency resolution. The dummy package is called autopkgtest-satdep.
https:/ /paste. ubuntu. com/p/Cszfkvy47 Z/
But it fails in strange ways, like not being able to select build-essential, even though it is already installed in the builder.
I am still trying to debug the root cause behind these autopkgtest regressions, which is why things have been delayed.
There is a provision in SRUs where they can be released as long as I can prove that the upload did not cause the regression:
https:/ /wiki.ubuntu. com/StableRelea seUpdates# Autopkgtest_ Regressions
In which case, I may as well invoke this clause, since I don't wish to keep you waiting any longer.
I will try and get this package released within the week.
Thanks,
Matthew