Public bug reported:
Having Debian Import frozen for the Resolute release brought quite a
hell in some golang packages part of the rclone build-depends graph,
because some `Breaks` were introduced, and syncing all the latest
versions at once prevents some of them to build.
As we currently understand it, those packages were uploaded to Debian:
Sun, 03 May 2026 15:03:38 +0000 golang-github-aws-smithy-go (1.25.1-1)
Sun, 03 May 2026 15:10:42 +0000 golang-github-aws-aws-sdk-go-v2 (1.41.7-1)
Thu, 07 May 2026 13:06:38 +0000 golang-github-aws-smithy-go (1.25.1-2)
^^^ this last one introduce "Breaks
golang-github-aws-aws-sdk-go-v2-dev (< 1.41.7-1)"
The plan right now is the following:
* Delete source of golang-github-aws-smithy-go (1.25.1-3) from stonking-proposed
* Delete binaries from golang-github-aws-smithy-go (1.25.1-2) from
stonking-proposed
* Upload golang-github-aws-smithy-go (1.25.1-1ubuntu1) to stonking with an
empty delta to prevent from syncing
* Retry all the related built failures:
golang-github-aws-aws-sdk-go-v2
golang-opentelemetry-otel
golang-github-prometheus-common
golang-github-prometheus-sigv4
golang-google-grpc
* Sync golang-github-aws-smithy-go (1.25.1-2 or later) again
There might be more entanglement down the line, but we'll see as things
progress.
** Affects: golang-github-aws-aws-sdk-go-v2 (Ubuntu)
Importance: Undecided
Status: New
** Affects: golang-github-aws-smithy-go (Ubuntu)
Importance: Undecided
Status: New
** Affects: golang-github-prometheus-common (Ubuntu)
Importance: Undecided
Status: New
** Affects: golang-github-prometheus-sigv4 (Ubuntu)
Importance: Undecided
Status: New
** Affects: golang-google-grpc (Ubuntu)
Importance: Undecided
Status: New
** Affects: golang-opentelemetry-otel (Ubuntu)
Importance: Undecided
Status: New
** Also affects: golang-github-aws-smithy-go (Ubuntu)
Importance: Undecided
Status: New
** Also affects: golang-opentelemetry-otel (Ubuntu)
Importance: Undecided
Status: New
** Also affects: golang-github-prometheus-common (Ubuntu)
Importance: Undecided
Status: New
** Also affects: golang-github-prometheus-sigv4 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: golang-google-grpc (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- FTBFS after Debian import resumed
+ FTBFS hell after Debian import resumed
** Description changed:
Having Debian Import frozen for the Resolute release brought quite a
hell in some golang packages part of the rclone build-depends graph,
because some `Breaks` were introduced, and syncing all the latest
versions at once prevents some of them to build.
As we currently understand it, those packages were uploaded to Debian:
Sun, 03 May 2026 15:03:38 +0000 golang-github-aws-smithy-go (1.25.1-1)
Sun, 03 May 2026 15:10:42 +0000 golang-github-aws-aws-sdk-go-v2 (1.41.7-1)
Thu, 07 May 2026 13:06:38 +0000 golang-github-aws-smithy-go (1.25.1-2)
- ^^^ this last one introduce "Breaks
golang-github-aws-aws-sdk-go-v2-dev (< 1.41.7-1)"
+ ^^^ this last one introduce "Breaks
golang-github-aws-aws-sdk-go-v2-dev (< 1.41.7-1)"
The plan right now is the following:
- * Delete golang-github-aws-smithy-go (1.25.1-2) from stonking-proposed
+ * Delete golang-github-aws-smithy-go (1.25.1-3) from stonking-proposed
* Upload golang-github-aws-smithy-go (1.25.1-1ubuntu1) to stonking with an
empty delta to prevent from syncing
* Retry all the related built failures:
- golang-github-aws-aws-sdk-go-v2
- golang-opentelemetry-otel
- golang-github-prometheus-common
- golang-github-prometheus-sigv4
- golang-google-grpc
+ golang-github-aws-aws-sdk-go-v2
+ golang-opentelemetry-otel
+ golang-github-prometheus-common
+ golang-github-prometheus-sigv4
+ golang-google-grpc
* Sync golang-github-aws-smithy-go (1.25.1-2 or later) again
There might be more entanglement down the line, but we'll see as things
progress.
** Description changed:
Having Debian Import frozen for the Resolute release brought quite a
hell in some golang packages part of the rclone build-depends graph,
because some `Breaks` were introduced, and syncing all the latest
versions at once prevents some of them to build.
As we currently understand it, those packages were uploaded to Debian:
Sun, 03 May 2026 15:03:38 +0000 golang-github-aws-smithy-go (1.25.1-1)
Sun, 03 May 2026 15:10:42 +0000 golang-github-aws-aws-sdk-go-v2 (1.41.7-1)
Thu, 07 May 2026 13:06:38 +0000 golang-github-aws-smithy-go (1.25.1-2)
^^^ this last one introduce "Breaks
golang-github-aws-aws-sdk-go-v2-dev (< 1.41.7-1)"
The plan right now is the following:
- * Delete golang-github-aws-smithy-go (1.25.1-3) from stonking-proposed
+ * Delete source of golang-github-aws-smithy-go (1.25.1-3) from
stonking-proposed
+ * Delete binaries from golang-github-aws-smithy-go (1.25.1-2) from
stonking-proposed
* Upload golang-github-aws-smithy-go (1.25.1-1ubuntu1) to stonking with an
empty delta to prevent from syncing
* Retry all the related built failures:
golang-github-aws-aws-sdk-go-v2
golang-opentelemetry-otel
golang-github-prometheus-common
golang-github-prometheus-sigv4
golang-google-grpc
* Sync golang-github-aws-smithy-go (1.25.1-2 or later) again
There might be more entanglement down the line, but we'll see as things
progress.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2155158
Title:
FTBFS hell after Debian import resumed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-aws-aws-sdk-go-v2/+bug/2155158/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
