Source: golang-1.13 Source-Version: 1.13.8-1 Severity: important Hi!
This package fails to build twice in a row. On the second dpkg-buildpackage invocation we get this: ,--- […] dpkg-source --before-build . debian/rules clean dh clean debian/rules override_dh_auto_clean make[1]: Entering directory '/tmp/golang/golang-1.13-1.13.8' for file in control gbp.conf source/lintian-overrides watch; do \ { \ echo '#'; \ echo '# WARNING: "debian/'$file'" is generated via "debian/rules gencontrol" (sourced from "debian/'$file'.in")'; \ echo '#'; \ echo; \ sed -e 's/X.Y/1.13/g' debian/$file.in; \ } > debian/$file; \ done # remove autogenerated files rm -f \ src/cmd/cgo/zdefaultcc.go \ src/cmd/go/zdefaultcc.go \ src/cmd/internal/obj/zbootstrap.go \ src/runtime/internal/sys/zversion.go # remove built objects rm -rf bin pkg removed 'golang-1.13-doc.dirs' removed 'golang-1.13-doc.install' removed 'golang-1.13-doc.links' removed 'golang-1.13-doc.lintian-overrides' removed 'golang-1.13-go.dirs' removed 'golang-1.13-go.install' removed 'golang-1.13-go.links' removed 'golang-1.13-go.lintian-overrides' removed 'golang-1.13-go.postinst' removed 'golang-1.13-src.install' removed 'golang-1.13-src.lintian-overrides' make[1]: Leaving directory '/tmp/golang/golang-1.13-1.13.8' dh_clean dpkg-source -b . dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building golang-1.13 using existing ./golang-1.13_1.13.8.orig.tar.gz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: local changes detected, the modified files are: golang-1.13-1.13.8/src/cmd/go/internal/cfg/zdefaultcc.go golang-1.13-1.13.8/src/cmd/go/internal/cfg/zosarch.go golang-1.13-1.13.8/src/cmd/internal/objabi/zbootstrap.go golang-1.13-1.13.8/src/go/build/zcgo.go dpkg-source: info: you can integrate the local changes with dpkg-source --commit dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/golang-1.13_1.13.8-1.diff.8vX2Ww dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 […] `--- I guess the paths got changed upstream and didn't get updated in the packaging? Thanks, Guillem