<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Modernizing Debian's Go Ecosystem: From 2011 Time-Travel to Module-Aware Builds</title>
        <link>https://peertube.debian.social/videos/watch/7ef9030a-a498-41ef-8883-9b703664c9d3</link>
        <description>by Andrew Lee (李健秋) At: MiniDebConf Winterthur 2026 https://ch2026.mini.debconf.org/talks/7-modernizing-debians-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? Room: Campo Foyez (Main Track) Scheduled start: 2026-08-30 15:50:00+02:00</description>
        <lastBuildDate>Fri, 04 Sep 2026 21:25:52 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>PeerTube - https://peertube.debian.social</generator>
        <image>
            <title>Modernizing Debian's Go Ecosystem: From 2011 Time-Travel to Module-Aware Builds</title>
            <url>https://peertube.debian.social/client/assets/images/icons/icon-96x96.png</url>
            <link>https://peertube.debian.social/videos/watch/7ef9030a-a498-41ef-8883-9b703664c9d3</link>
        </image>
        <copyright>All rights reserved, unless otherwise specified in the terms specified at https://peertube.debian.social/about and potential licenses granted by each content's rightholder.</copyright>
        <atom:link href="https://peertube.debian.social/feeds/video-comments.xml?videoId=7ef9030a-a498-41ef-8883-9b703664c9d3" rel="self" type="application/rss+xml"/>
    </channel>
</rss>