Update debian/rules to run `./setup.py test` during build
Bug #822413 reported by
Jason Gerard DeRose
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
FileStore |
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://
Related branches
lp:~thenewme91/filestore/lp822413
- Jason Gerard DeRose: Approve
-
Diff: 22 lines (+8/-0)1 file modifieddebian/rules (+8/-0)
Changed in filestore: | |
assignee: | nobody → Michael Chang (thenewme91) |
status: | Triaged → Fix Committed |
Changed in filestore: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Tried to take a stab at this, but for some reason, when I call "debuild -S", debhelper is calling python 2.6 instead of python 3.2 on my system:
http:// paste.ubuntu. com/661594/
I'm not sure if it's appropriate to add a debian/pyversions file as mentioned in this wiki page:
https:/ /wiki.ubuntu. com/PackagingGu ide/Python# Python_ versions_ information_ -_debian. 2BAC8-pyversion s
Adding a debian/pyversions file makes debuild and dput work nicely on my system.
For now lp:~thenewme91/filestore/lp822413 contains semi-tested changes (without debian/pyversions). Adding a debian/pyversions file with the content "3.2-" causes the package to build fine in my PPA.
Also, I'm not 100% sure if I changed the changelog correctly / should be changing the changelog at all.