Merge lp:~jml/pkgme/rollback-r121 into lp:pkgme
Status: | Merged |
---|---|
Approved by: | James Westby |
Approved revision: | 122 |
Merged at revision: | 122 |
Proposed branch: | lp:~jml/pkgme/rollback-r121 |
Merge into: | lp:pkgme |
Diff against target: |
155 lines (+4/-75) 6 files modified
pkgme/bin/main.py (+1/-5) pkgme/debuild.py (+0/-28) pkgme/package_files.py (+1/-1) pkgme/tests/test_debuild.py (+0/-38) pkgme/tests/test_package_files.py (+1/-1) pkgme/tests/test_script.py (+1/-2) |
To merge this branch: | bzr merge lp:~jml/pkgme/rollback-r121 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
James Westby | Approve | ||
Review via email: mp+115981@code.launchpad.net |
Commit message
Rollback r121, as it is breaking nagios checks on staging
Description of the change
Our staging end-to-end checks are failing with the following error (lightly formatted by me)
liam@emim:
Check failed in 8.129219: Failed to build package:
debuild --no-lintian -S -uc -us failed with returncode 29. Output:
| sh: 1: gcc: not found
| dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation)
| dpkg-buildpackage -rfakeroot -d -us -uc -S
| dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor): -g -O2 -fstack-protector --param=
| dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor): -D_FORTIFY_SOURCE=2
| dpkg-buildpackage: export CXXFLAGS from dpkg-buildflags (origin: vendor): -g -O2 -fstack-protector --param=
| dpkg-buildpackage: export FFLAGS from dpkg-buildflags (origin: vendor): -g -O2
| dpkg-buildpackage: export LDFLAGS from dpkg-buildflags (origin: vendor): -Wl,-Bsymbolic-
| dpkg-buildpackage: source package jabberwocky
| dpkg-buildpackage: source version 0
| dpkg-buildpackage: source changed by pkgme-service bot <email address hidden>
| sh: 1: gcc: not found
| dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation)
| dpkg-source --before-build jabberwocky
| fakeroot debian/rules clean
| dh clean
| dh_testdir
| dh_auto_clean
| sh: 1: gcc: not found
| dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation)
| dh_clean
| dpkg-source -b jabberwocky
| dpkg-source: error: can't build with source format '3.0 (quilt)': no upstream tarball found at ../jabberwocky_
| dpkg-buildpackage: error: dpkg-source -b jabberwocky gave error exit status 255
| debuild: fatal error at line 1350:
| dpkg-buildpackage -rfakeroot -d -us -uc -S failed
Other data: {u'dependencies': [], u'packaged_
This branch rolls back the latest changes to pkgme in the hope that it will fix this error.
jml
pkgme-service doesn't use the functions to build a package, just the ones to
write the packaging, then it builds the package itself.
Therefore I think this needs to be landed with a change to pkgme-service
to also call the new build_orig_tar_gz function.
Thanks,
James