<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Rescue Forky: We have Go Back to 2011. Building Go Like It's 2011 is Broken.</title>
        <link>https://peertube.debian.social/videos/watch/fcff6fee-7ccb-4556-b595-6503531f7939</link>
        <description>by Andrew Lee (李健秋) At: MiniDebConf Hamburg 2026 https://hamburg2026.mini.debconf.org/talks/28-rescue-forky-we-have-go-back-to-2011-building-go-like-its-2011-is-broken/ 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: Seminarroom Scheduled start: 2026-05-09 13:00:00+02:00</description>
        <lastBuildDate>Sun, 30 Aug 2026 09:46:03 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>PeerTube - https://peertube.debian.social</generator>
        <image>
            <title>Rescue Forky: We have Go Back to 2011. Building Go Like It's 2011 is Broken.</title>
            <url>https://peertube.debian.social/client/assets/images/icons/icon-96x96.png</url>
            <link>https://peertube.debian.social/videos/watch/fcff6fee-7ccb-4556-b595-6503531f7939</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=fcff6fee-7ccb-4556-b595-6503531f7939" rel="self" type="application/rss+xml"/>
    </channel>
</rss>