* Generating docs as requested... usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'pudge' * * ERROR: dev-python/elixir-0.5.2 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2440: Called die * The specific snippet of code: * PYTHONPATH=. "${python}" setup.py pudge || die "generating docs failed"; * The die message: * generating docs failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-python/elixir-0.5.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-python/elixir-0.5.2/temp/environment'. *
Created attachment 151941 [details] elixir-0.5.2-x86_64-emergeinfo_buildlog
Thanks, fixed in CVS.
For future reference, if "{python} setup.py pudge" doesn't build the documentation, you can add this line before it and it will modify setup.cfg: ${python} setup.py addcommand -p buildutils.pudge_command
(In reply to comment #3) > For future reference, if "{python} setup.py pudge" doesn't build the > documentation, you can add this line before it and it will modify setup.cfg: > > ${python} setup.py addcommand -p buildutils.pudge_command > A few questions here: 1. Does the CVS have any bearing upon portage? (How long before anyone can emerge this package without any errors present? Unless an updated version is in portage, this should have remained open.) 2. Where exactly is anyone supposed to put the code you gave for fixing python documentation? Is there a common location (/etc) where this can be set for all python packages? Shingoshi
(In reply to comment #4) > A few questions here: > 1. Does the CVS have any bearing upon portage? (How long before anyone can > emerge this package without any errors present? Unless an updated version is in portage, this should have remained open.) We use CVS to commit, then the rsync mirrors pick it up, so you should have it the next time you 'emerge sync' (give or take an hour). > 2. Where exactly is anyone supposed to put the code you gave for fixing python > documentation? Is there a common location (/etc) where this can be set for all > python packages? > That was a note to anyone else trying to fix an ebuild that uses pudge (it'll be in the elixir ebuild next time you sync). Pudge is a new documentation system and it isn't obvious how to build docs using it sometimes. I'll be going through all the ebuilds that use it and test to see if they need that magic line.
Thank you for your clarification. And now I have another question. Being that I'm reporting many bugs for which fixes are sometimes made available before that magic 24 hour limit on re-syncing is permitted, how likely is it that I would be restricted from rsync for getting packages that my reports have directly contributed to fixing? Do I need some kind of (prior) clearance to avoid a problem here? I'm asking, because I'm building many many packages at a time. And that high volume leads to many bug reports as well. So I'm just asking. Shingoshi
Thank you for the fix. It installed without trouble now. Shingoshi
(In reply to comment #3) > For future reference, if "{python} setup.py pudge" doesn't build the > documentation, you can add this line before it and it will modify setup.cfg: > > ${python} setup.py addcommand -p buildutils.pudge_command > I get the same error when trying to emerge pylons
