On 03/03/2025 10:09, Nicolas Peugnet wrote:
On 02/03/2025 21:04, Martina Ferrari wrote:
I think that makes sense.. But it would be good to know how many
packages break with the upgrade.. is the CI job in salsa reliable
enough to know this?
In this specific case, the "test_the_archive" jobs will not detect
issues, because it is not the sources of x-tools that are used in
dependent packages, but the built binaries. And IIRC, this job only
tries to rebuild everything from sources.
I am currently running ratt on a quite powerful machine, so the 409
packages should be rebuilt at the end of the day.
I can push it to the team's repo but I don't have the permissions to
upload anyway. I will post the results of ratt once it is done so that
we can decide in which distribution to upload it first.
Here are the results of ratt, out of 409 packages rebuilt, 12 failed to
build:
2025/03/03 16:02:12 FAILED: golang-k8s-kube-openapi (see
buildlogs/golang-k8s-kube-openapi_0.0~git20231214.ab13479-3)
2025/03/03 16:02:12 FAILED: kitty (see buildlogs/kitty_0.39.1-1)
2025/03/03 16:02:12 FAILED: gitaly (see buildlogs/gitaly_16.8.2+ds3-2)
2025/03/03 16:02:12 FAILED: golang-github-lucas-clemente-quic-go (see
buildlogs/golang-github-lucas-clemente-quic-go_0.46.0-2)
2025/03/03 16:02:12 FAILED: golang-github-bugsnag-bugsnag-go (see
buildlogs/golang-github-bugsnag-bugsnag-go_2.2.0-1)
2025/03/03 16:02:12 FAILED: gittuf (see buildlogs/gittuf_0.8.0-3)
2025/03/03 16:02:12 FAILED: etcd (see buildlogs/etcd_3.5.16-3)
2025/03/03 16:02:12 FAILED: gitlab-ci-multi-runner (see
buildlogs/gitlab-ci-multi-runner_14.10.1-1)
2025/03/03 16:02:12 FAILED: zabbix (see buildlogs/zabbix_1:7.0.10+dfsg-1)
2025/03/03 16:02:12 FAILED: gitlab (see buildlogs/gitlab_17.3.5-2)
2025/03/03 16:02:12 FAILED: golang-github-hashicorp-memberlist (see
buildlogs/golang-github-hashicorp-memberlist_0.5.0-1)
2025/03/03 16:02:12 FAILED: receptor (see buildlogs/receptor_1.5.2-1)
Most of them are already currently failing in unstable:
golang-k8s-kube-openapi: #1096242
kitty: #1099240
gitaly: #1088134
golang-github-lucas-clemente-quic-go: #1098558
golang-github-bugsnag-bugsnag-go: #1098550
gittuf: https://ci.debian.net/packages/g/gittuf/testing/amd64/58161105/
etcd: needs another fix as previously said
gitlab-ci-multi-runner: #1080062
gitlab: currently BD-Unistallable
golang-github-hashicorp-memberlist:
https://ci.debian.net/packages/g/golang-github-hashicorp-memberlist/unstable/amd64/58183351/
receptor: #1096226
There is only zabbix that seems to be a new failure, but I don't think
it comes from x-tools upgrade:
# google.golang.org/protobuf/types/known/timestamppb
vendor/google.golang.org/protobuf/types/known/timestamppb/timestamp.pb.go:327:92:
unsafe.StringData requires go1.20 or later (-lang was set to go1.18;
check go.mod)
vendor/google.golang.org/protobuf/types/known/timestamppb/timestamp.pb.go:353:32:
unsafe.StringData requires go1.20 or later (-lang was set to go1.18;
check go.mod)
I just pushed my changes to the team's repo
(https://salsa.debian.org/go-team/packages/golang-golang-x-tools), I'll
let one of you release it and do an upload.
--
Nicolas Peugnet
