Summary: | xfree automatically unmerged after emerging pysoulseek for no aparent reason | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Peter Lietz <p.lietz> |
Component: | Unclassified | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED FIXED | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Peter Lietz
2003-06-12 16:34:33 UTC
actually, xfree is still on your system happily doing its thing. What happened was that media-libs was removed from the tree as xfree itself provides that set of libraries. Hence media-libs/xpm-3.4k-r1 was "moved" to xfree So the clean up was of the renamed xpm-3.4k-r1 as you can see/ Thanks for the prompt answer! There are just three things I don't understand: 1. If xfree-4.3.0-r2 was still installed after the pysoulseek install (and before I remerged it), why did emerge -s xfree show x11-base/xfree-3.4k-r1 then? 2.Why did emerge -up xfree propose an upgrade from x11-base/xfree-3.4k-r1 to xfree-4.3.0-r2? 3. What is x11-base/xfree-3.4k-r1 anyway? There is no ebuild of that name. If you find the time, I'd be greatful for an explanation or a pointer to such. ps: http://forums.gentoo.org/viewtopic.php?t=60192 deals with a related problem. more people have this problem as seen on the forum and, according to them, xfree is actually removed, so this is a major bug. I'm therefore reopening it. I think this bug qualifies as critical or blocker. Is there any reason why portage insists that media-libs/xpm is now x11-base/xfree ? It does not appear in any of the /usr/portage/profile/updates . For the time being, the problem seems to be worked-around. Also, why is the dummy xpm ebuild all-out unstable? this was a bit of a snafu --- xpm was deprecated from the tree and the move code worked a little better than I expected :/ it's been removed, since then (the move directive) but I'm afraid xfree will have to be remerged closing as the issue is nothing that can be done about at this point -- it hit a few users -- and my apologies for that. |