Foundations Team Updates - 2026-04-30

Project Discussion Foundations
1

Hello everybody,

It’s time for a weekly update from Foundations :sparkles:

Courtesy ping:

Please, post your updates. Thanks!

2

Resolute

  • Triaged and investigated release upgrader bugs/problems
  • Finished initial packaging for upki (LP: #2139297)
3

Toolchains

  • LP: #2150160: Backport rustc-1.91 to Questing while testing new self-bootstrap method
  • Following up with LP: #2100266 SRU

Miscellaneous

  • Spec for modernized reverse dependency checking
  • Documenting and testing RVA23 rollback for backports
4

Toolchains

  • Published blog post about cargo-auditable!
  • Get a head start on Stonking tasks – more idiomatic C-A enablement and rebasing d/b/cargo from Debian

Misc

  • Madrid sprint prep!
  • Written interview grading
5

Java

  • Created openjdk-{17,21,25}-crac upstream releases with the April 2026 security updates.
  • Worked on addressing Security reviews on OpenJDK OpenSSL FIPS packages for Ubuntu 22.04 Pro.
  • Adoptium Workgroup meeting

Toolchains

  • Review of Zig docs.
  • Spent time learning about conda from @vmpyr

Misc

  • Attended the GIDS 2026 conference.
  • Sprint prep.
6

openjdk:

  • preparing April security update

Misc:

  • Sprint prep
7

Mostly working on archive opening, as well as grooming my backlog after the Resolute release and in preparation for the sprint to come.

8

Posting rather late, partly due to trouble doing so last week!

Stonking

Resolute

  • Ran through a whole bunch of old flash-kernel bugs looking for common EEPROM issues:
  • LP: #2150321 added some further instructions, but I think this one is just a misunderstanding of how dracut and flash-kernel interact
  • LP: #2138620 marked as fix released as I’d forgotten to mark this one on upload
  • There have been several bug reports involving upgrades not installing piboot-try
    • Worked through a whole bunch of upgrade scenarios from questing->resolute and noble->resolute
    • Couldn’t replicate the precise conditions, but did encounter several upgrade failures where u-r-u would simply fail to calculate the upgrade
    • Suspect several of the reports are trying a manual dist-upgrade
    • Still, quirks need to be added to u-r-u to force piboot-try into being installed (in a similar vein to the way dracut is forced on the Pi)

General