Andrew Lee (李健秋)

Modernizing Debian's Go Ecosystem: From 2011 Time-Travel to Module-Aware Builds

Hidden Injections, 404 Errors, and the Path to Modern Builds.

When a modern Go package is added to Debian, it should just work. But what if a perfectly compiled binary fails at runtime with a “404 Not Found” error that nobody can explain?

After our investigation: We found Debian’s Go infrastructure is trapped Bookworm and Trixie in a time machine in 2011. How can we rescue “Forky” (Debian 14) from the past and bring our Go builds back to the present and ready for the future?