On 2026-01-31 22:37:21 +0100, Dr. Tobias Quathamer wrote:
> Package: release.debian.org
> User: [email protected]
> Usertags: transition
> X-Debbugs-Cc: [email protected]
> Severity: normal
> 
> Dear release team,
> 
> as you're probably aware, the default golang compiler version for Debian is
> determined with the golang-defaults package. Currently, the golang-defaults
> package points to golang 1.24.
> 
> Upstream has released golang-1.25 in August 2025, and the next version 1.26
> will most probably be released in about two weeks.
> 
> We'd like to switch the default golang version to the latest upstream
> (probably to 1.26, after it has been released).
> 
> In https://bugs.debian.org/1116589, Tianon and I had a short conversation
> about how to do this. Tianon said that he thinks this needs a transition, so
> I'm reaching out to you.
> 
> However, I'm a bit lost as to how a Ben file could be written. From my quick
> search with grep-dctrl, it seems that only the golang-compiler packages need
> to be rebuilt:
> 
> $ grep-dctrl -F Depends: "golang-go " -s Package Packages
> Package: golang
> Package: golang-any
> Package: golang-doc
> 
> $ grep-dctrl -F Depends: "golang-1" -s Package Packages
> Package: golang-1.24
> Package: golang-1.24-go
> Package: golang-1.25
> Package: golang-1.25-go
> Package: golang
> Package: golang-doc
> Package: golang-go
> Package: golang-src
> 
> Which does make sense, because the golang-*dev packages are constructed to
> include the source files, there is no binary library compiled.
> 
> 
> So, it would be great if you could give your perspective on this -- do we
> need a transition for a new golang compiler? If yes, how could we track the
> progress?

We do not need a transition for the switch to a new golang version as we
do not need any rebuilds. The reverse dependencies will get rebuilt
during one of the "outdated Built-Using" rebuild campaigns. However,
we'd appreciate a test rebuild of the golang ecosystem before switching
to the new version so that we have an idea of the impact on the archive.
In that sense we appreciate coordination with us before switching the
default in unstable.

Cheers
-- 
Sebastian Ramacher

Reply via email to