Source: golang-github-checkpoint-restore-go-criu
Version: 4.1.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> cp -rv debian/missing-sources/* ./
> 'debian/missing-sources/rpc/rpc.proto' -> './rpc/rpc.proto'
> 'debian/missing-sources/rpc/rpc.proto.URL' -> './rpc/rpc.proto.URL'
> 'debian/missing-sources/stats/stats.proto' -> './stats/stats.proto'
> 'debian/missing-sources/stats/stats.proto.URL' -> './stats/stats.proto.URL'
> protoc --go_out=. rpc/rpc.proto
> cp -rv debian/missing-sources/* ./
> 'debian/missing-sources/rpc/rpc.proto' -> './rpc/rpc.proto'
> 'debian/missing-sources/rpc/rpc.proto.URL' -> './rpc/rpc.proto.URL'
> 'debian/missing-sources/stats/stats.proto' -> './stats/stats.proto'
> 'debian/missing-sources/stats/stats.proto.URL' -> './stats/stats.proto.URL'
> protoc --go_out=. stats/stats.proto
> dh_auto_configure
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>    dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
> package github.com/checkpoint-restore/go-criu/test: C source files not 
> allowed when not using cgo or SWIG: piggie.c
>       cd _build && go install -trimpath -v -p 4
> package .: no Go files in /<<PKGBUILDDIR>>/_build
> dh_auto_build: error: cd _build && go install -trimpath -v -p 4 returned exit 
> code 1
> make: *** [debian/rules:9: binary] Error 25

The full build log is available from:
   
http://qa-logs.debian.net/2020/09/26/golang-github-checkpoint-restore-go-criu_4.1.0-2_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!

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.

Reply via email to