the same happens for glib-2.32.2, glib-2.32.1 as http://forums.gentoo.org/viewtopic-t-896624-highlight-.html only glib-2.28.8 from poly-c can be used as a start point to install glib. Reproducible: Always
nah, this was solved months ago in Portage already. but it's entirely different issue if you have broken the dev-util/pkgconfig installation by uninstalling dev-libs/glib for some reason (uninstalling glib is a very bad idea). in that case you must also, emerge -C "virtual/pkgconfig dev-util/pkgconfig" to ensure *neither* to emerge them from scratch
(In reply to comment #1) > nah, this was solved months ago in Portage already. but it's entirely > different issue if you have broken the dev-util/pkgconfig installation by > uninstalling dev-libs/glib for some reason (uninstalling glib is a very bad > idea). in that case you must also, > > emerge -C "virtual/pkgconfig dev-util/pkgconfig" to ensure *neither* to > emerge them from scratch the update failed for lib files confliction. then those lib files were removed. then emerge glib to update it again still failed. then emerge -C glib which removed both slot 1 and slot 2 packages, and emerge -C pkgconfig , update failed again. the emerge -C virtual/pkgconfig was neglected.
emerge -C pkgconfig would only pick the actual package, dev-util/pkgconfig, it wouldn't unemerge both dev-util/pkgconfig AND virtual/pkgconfig this is actually the way portage is supposed to work and this is the first time i've seen it causing any 'problems' but since the 'problem' here is caused by mistakenly uninstalling glib, thus installed pkg-config because pkg-config is using glib, this is deemed to be an 'user error', like it or not so after becoming familiar with the fact that PKGCONFIG IS LINKING AGAINST GLIB, and UNEMERGING GLIB WILL BREAK PKGCONFIG... recovering the system... emerge -C dev-util/pkgconfig virtual/pkgconfig emerge -1 dev-util/pkgconfig the later command will also first install the dev-libs/glib as a dependency
*** This bug has been marked as a duplicate of bug 385561 ***
