it looks like pango has some files conflict with gir-repository Reproducible: Always Steps to Reproduce: 1. emerge -av dev-libs/gir-repository 2. 3. Actual Results: * atk is disabled, but gtk needs atk. Auto-enabling... * pango is disabled, but gtk needs pango. Auto-enabling... * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). Once again, please do NOT file * a bug report unless you have completely understood the above message. * * Detected file collision(s): * * /usr/lib/girepository-1.0/PangoCairo-1.0.typelib * /usr/lib/girepository-1.0/Pango-1.0.typelib * /usr/lib/girepository-1.0/PangoXft-1.0.typelib * /usr/lib/girepository-1.0/PangoFT2-1.0.typelib * /usr/share/gir-1.0/PangoCairo-1.0.gir * /usr/share/gir-1.0/PangoXft-1.0.gir * /usr/share/gir-1.0/PangoFT2-1.0.gir * /usr/share/gir-1.0/Pango-1.0.gir * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * x11-libs/pango-1.28.0 * /usr/lib/girepository-1.0/Pango-1.0.typelib * /usr/lib/girepository-1.0/PangoCairo-1.0.typelib * /usr/lib/girepository-1.0/PangoFT2-1.0.typelib * /usr/lib/girepository-1.0/PangoXft-1.0.typelib * /usr/share/gir-1.0/Pango-1.0.gir * /usr/share/gir-1.0/PangoCairo-1.0.gir * /usr/share/gir-1.0/PangoFT2-1.0.gir * /usr/share/gir-1.0/PangoXft-1.0.gir * * Package 'dev-libs/gir-repository-0.6.5' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message. $ emerge --info Portage 2.1.8.3 (default/linux/x86/10.0, gcc-4.4.3, glibc-2.11.2-r0, 2.6.34-gentoo i686) ================================================================= System uname: Linux-2.6.34-gentoo-i686-Intel-R-_Pentium-R-_Dual_CPU_T2370_@_1.73GHz-with-gentoo-2.0.1 Timestamp of tree: Wed, 09 Jun 2010 09:15:01 +0000 distcc 3.1 i686-pc-linux-gnu [disabled] ccache version 2.4 [enabled] app-shells/bash: 4.1_p7 dev-java/java-config: 2.1.11 dev-lang/python: 2.6.5-r2, 3.1.2-r3 dev-python/pycrypto: 2.1.0 dev-util/ccache: 2.4-r8 dev-util/cmake: 2.8.1-r2 sys-apps/baselayout: 2.0.1 sys-apps/openrc: 0.6.1-r1 sys-apps/sandbox: 2.2 sys-devel/autoconf: 2.13, 2.65 sys-devel/automake: 1.9.6-r3
You're probably using pango from Keruspe overlay, I'm totally reworking that, I'll add blockers in a few moments, sorry about that, should have been fixed a while ago (If this is your case, I think you can close it, it will be fixed today)
full emerge --info please.
downgrade pango fix this issue (In reply to comment #1) > You're probably using pango from Keruspe overlay, I'm totally reworking that, > I'll add blockers in a few moments, sorry about that, should have been fixed a > while ago > (If this is your case, I think you can close it, it will be fixed today) >
