<?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 Time Travel to 2011. Building Go Like It's 2011 is Broken.</title>
        <link>https://peertube.debian.social/videos/watch/4b65caf7-88fd-465c-bf1e-c73e6eb8e669</link>
        <description>by Andrew Lee At: DebConf26 https://debconf26.debconf.org/talks/87-rescue-forky-we-have-go-time-travel-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 with a "404 Not Found" error that nobody can explain? After our investigation: We found Debian’s Go infrastructure is trapped Bookworm, Trixie and also Forky in Time Travel to 2011. Can we rescue "Forky" (Debian 14) Go back to the present and to be ready for the future? Room: Aula Magna - FADU Scheduled start: 2026-07-25 11:30:00-03:00</description>
        <lastBuildDate>Mon, 31 Aug 2026 09:29:45 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 Time Travel 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/4b65caf7-88fd-465c-bf1e-c73e6eb8e669</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=4b65caf7-88fd-465c-bf1e-c73e6eb8e669" rel="self" type="application/rss+xml"/>
    </channel>
</rss>