Hi Andrew, Thank you for the update. Unfortunately, I am not a Debian Developer, but I will see if I can help out in some other way and will keep you posted.
I hope you enjoy DebConf! Best regards, George On Thu, Jul 16, 2026, 15:04 Andrew Lee <[email protected]> wrote: > Hi George, > > Thank you for your message. This sprint is currently focused on DD who > have upload permission. > > We indeed wanted to implement automation where we can, but we have > discovered more complex issues in the phase 1 stage of the transition, > such as legacy path and import path mismatch, missing major version > paths, or broken go.mod file from upstream. > > I am actively documenting how to fix these newly discovered issues as > early as possible on our mailing list, and then update into wiki page. > > If any DD wants to help, feel free to automate any part of this > workflow or write helper scripts, and sign and upload the corrected > packages under your name. > > Best regards, > -Andrew > > On Thu, Jul 16, 2026 at 8:31 AM George Kesaev <[email protected]> wrote: > > > > Hi Debian Go Team, > > > > First of all, thank you for organizing the sprint and for publishing the > progress so openly. > > While reading through the Phase 1 and Phase 2 pages, I found myself > wondering how much of the transition has been (or could be) automated. > > > > Looking at the Phase 1 workflow, it seems like a significant portion of > the work might be amenable to automation, for example, rebuilding packages > with the new dh-golang, running the relevant validation steps, classifying > the outcome, and generating a report for maintainers. > > I imagine the final review and signed upload would naturally remain a > manual responsibility of a Debian Developer. > > > > I assume there are constraints I'm not aware of, so I'm curious: > > Have you already explored automating more of this workflow? > > If so, what turned out to be the main challenges or blockers? > > Is the bottleneck primarily the review/upload process, or are there many > packages that require manual intervention before they can even be built > successfully? > > > > I'm asking partly out of curiosity and partly because, at first glance, > rebuilding and validating a few hundred packages feels like something that > could be handled by a bot or CI pipeline, leaving developers to focus on > reviewing exceptions rather than performing the repetitive parts manually. > > > > If that's a misconception, I'd be very interested to understand why. > > > > > > Thanks again, and good luck with the sprint! > > Best, George > > > > On Wed, Jul 15, 2026, 22:10 Andrew Lee <[email protected]> wrote: > >> > >> Dear DebCamp participants and Go Team, > >> > >> This is the daily report for the Debian Go Team Sprint at DebCamp26: > >> Major Transitioning to Module-Aware Builds in our new dh-golang > >> tooling. > >> > >> Phase 1: We have successfully completed 12 packages yesterday, while > >> 220 packages remain pending for source upload to unstable. > >> Please check the document and progress in this wiki page: > >> https://wiki.debian.org/DebConf/26/Sprints/DebianGoTeam/DevPackages > >> > >> For Phase 2: We have created a new wiki page to coordinate our > >> efforts, which can be found at: > >> https://wiki.debian.org/DebConf/26/Sprints/DebianGoTeam/GoModBuilds > >> > >> On phase 2, we have finished packaging two packages that builds with > >> the new dh-golang version 1.66 in experimental. These have already > >> been uploaded to experimental and were built successfully under the > >> modern, module-aware builds. However, 502 packages listed in phase 2 > >> page are still waiting to be transitioned. > >> > >> We are actively looking for helping hands to move this work forward. > >> If you are a Debian Developer with upload rights, whether you are > >> attending DebCamp in person or participating remotely, your help would > >> be incredibly valuable in making this sprint a success. > >> > >> To help everyone coordinate, the Debian Go Team Sprint is starting a > >> daily stand-up meeting at 3:00 PM in the hacklab. Andrew will be > >> present at these sessions to help onboard anyone who wants to help in > >> the sprint and get started. > >> > >> Happy hacking, > >> -Andrew > >> > >> On Tue, Jul 14, 2026 at 2:03 AM Andrew Lee <[email protected]> wrote: > >> > > >> > Dear DebCamp participants and Go Team, > >> > > >> > I have been preparing a wiki page for the Go Team Sprint at DebCamp26: > >> > > >> > https://wiki.debian.org/DebConf/26/Sprints/DebianGoTeam > >> > > >> > Everyone is welcome to join our efforts onsite or remote. We are now > >> > officially starting phase one, which is ensuring that all existing > >> > golang-related -dev packages ship their respective go.mod files. > >> > Getting this completed is a critical prerequisite to make the archive > >> > ready for modern Module-Aware Builds. > >> > > >> > Please visit the wiki page to find instructions on how to verify > >> > packages, claim tasks, and help with source uploads. > >> > > >> > Happy hacking! > >> > -Andrew > >> > > >> > On Fri, Jul 10, 2026 at 4:45 PM Andrew Lee <[email protected]> wrote: > >> > > > >> > > Dear Go Team and DebConf participates, > >> > > > >> > > Since I met Toddy during mini DebConf Hamburg.Toddy started his hard > >> > > work in making this major Go Module-Aware Builds transition > possible. > >> > > He just uploaded dh-golang with `GO111MODULE=on` enabled by default > in > >> > > Experimental. This unlocked modern Module-Aware Builds for the > entire > >> > > Debian Go ecosystem. > >> > > > >> > > Previously, building Go packages under the old `GO111MODULE=off` > >> > > introduced several known issues, including broken dependency > >> > > resolution and wrong runtime that make a lot of tests failed and > also > >> > > introduced insecured behaviors. > >> > > > >> > > While Toddy’s hard work, finally we can move away from the legacy > >> > > limitations. And now we are going to have a major modernizing > >> > > transition process for Go ecosystem in Debian. Due to Go packages in > >> > > archive were builds with the old `GO111MODULE=off`. We expected we > >> > > will immediately found a lot of build failures across various > packages > >> > > and architectures that only builds on legacy behaviors during this > >> > > transition. > >> > > > >> > > So I plan to host this Go Team Sprint during DebCamp next week. This > >> > > will be a week-long DebCamp Sprint dedicated for auditing, patching, > >> > > and modernizing our Go Ecosystem with new dh-golang in Debian. > >> > > > >> > > During this Sprint, we will focus on: > >> > > - Start to port high priority packages into Experimental with new > dh-golang. > >> > > - Find out the packages currently failing to build with > GO111MODULE=on > >> > > and file bug reports. > >> > > - Collecting go import path mappings to the actual path packaged in > >> > > Debian packages.(Maybe these would be useful to impletement as an > >> > > auto-redirection inside dh-golang itself later) > >> > > - I will be personal onsite during DebCamp to help on boarding > >> > > contributors who want to assist with the transition. > >> > > > >> > > Anyone who interested to help please join us. Anyone who would like > to > >> > > join remotely are also welcome. > >> > > > >> > > Happy hacking, > >> > > -- > >> > > -Andrew > >> > > >> > > >> > > >> > -- > >> > -Andrew > >> > >> > >> > >> -- > >> -Andrew > >> > > > -- > -Andrew >
