| Summary: | dev-vcs/mercurial-9999: installation fails with 'dodoc: PKG-INFO does not exist' | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Nikolaj Šujskij <skrattaren> |
| Component: | Current packages | Assignee: | Dirkjan Ochtman (RETIRED) <djc> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | arfrever.fta, polynomial-c |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Full dev-vcs/mercurial-9999 build.log | ||
Fixed in mercurial-2.4.1-r2, 2.4.2 and -9999. Thanks for the analysis. PKG-INFO is some distutils metadata, not any documentation. dodoc should never be used to install PKG-INFO, so the following change should be applied in non-9999 ebuilds: - dodoc CONTRIBUTORS PKG-INFO README doc/*.txt || die + dodoc CONTRIBUTORS README doc/*.txt || die |
Created attachment 333846 [details] Full dev-vcs/mercurial-9999 build.log % emerge -pqv '=dev-vcs/mercurial-9999' [ebuild R ] dev-vcs/mercurial-9999 USE="zsh-completion -bugzilla -doc% -emacs -gpg {-test} -tk" ... * Generating '/usr/bin/hg' wrapper script * Converting shebang in 'contrib/hg-ssh' !!! dodoc: PKG-INFO does not exist dodoc failed * ERROR: dev-vcs/mercurial-9999 failed (install phase): * (no error message) I tried to experiment with dropping PKG-INFO from ebuild, but dodoc fails with other errors then. ANyway, I don't think mercurial needs IUSE=doc": 1. Mercurial's `doc` make target compiles *user* documentation like manpages, which everyone needs 2. Released versions have those docs compiled, thus re-building them is unneeded 3. "Mercurial from mercurial" needs user docs anyway (see 1), so documentation should de built unconditionally.