Your message dated Mon, 23 Mar 2026 22:41:47 +0100
with message-id <[email protected]>
and subject line Re: Bug#1126733: Current status of golang-1.26
has caused the Debian Bug report #1126733,
regarding transition: golang-1.26
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1126733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126733
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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?
Regards,
Tobias
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On 2026-03-21 15:27:37 +0100, Sebastian Ramacher wrote:
> On 2026-03-21 15:10:50 +0100, Dr. Tobias Quathamer wrote:
> > Am 01.03.26 um 19:48 schrieb Sebastian Ramacher:
> > >> So, if you don't have any objections, I plan to switch the default
> > >> golang compiler to 1.26 in the next few days.
> > >>
> > >> Thoughts?
> > >
> > > Go ahead.
> > >
> > > Cheers
> >
> > Hi Sebastian,
> >
> > almost all build failures have been resolved by now. There are two
> > packages left which show a regression in the autopkgtests.
> >
> > - golang-gonum-v1-gonum/0.15.1-1
> >
> > This one should be resolved tomorrow, when the new upload (0.15.1-3) has
> > migrated to testing.
> >
> > - victoriametrics/1.112.0+ds1-4
> >
> > That package is unfortunately not easy to solve. It builds fine with Go
> > 1.24 (in testing), but FTBFS with Go 1.26. I'm not able to fix this
> > myself. The package will get removed from testing in a week (on 28 March
> > due to #1129170).
> >
> > As I understand it, those two packages are the last ones holding off the
> > migration of golang-defaults to testing. So we could wait one week for
> > the automatic removal of victoriametrics from testing.
> >
> > However, I was wondering if it would be a valid solution to finish the
> > Golang 1.26 migration to testing if the release team would add a hint
> > for golang-defaults to ignore the failing autopkgtest for
> > victoriametrics? Or maybe even remove the package from testing a bit
> > earlier?
>
> Thanks for the update. I have added a hint to ignore these two
> autopkgtest regressions.
golang-defaults migrated. Closing
Cheers
--
Sebastian Ramacher
--- End Message ---
