[pkg-go] Bug#980668: golang-github-cznic-lldb: FTBFS: expects import "modernc.org/fileutil"

[Lucas Nussbaum]

Source: golang-github-cznic-lldb
Version: 1.0.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>    dh_update_autotools_config -O--buildsystem=golang
>    dh_auto_configure -O--buildsystem=golang
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>    dh_auto_build -O--buildsystem=golang
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 in use)
> 	cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1 github.com/cznic/lldb
> src/github.com/cznic/lldb/2pc.go:16:2: code in directory /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/cznic/fileutil expects import "modernc.org/fileutil"
> src/github.com/cznic/lldb/2pc.go:17:2: code in directory /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src/github.com/cznic/mathutil expects import "modernc.org/mathutil"
> dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1 github.com/cznic/lldb returned exit code 1
> make: *** [debian/rules:6: build] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2021/01/20/golang-github-cznic-lldb_1.0.1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.