* travis-ci no longer supports python 2.5
http://blog.travis-ci.com/2013-11-18-upcoming-build-environment-updates/
> Python 2.5 has been removed due to very low overall usage and
> breaking changes in pip and virtualenv.
* GitPython
pip install no longer supports pre-release versions by default
http://www.pip-installer.org/en/latest/reference/pip_install.html#pre-release-versions
resolves build error:
$ pip install 'GitPython >= 0.2.0' --use-mirrors
--use-mirrors has been deprecated and will be removed in the future.
Explicit uses of --index-url and/or --extra-index-url is suggested.
Downloading/unpacking GitPython>=0.2.0
Could not find a version that satisfies the requirement
GitPython>=0.2.0 (from versions: 0.1.7, 0.2.0-beta1, 0.3.0-beta1,
0.3.0-beta2, 0.3.1-beta2, 0.3.2.RC1)
Cleaning up...
No distributions matching the version for GitPython>=0.2.0
Travis[1] runs continuous integration for Open Source projects. With
github, it will run the configured tests and tag pull requests as passing
or failing. This commit adds a Travis configuration.
Since Travis hosts run debian/ubuntu, and execute tests in virtualenv,
getting access to `rpm` and `python-rpm` is impossible, or nontrivial,
at least. For now, ignore the functional tests. To support running the
BuildTargetParser tests, pull that class out into its own module, and
away from release.py, which imports `rpm`.
To configure travis, go to the website, log in with your github account,
then sync your repos under the account tab below your name. Then just
switch the repo to 'on' and it should be all set up.
[1]: http://travis-ci.org
