modified autopkgtest-web to display “exit code” instead of just “code” which is cryptic
updated never_run with assimp/armhf/jammy, apport/armhf/jammy
manual cleanup of long running armhf tests
ISO Tracker
merged the 1753_QEMU_riscv64_install manual test case for @xypron
updated the ISO Tracker with the above test case and made the test case available for Subquity Live Server (riscv64)
Ubuntu
updated Jammy release notes with issues encountered during the release upgrade process * reviewed and merged @paelzer’s MP to make the release upgrade check less expensive fixing LP: #1893716
uploaded ubuntu-release-upgrader with the above fix, deb2snap changes for Ubuntu Studio and an improved apport package hook (gathers journalctl and a list of files in /var/crash)
NBS
We are two weeks out from release, which means it’s important to clean up all the remaining binaries in the release pocket that are no longer built from source. This generally involves looking at the reverse-dependencies listed on https://people.canonical.com/~ubuntu-archive/nbs.html and resolving why they have not been rebuilt to drop dependencies.
mozjs78: noticed lto-wrapper listed in the output of the builds on failing architectures, then noticed the architectures where it was built successfully are the archs where we don’t use LTO. Disabled use of LTO in the package, then also fix the test target to invoke the js interpreter from the binary install directory instead of from the source directory, which for some reason is not marked executable - we can ignore this instead of debugging the upstream build system. This unblocks removal of libicu67.
tracked down the sra-sdk autopkgtest failure with the new ncbi-vdb to be a misbuild of sra-sdk itself with LTO, not a bug in ncbi-vdb; rebuilt sra-sdk without LTO and both packages migrated, unblocking removal of mbedtls NBS binaries
Finally took a look at the cluster of blocked D library packages, to notice that 3 of the 4 were candidates but britney wasn’t working out on its own how to migrate them together. Added a hint for this and the 3 migrated. Then removed diet-ng, which is also FTBFS in Debian and not in testing. This let us remove the old libphobos binaries.
As of Tuesday, we have zero NBS binaries in the release pocket for jammy!
Proposed-migration
Looked at gyoto/ppc64el, one of 3 packages which block removal of python3.9. Failing to build because of mutually-incompatible options being passed to g++ when LTO mode is on; but these flags don’t come from the build of the gyoto package, instead they are hard-coded into the lorene library, causing the check-lorene test to fail. Worked on unpicking this, so that impossible options were not being inherited from liblorene.
skimming the bottom of update_excuses, noticed that two related packages, libdata-sah-normalize-perl and libperinci-sub-normalize-perl, had been blocked in -proposed for 170 days due to one of the packages failing its autopkgtests; but somehow no one had ever tried triggering the autopkgtest with both packages together? (+1 maintenance?) Did so now, and the packages migrated successfully.
Archive admin
it was pointed out that mozjs78 previously built on i386 but was now not being scheduled there. This led to a round of cleanup of old i386 binaries in the release pocket
got a request to clean up particular NBS binaries in the -proposed pocket, so went through update_excuses again and removed all NBS binaries I found; this should let around ~14 packages (mostly kernels) migrate
misc push-button NEW processing of packages synced from Debian
discovered in the process that the libpth20 i386 binary went missing in jammy by my hand despite having reverse-dependencies in the archive that should have prevented it being picked up as a candidate for removal. Best guess is that there was a window when there were not any reverse-dependencies in the jammy release pocket, and therefore it got removed. Binary is back now, though, and the count of uninstallables on i386 is now zero, which it hadn’t been for a few cycles.
pestered fellow AAs to clean up their manual whitelist entries for packages on i386 (which would ideally only be used during bootstrapping, with things eventually moving to the seed).
started trimming down the priority mismatches for jammy release. These are less important in the past now that we don’t use debian-installer which relies on their correctness, but it is a good review to make sure our base system is not being unexpectedly bloated.
re-running process-removals for all packages removed from Debian unstable since the start of 2021, picking up a few more removals of obsolete packages that are no longer blocked from removal in Ubuntu due to reverse-dependencies.
fixed remaining references to exfat-utils so it could be removed cleanly.
Noticed via an open ubuntu-archive bug that numba made it back into the archive, so resurrected all of the source packages to -proposed that were removed because of lack of numba. One or more of these probably needs follow-up to be migratable to the release pocket, but now it’s on the +1 maintenance todo list instead of being lost in the ether.
along the way, noticed that some packages were stuck in -proposed due to spurious autopkgtest "regressions’ reported on i386. Did a sweep of these, got 8 packages to migrate out of -proposed.
Release Team
Spent a little time cleaning up stale hints files in proposed-migration. We are now down to only 72 hints total in the devel release, and no force-reset-test hints left, so I will look at deprecating this delta from Debian.
SRU
Discussion with enr0n, jawn-smith about use of britney hints vs baseline autopkgtest retesting. Rejected an MP for a hint because the retest proved that snapd autopkgtests had regressed in the impish-updates pocket, so no manual override was required; thus unblocking a systemd SRU.
Misc
Discussion about systemd-oomd behavior regressing experience in certain situations where memory pressure was not causing issues, and possible reversion for jammy release
Technical board meeting with discussion about third-party-archive policies for flavors. Ran into an issue (RT#149245 filed by @sil2100) that prevents logins to wiki.ubuntu.com.
Went through the process of booking travel to attend the roadmap sprint in Copenhagen in the beginning of May, first trip in 2 years so having to jog my memory about how to do things!
PR: 1255 - Fix interation between early-commands and the location of the autoinstall file, as documented. Pending a review of autoinstall behavior after a snap refresh.
jammy stable: Merge PR: 1253, get RISC-V build enabled.
ubuntu-desktop-installer
PR: 749 - Add a command line arg in call to Subiquity to continue using os-prober.
curtin
MP: 417829 - Finish draft of partition resizing. Remove some redundant repartitioning. Add some safety checks. Improve handling of the partition device path. Handle resizing on both gpt and msdos partition tables.
casper
Discussion with @xypron about how to detect the installer image and to be able to output an ‘ejection’ message for that case
proposed-migration - amd64 systemd vs cron passes test on retry (we might want to go fix LP: #1944712)
Hoping to get some kind of ACK on the direction of the patch from upstream, in which case I will bring the patch into jammy. Edit: patch was accepted upstream.
Prepped a patch for LP 1926860 pending discussion with the team
started investigating LP: 1968146 - unattended-upgrade cancellation issues. Different behaviors depending on the version of Ubuntu / version of Subiquity. But generally, no real success in cancelling updates.
created and started investigating LP 1968161. Block device probing screen sometimes not refreshing automatically.
ltrace: submitted a patch to fix FTBFS on ppc64el. Requested changes to work on.
started working on focal SRU for livepatch vs MOTD alignment
Part of prep-work: reviewing the third-party software requirements document from Robie
Helping with some seed reviews and merges
Investigating issues with the RISC-V live-server daily image builds not happening
Roadmap considerations
ubuntu-image
Continuously working on the ubuntu-image classic redesign spec
Revisited the image definition file format, making it a bit structured as per propositions from the CPC team
Switching approach to using a gadget url instead of a deb package
Documenting additional customization functions
Discussions with John (CPC) and William about our current approach and the needs for cloud images
Discussions with Steve on the spec as it is unfolding
Started cleaning up changes that were needed to build raw-partitioned images for our RISC-V installers via debian-cd
ubuntu-cdimage + isotracker
Additional small fixes to WSL image build iso-tracker notification scripting
Finally confirmed that the changes work fully as expected
Preparing credentials for WSL remote rebuilds from cdimage/iso-tracker
Tweaked description of our RISC-V live-installer images
Still waiting for the wiki page entry for how to properly prepare the images to be used on real hardware, which is blocked on wiki.ubuntu.com login issues
Tweaked ppc64el image descriptions per the recent POWER9 baseline bump
Release
Daily 22.04 queue reviews
Creating tooling for generating Jira cards for milestone work tracking for the release team, using milestone templates that are easily definable via a .yaml file
Pushed to lp:ubuntu-archive-tools (probably better place needed)
Have some ideas on how to use this more (for syncing with the wiki pages for instance!)
Created a template for final release
Using above script, created Jira cards for 22.04 final
Started working on initial tasks for the 22.04 nearing Final release
Misc work on the RISC-V live-installer images
Ubuntu Core
Signing latest jammy grub2 binaries for UC22 usage, copying to staging PPA and building new core22 snap
Reviewing new non-dangerous model assertions for UC22
Discussing steps forward for an urgent core20 fix for a customer