Dear DebCamp participants and Go Team,

This is the 2nd daily report for the Debian Go Team Sprint at DebCamp26:
Major Transitioning to Module-Aware Builds in our new dh-golang
tooling.

We have made a lot of progress -

For Phase 1: Currently, there are 166 packages remaining in the queue
for participants to claim and work on.

We have 44 packages uploaded into unstable. And we have split the list
to handle in different cases. This includes 6 non-Go Team packages
that will likely require NMUs, 14 false-positives that do not actually
need an upload, and 3 packages without any reverse dependencies that
we can potentially look into removing from the archive. You can view
the full breakdown and claim your next package on our DevPackages wiki
page.

For Phase 2, we still have 502 packages waiting to be transitioned to
modern, module-aware builds in experimental.

As we run into more complex build issues, we will created a Migration
FAQ subpage under the DebianGoTeam wiki namespace. This page documents
recommended solutions for common blockers we are discovering, such as
handling legacy packages with misplaced go.mod files and implementing
compatibility symlinks using package-prefixed links files for
debhelper compatibility level 14.

We are actively looking for more helping hands to keep this sprint
going. If you are a Debian Developer with upload rights, whether you
are here at DebCamp or participating remotely, your help is incredibly
valuable.

Our daily stand-up meeting continues today at 3:00 PM in the hacklab,
where Andrew will be available to help onboard anyone who wants to get
started.

Happy hacking,
-Andrew

On Wed, Jul 15, 2026 at 7:20 PM 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

Reply via email to