Summary: | [PATCH] dev-python/pygobject-2.18.0 installation fails with sys-apps/coreutils-7.4 and sys-devel/automake-1.11 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin Väth <martin> |
Component: | [OLD] Development | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | QA | Keywords: | Inclusion |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | FreeBSD | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 319443 | ||
Attachments: | Patch which removes the duplicate line from codegen/Makefile.am |
Description
Martin Väth
2009-07-31 17:37:46 UTC
Created attachment 199750 [details, diff]
Patch which removes the duplicate line from codegen/Makefile.am
The patch has to be applied before eautoreconf, of course.
What version of sys-apps/coreutils do you actually mean? Also post the output of `emerge --info`. I mean coreutils-2.18 as written in the summary. Since apparently you cannot reproduce it, I checked and you are right that (currently) the problem only occurs if WANT_AUTOMAKE=1.11 is in the environment: The current autotools eclass otherwise defaults to WANT_AUTOMAKE=1.10, and automake-1.10 does not accumulate several files to one install command (so the duplicate target is just tacitly copied redundantly). Nevertheless that the target defsgen.py is duplicate in codegen/Makefile.am is a real bug (even if with automake-1.10 it "only" has the effect of a redundant copy operation). So consider it as a QA bug which will hit users at least once automake-1.11 will become the default in autotools eclass; I adjust the severity correspondingly. sys-apps/coreutils currently has only the following versions in the tree: 7.1, 7.2, 7.4 Why do you need support for ancient versions? Oh, I confused the version with pygobject's. I mean coreutils-7.4 Fixing it in the summary (and also adding automake-1.11 to the summary). You forgot to reopen this bug... patch looks fine, I'll check if the ebuild can be kept away from eautoreconf In 2.18 without a bump. |