On 02/03/2025 10:02, Nicolas Peugnet wrote:
On 02/03/2025 04:42, Guillem Jover wrote:
I wanted to look into this the other day, as I mentioned on IRC, but
run out of time, and I was not sure whether packaging a new upstream
release would be safe. Perhaps doing a targeted backport might be
safer (like was done for the -x-exp package), but didn't have time either
to look into what might fix that.
If you can look into this, that would be great, otherwise I'll try
during next week.
I will also try to see if it can be solved by backporting a patch as
easily as for the x-exp package, but I can not promise anything.
I bisected it and the first working commit is [2db563b], but it is too
difficult to backport on its own because it depends on other changes
elsewhere in the code.
Instead, I tried to import v0.25.0 which is the first release that
contains this commit, but there are a few failing tests. I will try to
fix these and propose an upload of this version.
[2db563b]
https://github.com/golang/tools/commit/2db563b1a3a2d4a703682ea03482335f63323a26
--
Nicolas Peugnet
