dev-python/pylucene-jcc is a DEPEND for dev-python/pylucene ( #81416 ) Ebuild prepared and needs bug for submission to sunrise overlay and subsequently entering portage Reproducible: Always Steps to Reproduce:
Created attachment 181960 [details] Ebuild for pylucene-jcc (~x86) Here is the ebuild - it builds fine and works well for building pylucene on my machine (marked ~x86 untested on other arches).
doesn't work for me. setup.py from pylucene wants me to have ejavac in addition to the issue 43 patch for setuptools .. how did you get your ejavac ? equery b `which ejavac` ?
As far as ejavac goes I changed that. Oh, and I changed the versioning to coincide with internal JCC versions (instead of with pylucene which was 2.4.*) I just uploaded into the java-experimental overlay. https://overlays.gentoo.org/svn/proj/java/java-experimental/dev-python/pylucene-jcc/ I tested on x86 only. All tests should work fine at this point. Please test on other arches, and let me know if there are any other things I missed. Thanks!
Comment on attachment 181960 [details] Ebuild for pylucene-jcc (~x86) With the version in the overlay, the ebuild attached is obsolete.
thanks a million. kinda works for me on amd64, I suggest adding ~amd64 to keywords. One odd thing though, when using my 0027 umask, it doesn't go though the compile phase. >>> Source configured. >>> Compiling source in /var/tmp/portage/dev-python/pylucene-jcc-2.2/work/pylucene-2.4.1-1/jcc ... Traceback (most recent call last): File "setup.py", line 317, in <module> main('--debug' in sys.argv) File "setup.py", line 275, in main raise type(e), "%s: %s" %(e, args) OSError: [Errno 13] Permission denied: ['', '-source', '1.4', '-target', '1.4', '-d', 'jcc/classes', 'java/org/apache/jcc/PythonVM.java', 'java/org/apache/jcc/PythonException.java'] * * ERROR: dev-python/pylucene-jcc-2.2 failed. I was able to work around it by temporarily reverting to a gentoo default umask 0022 (I was using 0027), and by using ebuild directly rather than by using emerge. This is the first time I had emerge issues due to my umask.
(In reply to comment #5) > kinda works for me on amd64, I suggest adding ~amd64 to keywords. > One odd thing though, when using my 0027 umask, it doesn't go though the > compile phase. Hmm. ok, I'll add ~amd64, but I'm really not sure how to go about fixing anything with umask problem though. Any suggestions?
Thanks for ~amd64 I added a simple "einfo `whoami`" at the beggining of pkg_setup and src_compile, and found out the pkg_setup part is being run by user "root", and that src_compile is being run as user "portage". That means that any package using pkg_setup should be affected, which means that my problem is not specific to this ebuild. Sorry for the confusion, and thanks once again for providing this ebuild.
See my comment in bug 81416.
