On Friday 19 January 2007 15:26, Stefan G. Weichinger wrote: > it's a while now since I get errors when portage tries to unmerge > dev-libs/glib-2.10.3 (for example when doing "emerge -avu world). [SNIP] > I added it to package.keywords for a try, as I have this on my desktop > machine without these problems. But it didn't solve this issue.
This is an unmerge problem not an emerge problem. The only thing that it might help emerging is another version of portage. > It doesn't make any real problems but it's not set up the correct way > when throwing errors ;) Your system is in an illegal state as you have two versions of glib in the same slot. > Any hints on this? Make sure that you have the latest portage (either latest stable or latest ~arch) i.e. run `emerge -u portage`. If that doesn't fix it I think you should file a bug against portage at bugs.gentoo.org. In the future as well as on bugs.gentoo.org please include `emerge --info` with portage tracebacks. -- Bo Andresen
pgp8Xo3Hm38Ed.pgp
Description: PGP signature