Created attachment 394706 [details] jenkins-webapi-0.4.0.ebuild Module for interacting with the Jenkins CI server Jenkins-webapi is a library for programatically accessing Jenkins' remote web API. It has the following advantages over other similar libraries: Supports Python versions 2.6 to 3.3. Has a comprehensive test suite. A concise and intuitive API. Needed by jenkins-autojobs.
Created attachment 394708 [details] jenkins-webapi-0.4.0.ebuild Correct license
Created attachment 394712 [details] jenkins-webapi-0.4.0.ebuild Correct homepage/description
looks good I'll run it tomorrow
tomorrow arrived. I ran it; cat /mnt/gen2/TmpDir/portage/dev-python/jenkins-webapi-0.4.0/work/jenkins-webapi-0.4.0/requirements-dev.txt pytest >= 2.6.3 termcolor >= 1.1.0 pytest-cov >= 1.8.0 httmock >= 1.2.2 Sphinx >= 1.2.3 alabaster >= 0.6.1 see https://pypi.python.org/pypi/httmock/1.2.2 The rest we have. That ought be an easy one. Optionally the test phase can be skipped which is not my style. Still awaiting progress on 537346. That one was entered first and ought be the first to be added.
upstream did it again ~/improvise/dev-python/jenkins-webapi $ l /mnt/gen2/TmpDir/portage/dev-python/jenkins-webapi-0.4.0/work/jenkins-webapi-0.4.0/ MANIFEST.in PKG-INFO README.rst jenkins.py jenkins_webapi.egg-info requirements-dev.txt setup.cfg setup.py but in the repo https://github.com/gvalkov/jenkins-webapi both a doc folder and a tests folder. After all the updating and bumping of the required test deps I get this. You know what to do
Because of that, we can pack version 0.3.2 instead of 0.4.0 (to have the tests).
Created attachment 395068 [details] jenkins-webapi-0.3.2.ebuild Adding tests
Created attachment 395070 [details, diff] local_jenkins_war.patch
Created attachment 395072 [details, diff] tests_py27.patch
(In reply to Tomas Mozes from comment #6) > Because of that, we can pack version 0.3.2 instead of 0.4.0 (to have the > tests). Actually, yes, we can add version 0.3.2 and have a fully running testsuite. In addition, need approach upstream and prompt / request then to add the missing 2 folders to the tarball that is for pypi for 2 reasons; 1) it's preferable to use pypi as a source repo in an ebuild in gentoo, 2) They may have overlooked it by human error. Re no. 2), there are 2 typical reasons; a) They decided they didn't want the tests included but were clumsy enough to still leave references and instructions to its use in the files of the source b) They missed by accident and will therefore likely reply with thanks for pointing this out. I have seen both many times. Either way, Just prompt with a simple factual observation which doesn't offend in any way, easily done, and then await their reply. I have done this many times. Either way, jenkins-webapi-0.4.0 cannot have a test run because of all above, but we still add it. Being the most recent release far outweighs absence of a testsuite. Then we look forward to a release which has them re-added and all just works.
Now for the doc build. Next to replicate this ~/improvise/dev-python/jenkins-webapi $ USE=doc ebuild jenkins-webapi-0.3.2.ebuild clean install * python2_7: running distutils-r1_run_phase python_install_all >>> Completed installing jenkins-webapi-0.3.2 into /mnt/gen2/TmpDir/portage/dev-python/jenkins-webapi-0.3.2/image/ ~/improvise/dev-python/jenkins-webapi $ l /mnt/gen2/TmpDir/portage/dev-python/jenkins-webapi-0.3.2/image//usr/share/doc/jenkins-webapi-0.3.2/ README.rst.bz2 html
Created attachment 395098 [details] jenkins-webapi-0.3.2.ebuild Adding docs
(In reply to Ian Delaney from comment #10) > (In reply to Tomas Mozes from comment #6) > > Because of that, we can pack version 0.3.2 instead of 0.4.0 (to have the > > tests). > > Actually, yes, we can add version 0.3.2 and have a fully running testsuite. > In addition, need approach upstream and prompt / request then to add the > missing 2 folders to the tarball that is for pypi for 2 reasons; 1) it's > preferable to use pypi as a source repo in an ebuild in gentoo, 2) They may > have overlooked it by human error. > > Re no. 2), there are 2 typical reasons; > a) They decided they didn't want the tests included but were clumsy enough > to still leave references and instructions to its use in the files of the > source > b) They missed by accident and will therefore likely reply with thanks for > pointing this out. > > I have seen both many times. Either way, Just prompt with a simple factual > observation which doesn't offend in any way, easily done, and then await > their reply. I have done this many times. Either way, jenkins-webapi-0.4.0 > cannot have a test run because of all above, but we still add it. Being the > most recent release far outweighs absence of a testsuite. Then we look > forward to a release which has them re-added and all just works. https://github.com/gvalkov/jenkins-webapi/issues/8
*jenkins-webapi-0.4.0 (29 Jan 2015) *jenkins-webapi-0.3.2 (29 Jan 2015) 29 Jan 2015; Ian Delaney <idella4@gentoo.org> +files/local_jenkins_war.patch, +files/tests_py27.patch, +jenkins-webapi-0.3.2.ebuild, +jenkins-webapi-0.4.0.ebuild, +metadata.xml: Module for interacting with the Jenkins CI server, ebuilds written by maintainer via bug #537440, 0.4.0 is missing folders present in 0.3.2, next release expected to see them re-added, closes bug #537440
