Summary: | dev-python/anyvc-0.3.7.1: "ImportError: No module named hgdistver" when building docs | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Nikolaj Šujskij <skrattaren> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Full dev-python/anyvc-0.3.7.1 build.log |
Description
Nikolaj Šujskij
2012-06-28 11:40:49 UTC
this http://pypi.python.org/pypi/hgdistver/ is why. It requires this new dep not in portage Indeed. So maintainer should either add it, or mask/remove USE-flag for the time being. Unnecessary build-time dependency on hgdistver can be easily avoided. See ebuild from Progress Overlay: http://code.google.com/p/gentoo-progress/source/browse/overlays/progress/dev-python/anyvc/anyvc-0.3.7.1-r1000.ebuild (In reply to comment #3) > Unnecessary build-time dependency on hgdistver can be easily avoided. Indeed, shamelessly stolen src_prepare() fseems to fix the issue. Thanks! > See Also: bug #424695
Er... How these two bugs are related?
looks like I missed by again 1 ( in a vertical list) No. 424681 I will refrain from putting it in also. It's clearly related; building docs in anyvc. (In reply to comment #7) > Issue resolved according to comment 3 But it ain't. Nobody has applied that patch to anyvc in Portage tree, I had simply edited local ebuild to get it compiled fine. Meanwhile, hgdistver is in Portage now. Reopened. (In reply to comment #8) > (In reply to comment #7) > > Issue resolved according to comment 3 > But it ain't. Nobody has applied that patch to anyvc in Portage tree, I had > simply edited local ebuild to get it compiled fine. > > Meanwhile, hgdistver is in Portage now. > > Reopened. Nikolaj Sjujskij The raison d'etre of this was the failure to build using USE="doc mercurial". anyvc # USE="doc mercurial" ebuild anyvc-0.3.7.1.ebuild clean install * Generating '/usr/bin/vc' wrapper script >>> Completed installing anyvc-0.3.7.1 into /var/tmp/portage/dev-python/anyvc-0.3.7.1/image/ However this is without distver emerged. The patch from the progress overlay in src_prepare is double barelled. It appears that fixing the use of the unsupported theme option which needed fixing anyway has captured the build docs error. anyvc # grep hgdistver /var/tmp/portage/dev-python/anyvc-0.3.7.1/temp/build.log Installed /var/tmp/portage/dev-python/anyvc-0.3.7.1/work/anyvc-0.3.7.1/hgdistver-0.16-py2.7.egg warning: no files found matching 'hgdistver.py' making a mockery of the need for the distver package. For now the fix of the unsupported themes had been added, therefore holding off re-closing until you or anyone else can test and confirm the above described status. I'm sorry, Ian, but I have just sync'ed tree and run `emerge -a1 anyvc` and it fails just as described in my first report. I have no idea why it succeeds on your box, though. we have at at least possible confounding causes here 11:27:45 04:16:16 Probably enough time to hit the mirrors. remember I said the patch from preogress is double barrelled. I have only added the second barrel. Fistly check that you have at least an updated ebuild with the entry I add in src_prepare. Seeing my test was effective with just that, I saw no need for the rest. Re-add the rest and retry, and I suppose that's sufficient to include the second barrel. Hm... Strange thing. I gave it two shots on two different boxes, and here's the results: * on my laptop which has gone offline after sync and fetch, building anyvc was requiring network (!). Unfortunately I cannot provide logs or anything like that due to subsequent hardware failure * on my workstation I have just the same error about hgdistver being absent :( Yes, I've checked for ChangeLog entry and ebuild updates. |