On Sat, 10 Jan 2009 12:39:50 -0600, Michal Varga <varga.mic...@gmail.com>
wrote:
Hello guys,
I noticed that Gnome 2.24 was commited today along with gnome-session
2.24, so I need to ask - how did FreeBSD Gnome team decide to deal
with the recent session management fuckup? I mean this:
Because we don't know about this bug. Nobody has report about this bug
when 2.24 was available in MarcusCom CVS for very long time. I guess, we
will have to add in our known issue for now until we figure what to do
with it.
Cheers,
Mezz
http://np237.livejournal.com/22014.html
http://bugzilla.gnome.org/show_bug.cgi?id=552387
https://bugzilla.redhat.com/show_bug.cgi?id=471980
...etc, basically any OS/distribution that adopted 2.24 has been
heavilly bitten by this major regression (try google a few discussions
just for the lulz factor, though seriously, the whole situation is not
that much humorous) and so far I heard that only Gentoo ships
(probably somewhat modified/patched, though I'm not a Linux user and
would need to check their repos first) gnome-session 2.22 to address
it.
Anyway, my question is (while i'm still syncing the ports) - was the
issue addressed on FreeBSD's side, if not, are there any plans to
address it "really soon", and if not (god save us), can someone please
at least put a neon blinking warning in UPDATING? I've seen a few
Linux early adopters of Gnome 2.24 on a verge of suicide then they
learned that session management (as we know it) has been shot in the
head, without any replacement in sight..
m.
--
me...@cox.net - m...@freebsd.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gn...@freebsd.org
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
