Fixing golang-github-bugsnag-bugsnag-go: FTBFS

To: debian-go@lists.debian.org
Subject: Fixing golang-github-bugsnag-bugsnag-go: FTBFS
From: Nicolas Peugnet <nicolas@club1.fr>
Date: Tue, 4 Mar 2025 19:15:05 +0100
Message-id: <[🔎] cd4d9122-bc57-41d0-9382-39176a52eacc@club1.fr>

Hi,

After quite a long debugging session, I managed to fix the build failureof golang-github-bugsnag-bugsnag-go.

(https://salsa.debian.org/go-team/packages/golang-github-bugsnag-bugsnag-go)

For now I only added a patch to v2.2.0, but we should be able to upgradethe package to v2.5.1. I will run ratt with this new version and keepyou updated. It it fails, we can simply upload the patched v2.2.0.

--
Nicolas Peugnet

Reply to:

debian-go@lists.debian.org
Nicolas Peugnet (on-list)
Nicolas Peugnet (off-list)

Follow-Ups:
- Re: Fixing golang-github-bugsnag-bugsnag-go: FTBFS
  - From: Nicolas Peugnet <nicolas@club1.fr>

Prev by Date: Re: [notaryproject/notary] arm64 self-check failures: runtime: marked free object in span 0xffff5ec83ac0, elemsize=208 freeindex=3 (bad use of unsafe.Pointer or having race conditions? try -d=checkptr or -race) (Issue #1708)
Next by Date: Re: [notaryproject/notary] arm64 self-check failures: runtime: marked free object in span 0xffff5ec83ac0, elemsize=208 freeindex=3 (bad use of unsafe.Pointer or having race conditions? try -d=checkptr or -race) (Issue #1708)
Previous by thread: Re: Fixing golang-opentelemetry-contrib: FTBFS
Next by thread: Re: Fixing golang-github-bugsnag-bugsnag-go: FTBFS
Index(es):
- Date
- Thread