GDM 2.6 isn't in the Portage tree (masked or otherwise), while everything else in GNOME 2.6 appears to be. Is this an oversight? I know I and a few others are having compilation difficulties with the 2.4 version; dunno if this is the problem, but it'd be good to have the new release nonetheless.
Steps to Reproduce:
I'm having comile problems with the present version of gdm and the gnome 2.6 system.
it's no oversight.. gdm schedule tends not to be tied to the gnome schedule, so I don't treat it as such. It'll come when we find the time.
@ jon : file your problems as a new bug, this tells us completely nothing. If you can't make a useful comment, don't make a comment at all please.
Gotcha. Just checking.
*** Bug 47509 has been marked as a duplicate of this bug. ***
Gotten from http://www.jirka.org/gdm.html (the homepage of GDM) under the "Download" section:
"After GNOME2.4, the versioning will 'sync up' with the GNOME versioning scheme to make things simpler."
I think the ftp-address speaks for itself.
Just something personal: If you like to give small "friendly" comments about duplicates I think you should wait until they have got the linking between packages.gentoo.org and bugs.gentoo.org to work so it is really easy to find "bugs" related to a package. It is not always you find what you are looking for becouse you maybe choosed not so good keywords for the search.
Is it too much work to put a little effort in ? I have to find the old one and dupe it. You give us the work now. Well, you give us the work in the first place with the request without ebuild.
And when handling dozens of bugs a day you don't weigh every sentence you type anymore.
And yes the schedules are supposed to be synced, but we're not ... yet. So that's just the deal. Have a little patience, we're trying as hard as we can here and i keep on wasting time writing replies to these kind of bugs where people tend to always know just a little bit better why this or that should be done in that or this way and try in every way to make their point and prioritize their oh-so important bugreport. I really shouldn't have written that, but hey.. that's the feeling i got and i'm an emotional person and i just write down what i think. ...*should edit comment*... ah well
Well gdm 184.108.40.206 and lately 220.127.116.11 have worked here flawless for a while using the 18.104.22.168-r1 ebuild with the selinux.patch commented away (don't sure what it does but does not break things for me) but you have to get the tar.bz2 file yourself. I only using local logins so stability for remote-working I can't comment.
Just for notice if anybody cares.
this got fixed btw