Version 0.3.8 of gtk-vnc was released several months ago, 2008-12-07 19:35:04 (GMT). Reproducible: Always
yes yes we know, it's in the gnome overlay
I don't think that is a very good answer really. When is it coming into portage proper? The release was over 3 months ago........
And you could learn some manners when requesting something from people you've never met before. If Gilles said gtk-vnc will go to portage with the rest of Gnome 2.26, then so be it.
Where was it stated that this would be resolved when Gnome 2.26 goes in? I don't follow any gentoo-gnome herd lists, or IRC channels. A package I care about has a dependency on gtk-vnc, and I see that it (gtk-vnc) hasn't been updated despite the new version having been released 3+ months ago. As far as manners go, "Pot, meet Kettle.." Check the bug db for my name. I contribute quite a bit for a non-dev, I rarely ask for something for nothing; and I doubt anyone would say that opening a tracking ticket for a package which needs to be updated is some giant favor to be granted. Sheesh. So, the question remains: when will this get put into portage proper?
jieryn, you've got a reply from the gnome team that they will do it when they mark gnome-2.26 stable. No need for heated reactions or harsh words about a package bump.
Sorry, I meant when gnome-2.26 is *added* to the tree and not when it's marked stable.
Sorry if our answers seemed a bit harsh, we are a bit under-manned to take care of everything. It happens that gtk-vnc-0.3.8 is already available in gnome overlay because vinagre is using it. If another packages in tree required the update then we would probably move it out of sync of the rest of gnome package. This to my knowledge this is not the case hence the generic answer "will be moved with other gnome packages when 2.26 is ready". In any case 2.26 is near completion from a review standpoint so it'll probably start hitting the tree by the end of the week and there is no need to be in a hurry. This is nothing against you but users asking for things already available that they could have figured out by searching a bit (gnome overlay is in layman) or discussing with us on irc are a bit boring with time.
At least myself I haven't been marking bugs as FIXED until the ebuild is in the main tree. Keeping the bug open means users will find it while searching for open bugs.
It is discoverable via the 2.26 tracker and prepending ALL to your search as suggested on bugzilla's main page. Keeping bugs opened for the sake of it is imho useless and it just creates noise for real bugs that needs attention. We are moving off topic here, feel free to raise this issue to devel if you feel like it.
It's generally been the policy of the gnome team to close bugs against the next version of gnome when they're fixed in the overlay. That way we don't have to go through and close hundreds of bugs (and probably miss a lot) when the overlay is actually synced against portage. Bugs against versions of gnome already in portage, of course, aren't closed until they're fixed in portage.
