Normally I'd just do some unmerge'ing (and will do in a minute) but thought you might like to know... ~ # emerge -pv --oneshot gnome These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] <=x11-themes/gnome-themes-2.8.2 (is blocking x11-themes/gtk-engines-2.6.2) [blocks B ] <app-admin/gnome-system-tools-1.1.91 (is blocking app-admin/system-tools-backends-1.2.0) [...lots of stuff...] [ebuild U ] gnome-base/gnome-2.10 [2.8.3-r1] -accessibility +cdr -dvdr -hal 0 kB Yes, I know there is a comment in one of the forums about this (not exactly appropriate though (from joem): "the dep is not broken. Any version of gnome-system tools before 1.9.92 doesn't have the backend split out, and will cause collision problems when you merge system-tools-backends. You need to unmerge <gnome-system-tools-1.1.92 in order to upgrade. New totem should be available tomorrow, deps break when using stuff in package.mask" Well, I'm not using package.mask, and things (ideally) shouldn't break like this when I'm using ~x86 because they'll do the same when it goes x86 for thousands of other people :-) Phil
You need to put those ebuilds to /etc/portage/package.unmask - see /usr/portage/profiles/package.mask for a list of things that need to be unmasked.
Erm, put *what* ebuilds into package.unmask? I did an unmerge on the old versions and the new versions are cleanly merging - nothing needs to be explicitly unmasked. The problem was to do with incompatibility between old and new resulting in a block - masking had nothing to do with it. Maybe I've missed the point... (It should be noticed that I did not override any package masking on gnome 2.10 - this is purely a result of somebody putting gnome 2.10 into ~x86 - I therefore shouldn't have to mask/unmask anything to get it to work, should I?) (*And* I'm not convinced that this was an "INVALID" bug report - the problem exists/existed and requires manual intervention to fix.)
Comment #2: You are mixing arch, ~arch and package.masked ebuilds, this will _never_ work without manual intervention and is not a bug(tm) Any of the following need to be put in package.unmask if you have earlier version installed and want to upgrade to gnome-2.10. Alternatively, you can unmerge them. # Joe McCann <joem@gentoo.org> (30 April 2005) #Gnome-2.10.1 mask >=www-client/epiphany-extensions-1.6.3 >=www-client/epiphany-1.6.3 >=gnome-base/gnome-2.10.1 >=gnome-base/gnome-light-2.10.1 >=gnome-base/gnome-volume-manager-1.2.1 >=gnome-base/gnome-vfs-2.10.1 >=gnome-base/control-center-2.10.1 >=gnome-base/eel-2.10.1 >=gnome-base/nautilus-2.10.1 >=gnome-extra/gnome-media-2.10.2 >=media-gfx/eog-2.10.0 >=app-arch/file-roller-2.10.3 >=gnome-extra/gcalctool-5.5.42 >=app-editors/gedit-2.10.2 >=gnome-base/gnome-desktop-2.10.1 >=gnome-base/gnome-applets-2.10.1 >=gnome-base/gnome-panel-2.10.1 >=gnome-base/gnome-menus-2.10.1 >=x11-themes/gtk-engines-2.6.3 >=x11-themes/gnome-themes-2.10.1 >=gnome-base/libgnomeprint-2.10.3 >=gnome-base/libgnomeprintui-2.10.2 >=gnome-extra/gnome-utils-2.10.1 >=gnome-extra/gnome-games-2.10.1 >=gnome-base/libgtop-2.10.1 >=gnome-extra/gnome-system-monitor-2.10.1 >=x11-wm/metacity-2.10.1 >=x11-libs/vte-0.11.13 >=gnome-extra/nautilus-cd-burner-2.10.1 >=x11-themes/gnome-backgrounds-2.10.1 >=gnome-base/gnome-menus-2.10.1 #evolution mask >=gnome-extra/evolution-data-server-2.2.2 >=mail-client/evolution-2.2.2 >=gnome-extra/evolution-webcal-2.2.2 >=gnome-extra/gal-2.4.2 #accessibility pkgs #End of gnome-2.10 mask
Err, sorry for this, I completely missed that gnome-2.10 is already in ~arch and not in package.mask. I should get some sleep. Anyway - there is no gnome-system-tools-1.1.91 in portage, only 1.2.0 (please emerge sync). But gtk-engines-2.6.2 dependency seems indeed wrong, blocks all but package.masked versions of gnome-themes. Reopened.
*laugh* Good night... The gnome-system-tools was emerged quite some time back - dunno why I didn't get prompted for upgrade/downgrade - maybe it was orphaned from world. Anyway, after getting rid of it and the gnome-themes blocker, I now have a gnome 2.10 fully installed. Phil
This is not a bug..as I explained earlier some of the files these packages install have been moved into other packages and thus they can't both be installed at the same time(so they block one another) This is how we handle conflicting packages via portage and yes it does involve manual unmerging because we don't remove stuff without asking first.
