Update debian/rules to run `./setup.py test` during build
Bug #823288 reported by
Jason Gerard DeRose
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Microfiber |
Fix Released
|
High
|
Michael Chang |
Bug Description
During Barry Warsaw's App Developer Week session, he mentioned how to make debian/rules run `setup.py test` during a build, so that tests are run during daily Launchpad builds and so on. Here's the IRC log:
https:/
And an example debian/rules (but we need Python3 only):
http://
Also see equivalent bug in `filestore`:
Related branches
lp:~thenewme91/microfiber/lp823288
- Jason Gerard DeRose: Approve
-
Diff: 36 lines (+10/-1)2 files modifieddebian/control (+2/-1)
debian/rules (+8/-0)
Changed in microfiber: | |
status: | In Progress → Fix Committed |
Changed in microfiber: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Initially, the project failed to build from source (FTBFS) upon adding the tests to the build proces; upon inspecting the logs, it appears that debhelper was calling python3.1 to run tests when only python3.2 was installed.
Updating debian/control to include X-Python-Version and X-Python3-Version headers (instead of the outdated XS-Python-Version header, as per the Debian Python Policy[0]) makes it build again.
[0] http:// www.debian. org/doc/ packaging- manuals/ python- policy/ ch-module_ packages. html