Foundations Team Updates - Thursday 2024/12/19

Previous status: Foundations Team Updates - Thursday 2024/12/12

Distro

Making openssl 3.4.0 migrate, i.e. adapt users to its behaviour changes:

Currently preparing another openssl upload to add the error message from plucky-lp-2066990 : lp:~adrien/ubuntu/+source/openssl : Git : Code : openssl package : Ubuntu and to work around the m2crypto ftbfs.

KDE/QEMU

  • libvirt’s API returned wrong firmware information (LP #2091573)
  • Add missing pc-bios/descriptors/60-edk2-riscv64.json to upstream QEMU
  • Add our replacement file to Debian’s edk2-2024.11-2 via MR in salsa.debian.org

Cookbook for RISC-V image creation

  • Add further sections

Silicon Vendor Collaboration

Launchpad

  • Analyze issue in booting RISC-V builder images

Greenhouse

  • Evaluate submissions

distro

  • +1 maintenance this week (report going out tomorrow or later if list moderation takes longer).

dotnet

distro

  • Uploaded a quick systemd SRU for Jammy
  • Working on getting systemd v257 migrated in plucky
  • SRU training

misc

  • Conducted some interviews/other hiring

Packaged a bunch of dependencies for Picamera2

[needs-packaging]

Built picamera2, testing examples given on https://datasheets.raspberrypi.com/camera/picamera2-manual.pdf

Misc

Plucky

  • Reviewed and sponsored raspi-utils packaging for @r41k0u (LP: #2046250)
  • Reviewed rpicam-apps packaging for @r41k0u (LP: #2020101)
  • Still working on “cleaner” flash-kernel merge
    • About half the delta (in line count) is now gone
    • Off-list replies to the ubuntu-devel thread indicate only Wandboard Quad is still in use
    • That board will still have a db entry in the revised version, but will just be derived from Debian
  • Filed bug to add Pi 500 entry (LP: #2092216), speaking of which…

Oracular

  • Pi 500 compatibility
    • Missing entry for flash-kernel prevents completion (which we knew; this couldn’t be included as the board wasn’t public at release)
    • Unfortunately, the cunning plan to patch it in via a cloud-init config patch won’t work because cloud-init doesn’t run on first boot
    • Writing a new patch for the release notes instead…

General

  • Merge request for addition of Pi 500 to the imager JSON was merged
    • Pinged release management to update changelogs.u.c
  • Merged fix for CI in meta-release
  • Pi meetings
  • Take home tests

Short report. I probably missed documenting parts of what I did.

Distro

proposed migration

patch pilot

My patch pilot report: Patch Pilot Hand-off 25.04 - #23 by bdrung

Rust

Distro

apt

After being distracted by a python-apt bug triggered in Launchpad I went on wild goose chases and ended up implementing APT stuff

  • Automatic paging of apt output, like git does
  • An sqv verification backend
  • Actually rebuilt sqv with OpenSSL and massive size optimizations in plucky now, it’s now 1.9 MB.
  • Played around with Rust vendoring for sqv.
  • Almost done it seems switching from GnuTLS for TLS + gcrypt for hashes to OpenSSL. We also have a pure GnuTLS option now, without gcrypt. This started because I found out that a minimal docker container only pulls in libgcrypt due to apt once gpgv is replaced with sqv. Then I spent 6 hours from 6pm to midnight yesterday hacking up a TLS backend lol.

misc

I had a meeting about boot CAs which was bit premature.

My patch to Sequoia got merged and is part of the sq 1.0 release, hooray.

autopkgtest-cloud

  • Lots of retries of tempfailing tests
  • Fixed a bug in the amqp-status-collector
  • Working on MP moving from mojo to terraform

iso testing

  • Lots of work on windows installer automation (for testing installs alongside dual boot)
  • More Greenhouse activity than usual
  • Did some preliminary triage of the glibc stable branch fixes
    • That actually sucked me into the depth of the Python email module, because my MUA was unhappy
  • @waveform is a CoreDave now!
  • Continued reading up on some of the archive weirdness.

autopkgtest-cloud

  • Implemented support for riscv64 runners in the infra: MP.
    This is now deployed, but keep in mind that runners are still in emulation, and there are very few of them, so don’t expect good performances, but at least you can play with that (mostly on Noble, the rest is still kinda borken) :tada:

error-tracker

  • Making progress on the new retracer environment:
    • Still porting the code to run on Noble. This is now considered finished and merged.
    • Remains finishing building a new charm for proper deployment in production.

Plucky

MoM

  • Kicked it a few times
  • Got tired of that, so I cowboyed a few timeout 1h cmd... in the cron job entrypoint, to see if it helps.

misc

  • Hiring