The block againt gtk-thinice-engine is gnome-themes 2.6 also blocks the gtk+ 1.x version... it should only be blocks >= 2.0...
this is really simple to fix... gnome-themes 2.6.x doesnt provide anything for the gtk 1.x theme.. please just fix the dep... this is especially annoying the new portage that complains about blockers even between already installed packages when doing emerge -uUD world..
i'm not sure.. gtk-engines-thinice is still using the gtk-engines eclass instead of the new gtk-engines2 eclass. I'm not sure if this is deliberate. liquidx really should really say something here.
at the very least.. gtk-engines-thinice-1.0.4 and gnome-themes-2.6.1 have 0 file in common on my system.. because gnome-themes-2.6.1 does not provide a gtk+1 theme..
there is no reason why any ebuild should be using the old gtk-engines eclass .. i'll take a look at this
ping ping, this is still not fixed changing RDEPEND to RDEPEND=">=x11-libs/gtk+-2 >=x11-themes/gtk-engines-2.2.0 !>=x11-themes/gtk-engines-thinice-2 !>=x11-themes/gtk-engines-lighthouseblue-2 !>=x11-themes/gtk-engines-crux-2 !>=x11-themes/gtk-engines-mist-2" seems to be perfectly fine, I don't know if the other than thinice have -1 versions, but i got carried away a bit.
something happening with this? Its really annoying having to unmerge this before doing emerge -uD world (because it complains about it blocking) only to have it being installed again at the end of the emerge.
this bug still exists with gnome-themes-2.8.0. Is there really any reason this isn't being worked on? The above fix works fine, and allows you to cleanly use the gtk-1.x thinice ebuild along with the gtk-2.x version included with gnome-themes. For comment #6: there's no reason to do that, just fix the ebuild according to the directions above and stick it in your portage_overlay. Once this is fixed you can just remove it from overlay. After it's in there, un-merge gtk-engines-thinice-2*, and install gtk-engines-thinice-1.0.4 for gtk1 thinice.
Created attachment 44039 [details, diff] patch that fixes this status report here? this is such a simple fix. attached is a patch which will fix it, though it'd probably take me longer to patch it then it would to simply edit the thing by hand....
Comment on attachment 44039 [details, diff] patch that fixes this >--- gnome-themes-2.8.0.ebuild 2004-11-11 22:15:47.000000000 -0500 >+++ /usr/local/portage/x11-themes/gnome-themes/gnome-themes-2.8.0.ebuild 2004-11-16 00:54:17.119944026 -0500 >@@ -16,7 +16,7 @@ > > RDEPEND=">=x11-libs/gtk+-2 > >=x11-themes/gtk-engines-2.2.0 >- !x11-themes/gtk-engines-thinice >+ !>=x11-themes/gtk-engines-thinice-2 > !x11-themes/gtk-engines-lighthouseblue > !x11-themes/gtk-engines-crux > !x11-themes/gtk-engines-mist
oops, I tried to remove the * at the end as it's not needed, but something went a little odd there..
2 months later...still no fix?
this is a bit ridiculous, why hasn't anything been done about this? It's almost 5 months now.
with gnome 2.6.10 this bug now applies to gtk-engines instead of gnome themes. Can someone PLEASE fix this already? It's getting ridiculous.
*** Bug 91634 has been marked as a duplicate of this bug. ***
It is annoying me too. Shouldn't this be a simple fix.
Ran into this on my friend
Ran into this on my friend´s desktop today. *sigh* Guys, would someone from the Gnome herd kindly spare his undoubtedly precious 5 seconds to finally get rid of this trivial bug? It´s been here for over one year and it´s really ridiculous. Or shall we wait until all versions <2.10 get purged from portage tree and this bug will become pointless? :-p Thanks!
The fix has been committed. Thank you all for your help. I sincerely apologise for any inconveniences caused by this. Ideally, this kind of bugs should get fixed much quicker, but as you know, we are all volunteers here with limited resources (mainly time), and while we try to do our best taking care of bugs by their priority, there's so much we can do.
(In reply to comment #17) > The fix has been committed. Wow, thanks! :-)
the fix that was comitted only applies to gnome 2.8 and below. This isn't fixed for gnome 2.10, which moved this block of thinice from gnome-themes to gtk-engines, however it's the same exact thing, just the block is in gtk-engines now, as I mentioned already.
Thanks for the notice. gtk-engines includes the fix now too.
