start here # emerge rsync # emerge -pu world Keeps telling me that it want's to emerge gnome-vfs-1.0.5-r3. If I run: # emerge gnome-vfs emerge merges gnome-vfs-2.0.4.1-r0. repeat loop. -------------------------------------------------------------------------- dragon root # emerge -pu --deep world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild UD] gnome-base/gnome-vfs-1.0.5-r3 [2.0.4.1-r0] [ebuild U ] app-office/abiword-1.0.4_pre1-r2 [1.0.4_pre1-r1] [ebuild UD] app-editors/xemacs-21.4.10-r1 [21.4.11_rc1-r0] [ebuild U ] app-admin/gentoolkit-0.1.17-r6 [0.1.17-r5] dragon root # -------------------------------------------------------------------------- The only way to emerge gnome-vfs-1.0.5-r3 is to: # emerge /usr/portage/gnome-base/gnome-vfs/gnome-vfs-1.0.5-r3.ebuild After while successfully emerging gnome-vfs-1.0.5-r3, I get: -------------------------------------------------------------------------- ... various emerge messages ... >>> Regenerating /etc/ld.so.cache... >>> gnome-base/gnome-vfs-1.0.5-r3 merged. gnome-base/gnome-vfs selected: 1.0.5-r2 protected: 1.0.5-r3 2.0.4.1 omitted: none >>> Packages in red are slated for removal. >>> Packages in green will not be removed. >>> Waiting 5 seconds before starting... >>> (Control-C to abort)... >>> Unmerging in: 5 4 3 2 1 >>> Unmerging gnome-base/gnome-vfs-1.0.5-r2... No package files given... Grabbing a set. ... more emerge messages -------------------------------------------------------------------------- When I double check that the emerge has completed successfully, I get: -------------------------------------------------------------------------- dragon root # emerge -pu --deep world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild U ] app-office/abiword-1.0.4_pre1-r2 [1.0.4_pre1-r1] [ebuild UD] app-editors/xemacs-21.4.10-r1 [21.4.11_rc1-r0] [ebuild U ] app-admin/gentoolkit-0.1.17-r6 [0.1.17-r5] dragon root # emerge -p gnome-vfs These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] gnome-base/gnome-vfs-2.0.4.1 dragon root # -------------------------------------------------------------------------- I presume that this behavior is not normal for emerging any package. :-) At least, it doesn't look normal to me. I've gone through this scenario on 3 different machines. If you need the logs etc... just post exactly what you want and I'll add the gzipped attatchments.
actually you could do emerge -pu \<gnome-vfs-2 to update the SLOT that is below gnome-vfs-2.x series this is because portage allows you to have multiple versions installed, and can depend on either. meaning that you can have both gnome-vfs-1.x and 2.x at the same time, and the update should cover that if you specify which to try.
OK - I've now read the relevant portage documentation. However, I think there is still a problem: 'emerge -pu world' reported that it was recommending that gnome-vfs-1.0.5-r3 needed to be emerged. Doing 'emerge -u world' and doing 'emerge gnome-vfs' both did not emerge gnome-vfs-1.0.5-r3. I can't see where the ability to update the SLOT _manually_ is the correct answer for this situation. Note that 'emerge help' does not say anything about updating SLOTs. If you still feel that this 'works as designed', then please close again.
Please also note: after doing the explicit emerge of /usr/portage/gnome-base/gnome-vfs/gnome-vfs-1.0.5-r3.ebuild as I originally described, my results of an 'emerge -s gnome-vfs' search are: --------------------------------------------------------------------------------------------------- dragon root # emerge -s gnome-vfs Searching... [ Results for search key : gnome-vfs ] [ Applications found : 2 ] * gnome-base/gnome-vfs Latest version available: 2.0.4.1-r1 Latest version installed: 2.0.4.1 Size of downloaded files: 814 kB Homepage: http://www.gnome.org/ Description: Gnome Virtual Filesystem * gnome-extra/gnome-vfs-extras Latest version available: 0.99.6 Latest version installed: [ Not Installed ] Size of downloaded files: 727 kB Homepage: http://www.gnome.org/ Description: the Gnome Virtual Filesystem extra libraries dragon root # ---------------------------------------------------------------------------------------------------------- After doing an apparently successful emerge of the 1.0.5-r3 version, it seems to have magically dissappeared. It was my understanding that support for multiple SLOTs occured automatically as needed. Somewhere, something is wrong here. Either 'emerge -pu world' should _not_ have indicated that it wanted to emerge gnome-vfs-1.0.5-r3 to begin with or there is something wrong with how it's being emerged. Of course, this is just my opinion. I will not re-open this again if you decide that it should be closed. I don't seem to be having any problems related to gnome-vfs. Best regards, Guy
emerge -pu world should have shown there was an updated version in the SLOT emerge -u world - would- have updated gnome-vfs-1.0.5-r3 if you had run it, since the -pu showed that it would be installed. But, this is more a portage bug or how portage relays information than anything else. I'm reassigning this to carpaski since he might now better what to do with it, or at least get notice that our users get confused.
Update - this is no longer a problem and can be closed
I believe this has been fixed - changing to resolved - fixed
