Actions
Bug #13057
closedpython-setuptools is missing from debian/control
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
If I run a package build from the current git master, I get this error after about 90 minutes of compilation:
... cd ./ceph-detect-init ; python setup.py build Traceback (most recent call last): File "setup.py", line 23, in <module> from setuptools import setup ImportError: No module named setuptools Makefile:25678: recipe for target 'all-local' failed make[4]: *** [all-local] Error 1 make[4]: *** Waiting for unfinished jobs.... make[4]: Leaving directory '/home/jrosenboom/ceph/src' Makefile:24140: recipe for target 'all-recursive' failed make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory '/home/jrosenboom/ceph/src' Makefile:10094: recipe for target 'all' failed make[2]: *** [all] Error 2 make[2]: Leaving directory '/home/jrosenboom/ceph/src' Makefile:479: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/jrosenboom/ceph' debian/rules:50: recipe for target 'build-stamp' failed make: *** [build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 debuild: fatal error at line 1376: dpkg-buildpackage -rfakeroot -D -us -uc -b -j8 failed
After apt-get-installing python-setuptools the package build works fine.
Updated by Loïc Dachary over 8 years ago
- Status changed from New to Need More Info
did you ./install-deps.sh before building ?
Updated by Jens Harbott over 8 years ago
yes, otherwise the compilation wouldn't have succeeded that far.
Updated by Loïc Dachary over 8 years ago
Which Operating System (type and version) should I use to reproduce this problem ?
Updated by Jens Harbott over 8 years ago
Sorry for not getting back earlier, I think my test has been on Ubuntu Trusty, but it may have been some newer Ubuntu release.
Anyway, when trying to reproduce, I found that this has already been resolved by commit 036d36f4ff6d4b6ae97712ee565e88564159e0f0.
Updated by Sage Weil over 8 years ago
- Status changed from Need More Info to Resolved
Actions