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? Regards, Tobias
OpenPGP_signature.asc
Description: OpenPGP digital signature
