On 10/5/26 16:23, Juan Manuel Méndez Rey wrote:
This FTBFS is the otel/log API change from otel 1.45 (log.Value / log.KeyValue
moved to attribute.*), which siso 1.5.22 still used in o11y/clog/clog.go. It
only surfaced now that otel 1.46 reached sid.
The new upstream 1.6.3 fixes it: upstream migrated clog.go to the attribute.*
API. I have it packaged and building against otel 1.46, as an MR against
go-team with a fully green Salsa CI (build on all arches, lintian, autopkgtest,
piuparts):
https://salsa.debian.org/go-team/packages/siso/-/merge_requests/8
Its changelog closes this bug. Could a DD review and sponsor the upload?
Andres, you kindly helped with siso before (the 1.5.22 binNMU, #1149669);
would you be able to take this one? It fixes the RC FTBFS and brings siso to
1.6.3 in one go.
Three things: 1) I'm not a member of the Go Team, and so I don't have
permission to merge that MR. I'd want either to be added as a member so
I could merge that MR before uploading, or at the very least get an ACK
from Simon that the MR will be merged and the release tagged after I
verify the MR and sponsor the upload. I don't want the package to get
out of sync with the git repo. (Obviously if there issues w/ the MR, I'd
ask for them to be fixed before doing the upload.)
2) Salsa has a "reviewer" field; I think you'll get more responsiveness
if you use it. For example, see this MR on the chromium package:
https://salsa.debian.org/chromium-team/chromium/-/merge_requests/46
Had Daniel not set me as the reviewer, I wouldn't have seen it until I
happened to be bored and looked specifically at chromium's MRs.
3) I don't know who's actually updating the pristine-tar branch, but I'm
going to assume whoever is doing that will do it after this MR gets merged.
If Simon gives me the okay, I'll go ahead and start reviewing the MR.
