ags-integration-test fails with "dpkg-buildpackage: error: fakeroot not found, either install the fakeroot package, specify a command with the -r option, or run this as root"

Bug #1743511 reported by Daniel van Vugt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gsequencer (Debian)
Fix Released
Unknown
gsequencer (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Looks like someone forgot to build-depends on fakeroot...

autopkgtest [05:58:27]: test ags-integration-test: [-----------------------
dpkg-source: info: using options from /tmp/autopkgtest.MH7aNB/build.UF6/src/debian/source/options: --extend-diff-ignore=(^|/)(config\.sub|config\.guess|Makefile)$
dpkg-buildpackage: error: fakeroot not found, either install the fakeroot
package, specify a command with the -r option, or run this as root
autopkgtest [05:58:27]: test ags-integration-test: -----------------------]
autopkgtest [05:58:27]: test ags-integration-test: - - - - - - - - - - results - - - - - - - - - -
ags-integration-test FAIL non-zero exit status 25
autopkgtest [05:58:28]: test ags-integration-test: - - - - - - - - - - stderr - - - - - - - - - -
dpkg-buildpackage: error: fakeroot not found, either install the fakeroot
package, specify a command with the -r option, or run this as root
autopkgtest [05:58:28]: @@@@@@@@@@@@@@@@@@@@ summary
ags-integration-test FAIL non-zero exit status 25

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/g/gsequencer/20180116_055835_6652f@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/g/gsequencer/20180116_033415_6652f@/log.gz

summary: ags-integration-test fails with "dpkg-buildpackage: error: fakeroot not
- found, either install the fakeroot"
+ found, either install the fakeroot package, specify a command with the
+ -r option, or run this as root"
description: updated
Changed in gsequencer (Ubuntu):
importance: Undecided → High
Changed in gsequencer (Debian):
status: Unknown → New
Revision history for this message
Iain Lane (laney) wrote :

This was fixed in 1.2.1-1

gsequencer (1.2.1-1) unstable; urgency=medium

  * New upstream version 1.2.1

  [ Joël Krähemann ]
  * Refreshed patches
    * Removed patches applied upstream
    * Provided patch to enable integration tests
  * Removed libgmp dependency
  * Updated autopkgtests
    * Fixed dependencies
    * Restrictions: isolation and stderr
    * Run integration tests using xvfb-run
    * Fixed pre-integration-test target and provide LD_LIBRARY_PATH
      (both multi-arch and non-multi-arch)
  * Added pre-integration-test target

  [ IOhannes m zmölnig (Debian/GNU) ]
  * Removed generated lib*.sym files in 'clean' target
  * Updated libags(-audio|-gui|)1.symbols
  * Use https:// in d/watch
  * Bumped standards version to 4.1.2

 -- IOhannes m zmölnig (Debian/GNU) <email address hidden> Wed, 13 Dec 2017 15:37:51 +0100

We need to run against a newer gsequencer. It hasn't migrated to release yet because we're still not getting builds for all arches.

I execute this run and it succeeded.

Changed in gsequencer (Ubuntu):
status: New → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

That doesn't sound right. Firstly the version of gsequencer in archive has not changed. So nothing was released. Secondly, looking at the source of version 1.3.6-1 I can see the bug still but no fix, so what does the fix look like?

Changed in gsequencer (Ubuntu):
status: Fix Released → New
Changed in gsequencer (Debian):
status: New → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Actually, it sounds like it's fixed now:

autopkgtest for gsequencer/1.1.4-1: arm64: Regression ♻ , armhf: Pass, ppc64el: Regression ♻ , s390x: Ignored failure
autopkgtest for gsequencer/1.3.6-1: amd64: Pass, i386: Pass

Changed in gsequencer (Ubuntu):
status: New → Fix Committed
Changed in gsequencer (Ubuntu):
status: Fix Committed → Fix Released
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.