I have set ACCEPT_KEYWORDS="x86". As I wanted to install pysoulseek I had two options: do an ACCEPT_KEYWORDS="~x86" emerge pysoulseek or do an emerge pysoulseek-1.2.0-r2.ebuild in the apropriate dir. I did the latter, as that variant installs less unstable packages. An emerge -p displayed the dependencies and pysoulseek proper to be newly installed. After the actual emerge was done installing pysoulseek and its dependencies, all over a sudden I saw xfree being unmerged. I am startled how such a strange thing can possibly happen. Reproducible: Didn't try Steps to Reproduce: 1. emerge /usr/portage/net-p2p/pysoulseek/pysoulseek-1.2.0-r2.ebuild 2. 3. Actual Results: afterpysoulseek was installed, xfree was unmerged and downgraded to xfree-3.4k-r1 Expected Results: no unmerging of xfree my emerge.log. The worrying bit is the unmerging xfree-4.3.0-r2. I remerged it manually, afterwards. 1055448336: Started emerge on: Jun 12, 2003 22:05:36 1055448336: *** emerge pysoulseek-1.2.0-r2.ebuild 1055448336: >>> emerge (1 of 7) dev-python/PyOpenGL-2.0.0.44 to / 1055448336: === (1 of 7) Cleaning (/usr/portage/dev-python/PyOpenGL/PyOpenGL-2.0.0.44.ebuild) 1055448336: === (1 of 7) Compiling/Merging (/usr/portage/dev-python/PyOpenGL/PyOpenGL-2.0.0.44.ebuild) 1055448418: === (1 of 7) Post-Build Cleaning (/usr/portage/dev-python/PyOpenGL/PyOpenGL-2.0.0.44.ebuild) 1055448418: >>> AUTOCLEAN: dev-python/PyOpenGL 1055448418: --- AUTOCLEAN: Nothing unmerged. 1055448418: ::: completed emerge (1 of 7) dev-python/PyOpenGL-2.0.0.44 to / 1055448418: >>> emerge (2 of 7) dev-db/unixODBC-2.0.6 to / 1055448418: === (2 of 7) Cleaning (/usr/portage/dev-db/unixODBC/unixODBC-2.0.6.ebuild) 1055448418: === (2 of 7) Compiling/Merging (/usr/portage/dev-db/unixODBC/unixODBC-2.0.6.ebuild) 1055448741: === (2 of 7) Post-Build Cleaning (/usr/portage/dev-db/unixODBC/unixODBC-2.0.6.ebuild) 1055448742: >>> AUTOCLEAN: dev-db/unixODBC 1055448742: --- AUTOCLEAN: Nothing unmerged. 1055448742: ::: completed emerge (2 of 7) dev-db/unixODBC-2.0.6 to / 1055448742: >>> emerge (3 of 7) x11-libs/wxGTK-2.4.0 to / 1055448742: === (3 of 7) Cleaning (/usr/portage/x11-libs/wxGTK/wxGTK-2.4.0.ebuild) 1055448744: === (3 of 7) Compiling/Merging (/usr/portage/x11-libs/wxGTK/wxGTK-2.4.0.ebuild) 1055449367: === (3 of 7) Post-Build Cleaning (/usr/portage/x11-libs/wxGTK/wxGTK-2.4.0.ebuild) 1055449368: >>> AUTOCLEAN: x11-libs/wxGTK 1055449368: --- AUTOCLEAN: Nothing unmerged. 1055449368: ::: completed emerge (3 of 7) x11-libs/wxGTK-2.4.0 to / 1055449368: >>> emerge (4 of 7) dev-python/wxPython-2.4.0.2 to / 1055449368: === (4 of 7) Cleaning (/usr/portage/dev-python/wxPython/wxPython-2.4.0.2.ebuild) 1055449368: === (4 of 7) Compiling/Merging (/usr/portage/dev-python/wxPython/wxPython-2.4.0.2.ebuild) 1055450084: === (4 of 7) Post-Build Cleaning (/usr/portage/dev-python/wxPython/wxPython-2.4.0.2.ebuild) 1055450084: >>> AUTOCLEAN: dev-python/wxPython 1055450084: --- AUTOCLEAN: Nothing unmerged. 1055450084: ::: completed emerge (4 of 7) dev-python/wxPython-2.4.0.2 to / 1055450084: >>> emerge (5 of 7) media-libs/pyogg-1.1 to / 1055450084: === (5 of 7) Cleaning (/usr/portage/media-libs/pyogg/pyogg-1.1.ebuild) 1055450085: === (5 of 7) Compiling/Merging (/usr/portage/media-libs/pyogg/pyogg-1.1.ebuild) 1055450089: === (5 of 7) Post-Build Cleaning (/usr/portage/media-libs/pyogg/pyogg-1.1.ebuild) 1055450089: >>> AUTOCLEAN: media-libs/pyogg 1055450089: --- AUTOCLEAN: Nothing unmerged. 1055450089: ::: completed emerge (5 of 7) media-libs/pyogg-1.1 to / 1055450089: >>> emerge (6 of 7) media-libs/pyvorbis-1.1 to / 1055450089: === (6 of 7) Cleaning (/usr/portage/media-libs/pyvorbis/pyvorbis-1.1.ebuild) 1055450089: === (6 of 7) Compiling/Merging (/usr/portage/media-libs/pyvorbis/pyvorbis-1.1.ebuild) 1055450093: === (6 of 7) Post-Build Cleaning (/usr/portage/media-libs/pyvorbis/pyvorbis-1.1.ebuild) 1055450093: >>> AUTOCLEAN: media-libs/pyvorbis 1055450093: --- AUTOCLEAN: Nothing unmerged. 1055450093: ::: completed emerge (6 of 7) media-libs/pyvorbis-1.1 to / 1055450093: >>> emerge (7 of 7) net-p2p/pysoulseek-1.2.0-r2 to / 1055450093: === (7 of 7) Cleaning (/usr/portage/net-p2p/pysoulseek/pysoulseek-1.2.0-r2.ebuild) 1055450093: === (7 of 7) Compiling/Merging (/usr/portage/net-p2p/pysoulseek/pysoulseek-1.2.0-r2.ebuild) 1055450097: === (7 of 7) Post-Build Cleaning (/usr/portage/net-p2p/pysoulseek/pysoulseek-1.2.0-r2.ebuild) 1055450097: >>> AUTOCLEAN: net-p2p/pysoulseek 1055450097: --- AUTOCLEAN: Nothing unmerged. 1055450097: ::: completed emerge (7 of 7) net-p2p/pysoulseek-1.2.0-r2 to / 1055450097: *** Finished. Cleaning up... 1055450102: === Unmerging... (x11-base/xfree-4.3.0-r2) 1055450314: >>> unmerge success: x11-base/xfree-4.3.0-r2 1055450314: *** exiting successfully. 1055450314: *** terminating. 1055450328: Started emerge on: Jun 12, 2003 22:38:48 1055450328: *** emerge search xfree 1055450329: *** terminating. 1055450373: *** terminating. 1055450379: *** terminating. 1055450440: *** terminating. 1055450448: Started emerge on: Jun 12, 2003 22:40:48 1055450448: *** emerge xfree 1055450448: >>> emerge (1 of 1) x11-base/xfree-4.3.0-r2 to / 1055450448: === (1 of 1) Cleaning (/usr/portage/x11-base/xfree/xfree-4.3.0-r2.ebuild) 1055450448: === (1 of 1) Compiling/Merging (/usr/portage/x11-base/xfree/xfree-4.3.0-r2.ebuild) 1055454105: === (1 of 1) Updating world file (/usr/portage/x11-base/xfree/xfree-4.3.0-r2.ebuild) 1055454105: === (1 of 1) Post-Build Cleaning (/usr/portage/x11-base/xfree/xfree-4.3.0-r2.ebuild) 1055454120: >>> AUTOCLEAN: x11-base/xfree 1055454125: === Unmerging... (x11-base/xfree-3.4k-r1) 1055454129: >>> unmerge success: x11-base/xfree-3.4k-r1 1055454129: ::: completed emerge (1 of 1) x11-base/xfree-4.3.0-r2 to / 1055454129: *** Finished. Cleaning up... 1055454133: *** exiting successfully.
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.
