Here's a template for the dependency hell I just encountered. It's mass confusion imo,but still early during the introduction of f-spot-0.5*.. so might be cleared-up soon. f-spot-0.5.0.3 requires dev-dotnet/gtk-sharp-2.12 But, glade-sharp blocks gtk-sharp-2.12.6-r1! Reproducible: Always [blocks B ] dev-dotnet/glade-sharp ("dev-dotnet/glade-sharp" is blocking dev-dotnet/gtk-sharp-2.12.6-r1) Total: 12 packages (5 upgrades, 1 downgrade, 5 new, 1 reinstall), Size of downloads: 4,705 kB Conflict: 2 blocks (2 unsatisfied) !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: dev-dotnet/gtk-sharp:2 ('ebuild', '/', 'dev-dotnet/gtk-sharp-2.10.0', 'merge') pulled in by ('ebuild', '/', 'dev-dotnet/glade-sharp-2.10.0', 'merge') ('ebuild', '/', 'dev-dotnet/gtk-sharp-2.12.6-r1', 'merge') pulled in by ('installed', '/', 'net-dns/avahi-0.6.22-r1', 'nomerge') ('installed', '/', 'dev-dotnet/evolution-sharp-0.17.4', 'nomerge') ('installed', '/', 'dev-libs/gmime-2.2.23', 'nomerge') (and 6 more)
I'm seeing this too. I think the problem here is glade-sharp is out of date... bump for a new ebuild <.<
This one is mine. emerge -C glade-sharp, gtk-sharp-2.12.6-r1 with the use flag "glade" provides this now.
On a recent portage sync today, the glade use flag for gtk-sharp disappeared. Not only this, but glade-sharp will still get yanked in. I'll try working on your solution for another day or so.
..never mind, the glade use flag is still there... posted this before switching virtual terminals & checking... duh.
Still getting this after ensuring building with glade use flag and emerge -C glade-sharp: [ebuild U ] dev-dotnet/gtk-sharp-2.12.6-r1 [2.10.0] USE="glade%* -doc" 0 kB [ebuild NS ] dev-dotnet/gtk-sharp-1.0.10 [2.10.0] 0 kB [blocks B ] dev-dotnet/glade-sharp ("dev-dotnet/glade-sharp" is blocking dev-dotnet/gtk-sharp-2.12.6-r1) So I masked glade-sharp and did another emerge -uDNpv world and found glade-sharp being pulled in by the following packages: (dependency required by "dev-dotnet/gconf-sharp-2.16.0" [installed]) (dependency required by "app-misc/tomboy-0.10.2" [installed]) and some more screwing around: # emerge -uDNpv world !! ! All ebuilds that could satisfy "=dev-dotnet/glade-sharp-2.10*" have been masked. !!! One of the following masked packages is required to complete your request: - dev-dotnet/glade-sharp-2.10.0 (masked by: package.mask) For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. (dependency required by "dev-dotnet/gconf-sharp-2.16.0" [installed]) (dependency required by "app-misc/tomboy-0.10.2" [ebuild]) (dependency required by "gnome-base/gnome-2.22.3" [installed]) (dependency required by "@world" [argument] Once gconf-sharp-2.24* is unmasked, it wants to bring in the whole gnome-2.24* tree, in which, gnome wants tomboy installed, which depends on glade-sharp in it's earlier version. Guess this is just one of the side effects of keeping newer versions of gnome masked for longer periods of time! Think many others are going to run into this as they want to upgrade to the latest f-spot, which depends on the latest mono, in which depends on gtk-sharp... which depends on gnome-2.24* lol
I'm not sure how to get around this.
um. unmasking gnome-2.24* lol. or, it seems to be a dep issue between glade-sharp & gtk-sharp. (I'm not too hip with mono, but really enjoy f-spot. It suits wonderfully for managing a large photo collection.) I'm reverting to f-spot-4*. Also, downgrading from f-spot-5* depends seems to have broken mono-addins & mono-tools during their compilation. God, what a nightmare.
Your basic problem here is mixing unstable and stable, I think. emerge -C glade-sharp USE="glade" emerge -1 gtk-sharp Should actually solve this if you're on ~arch. And, gnome-2.24 isn't masked, it's just not stable yet.
Exactly. Upgrading to f-spot-5* depends on unstable mono packages which then wants to bring in the whole unstable branch of gnome-2.24*. :-/ So, is gnome-2.24* going stable anytime soon? (...marking as fixed :-/ )
(In reply to comment #8) > Your basic problem here is mixing unstable and stable, I think. > emerge -C glade-sharp > USE="glade" emerge -1 gtk-sharp > Should actually solve this if you're on ~arch. > > And, gnome-2.24 isn't masked, it's just not stable yet. > That doesn't solve it. The problem remains.
In comment #9, I briefly & roughly described the dependency graph. I just spent the day marking gnome-2.24 stable on my system. After placing around 133 packages into package.keywords, emerge -uDNpv world does list everything for install correctly. The only thing to test, is to see if gtk-sharp (glade) does satisfy the dependency completely & correctly for f-spot. (Matthew, are you saying you have gnome-2.24 marked stable on my platform?)
I'll be more specific: I'm running ~amd64, so yes I have Gnome 2.24 & friends This whole thing came about in my usual emerge -DuN world, with the block as follows: [ebuild U ] dev-db/sqlite-3.6.6.2 [3.6.2] [ebuild U ] dev-libs/xmlrpc-c-1.16.06 [1.16.04] [ebuild U ] sys-fs/udev-135-r1 [133] [ebuild N ] x11-themes/sound-theme-freedesktop-0.2 [ebuild U ] x11-misc/util-macros-1.2.0 [1.1.6-r1] [ebuild U ] x11-proto/inputproto-1.5.0 [1.4.4] [ebuild U ] dev-dotnet/libgdiplus-2.0 [1.9] [ebuild U ] dev-lang/mono-2.0.1 [1.9.1] [ebuild UD] dev-dotnet/gtk-sharp-2.10.2 [2.12.6-r1] [ebuild N ] dev-dotnet/glade-sharp-2.10.0 [ebuild U ] dev-dotnet/art-sharp-2.24.0-r2 [2.16.0] [ebuild U ] net-fs/samba-3.0.33 [3.0.32] [ebuild U ] gnome-base/libgnomeui-2.24.0 [2.22.1] [ebuild U ] dev-dotnet/gnomevfs-sharp-2.24.0-r1 [2.16.0] [ebuild U ] gnome-extra/evolution-data-server-2.24.2 [2.22.3-r1] [ebuild U ] x11-terms/gnome-terminal-2.24.2 [2.24.1] [ebuild U ] gnome-extra/evolution-webcal-2.24.0 [2.21.92] [ebuild U ] mail-client/evolution-2.24.2 [2.22.3.1] [ebuild U ] gnome-base/gnome-settings-daemon-2.24.1-r1 [2.24.1] [ebuild U ] www-client/epiphany-2.24.2.1-r10 [2.24.1-r10] [ebuild U ] dev-libs/soprano-2.1.1 [2.1] [ebuild U ] gnome-base/gnome-volume-manager-2.24.0-r1 [2.24.0] [ebuild R ] gnome-base/gnome-control-center-2.24.0.1 USE="sound*" [ebuild U ] dev-dotnet/gconf-sharp-2.24.0-r1 [2.16.0] [ebuild N ] gnome-extra/gnome-do-0.4.2.0-r2 USE="-debug" [ebuild R ] gnome-extra/gnome-games-2.24.2 USE="(-debug%)" [blocks B ] dev-dotnet/glade-sharp ("dev-dotnet/glade-sharp" is blocking dev-dotnet/gtk-sharp-2.12.6-r1)
cr*p. (in the middle of compiling gnome-2.24 in a last effort) Well, I'll look at it this way, once gnome-2.24 is installed, I'll now have the latest Banshee. ;-) I'll follow-up once I get gnome-2.24 completely installed here. For now, I'll just leave this open.
Ok. I'm getting could emerge world pretends here without blocking. What's probably happening, something is still pulling in glade-sharp. Do the following & then try emerge world to find the offending package: # echo "dev-dotnet/glade-sharp" >> /etc/portage/package.mask Once you find the offending package, either remove it or mark it's later versions stable. Also, I find "rm -rf /usr/portage/local/layman/gnome" && layman -s gnome fixes any errors within the gnome overlay. (Sometimes I find missing files, etc.) As we've said before, gtk-sharp now provides glade-sharp, so glade-sharp should be removed along with any of it's depends. I don't have "dev-dotnet/gtk-sharp glade" in my /etc/portage/package.use here, but you might also try this if you haven't already.
gnome-do and gnome-do-plugins were pulling glade-sharp in my case ... just a tip
eh. new one to me. I've just about finished upgrading to gnome-2.24* to evade this bug. If I get time, I'll publish the list of packages I now have in package.unmask to gentoo-wiki.com so others can have fun with gnome-2.24*. Marking as closed.
(In reply to comment #15) > gnome-do and gnome-do-plugins were pulling glade-sharp in my case ... just a > tip > Took your tip and fixed it. 0.6.1.0 is now in tree.
(In reply to comment #16) > eh. new one to me. > > I've just about finished upgrading to gnome-2.24* to evade this bug. > > If I get time, I'll publish the list of packages I now have in package.unmask > to gentoo-wiki.com so others can have fun with gnome-2.24*. > > > Marking as closed. > even with all these workarounds, still got "gtk-sharp-2.12, but is blocked by glade-sharp" I had to emerge -C gnome, dev-dotnet/gconf-sharp, media-gfx/f-spot, app-misc/beagle to get a working emerge -vaDnu world
