ftbfs with golang-1.16

Bug #1939171 reported by Brian Murray
This bug affects 1 person
Affects Status Importance Assigned to Milestone
piuparts (Debian)
Fix Released
piuparts (Ubuntu)
Fix Committed
Brian Murray

Bug Description

In https://launchpadlibrarian.net/551476957/buildlog_ubuntu-impish-amd64.piuparts_1.1.4_BUILDING.txt.gz we can see the following:

touch build-stamp
(cd helpers/debiman-piuparts-distill && go build)
go: go.mod file not found in current directory or any parent directory; see 'go help modules'
make[2]: *** [Makefile:61: build-master-stamp] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:9: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

This happens with piuparts version 1.1.4 and a test rebuild of 1.12 using golang-go (which depends on golang-1.16-go) also failed.

Modifying piuparts to build with golang-1.15-go causes the build to succeed.

tags: added: ftbfs
Changed in piuparts (Ubuntu):
assignee: nobody → Brian Murray (brian-murray)
status: New → In Progress
Revision history for this message
Brian Murray (brian-murray) wrote :

I've forwarded the attached patch to Debian.

tags: added: patch
Changed in piuparts (Debian):
status: Unknown → New
Changed in piuparts (Debian):
status: New → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote :

piuparts (1.1.5) unstable; urgency=medium

  [ Nicolas Dandrimont ]
  * pejacevic: update enabled suites for bullseye as stable, bookworm as
  * Add news for the bullseye update.
  * Fix perjacevic typo in docs.

  [ David Steele ]
  * Remove oldstable results from summary.json.

  [ Athos Ribeiro ]
  * d/rules: set GO111MODULE to auto to maintain pre Go 1.16 behavior. Closes: #991970.
    (MR: debian/piuparts!35)

 -- Holger Levsen <email address hidden> Thu, 14 Oct 2021 15:23:26 +0200

Changed in piuparts (Ubuntu):
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.