My first +1 week with upload rights, I actually didn’t upload many things, but the week was packed with two very interesting 
investigations.
Still, I want to note that upload rights were useful more than once not to upload, but to retry build failures when appropriate, to resolve the go mess.
Work-needed items
- The go build-deps dependency hell still isn’t completely fixed. Look at LP: #2155158 if you’re interested.
- Similarly, if you want to work on the Launchpad builder, you can have a look at LP: #2155652.
Full logs
ubuntu-release-upgrade:
- Both
stonkingand the ongoingresoluteSRU were stuck on failing autopkgtest due topycodestylebeing unhappy. @bamf0 quickly fixed that forstonking, but I’ve backported that and re-uploaded the SRU, then baby-sitted the autopkgtests throughout the week. - This sparked this small QoL MP to catch such issues earlier: https://code.launchpad.net/~skia/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/505775
- I also helped a bit around the ongoing SRU after the autopkgtest got fixed.
ubuntu-release KPIs
- I quickly sent a small fix to get back the autopkgtest queues on the release KPI: autopkgtest: don't rely on now broken endpoint · ubuntu/ubuntu-release-metrics@6cfe7a9 · GitHub
llvm-toolchain-22
- I reviewed and sponsored this pending merge for @karljs: https://code.launchpad.net/~karljs/ubuntu/+source/llvm-toolchain-22/+git/llvm-toolchain-22/+merge/504809
apport
- I reviewed some PR on Apport for @bdrung: apt_dpkg: fix GDB command for amd64 sandbox on non-amd64 by bdrung · Pull Request #600 · canonical/apport · GitHub
rclone build-deps go dependency hell
- I had a blast investigating some go build dependency hell with @whershberger.
Just look at the bug, it’s very funny: Bug #2155158 “FTBFS hell after Debian import resumed” : Bugs : golang-google-grpc package : Ubuntu
util-linux
- On that, it all started with a merge to test the new
git ubuntu deltarebase autofeature from @jj: Bug #2153369 “Merge util-linux from Debian for stonking cycle” : Bugs : util-linux package : Ubuntu - Then the merge FTBFS on stonking in the LP PPA, but somehow passed, or failed very differently locally, depending on which laptop I was working on (arm64 or amd64).
- After a long and also very funny investigation, that led me to opening a bug against buildd: Bug #2155652 “expose a root mount point to chroots” : Bugs : launchpad-buildd
sbuild
- The previous investigation sparked me to dig into
sbuild, and I opened a discussion around easy inclusion ofauto-apt-proxy: https://salsa.debian.org/debian/sbuild/-/merge_requests/236