April 2009 - openSUSE GNOME - openSUSE Mailing Lists

[opensuse-gnome] GNOME status
by Vincent Untz 17 Apr '09

17 Apr '09

Hey, (I stopped calling those mails G:F status since we can also put some G:S thing in there :-)) G:F === As of now, nearly all GNOME 2.26.1 is in G:F. AFAIK, we're missing gdm (because there's a patch that needs some investigation -- hpj, can you look at the gdm-xauthlocalhostname.patch patch and see if it's still needed in 2.26.1?) and evo/eds (well, we have 2.26.1, but not 2.26.1.1) It's all compiling right now, but please test when it's ready. Packages to update: + NetworkManager stack: I guess everybody is hoping Tambet will do it ;-) + avahi: shouldn't be hard. Any volunteer? + epiphany/metacity: there are 2.27 versions there. We are waiting a bit, but we might want to go ahead + gnome-do: should be straightforward. We might also want to add gnome-do-plugins. Any volunteer? + gnucash: I know Magnus looked at this. Not sure if something went wrong? + gobby: we're still waiting for someone to review the new packages. Maybe we should just request help from opensuse-packaging? + libtasn1: the new version removes libtasn-config, which could break many things. Maybe we should create libtasn2 instead? + liferea: will do it now + monsoon: still nobody wanting to update it? + pulseaudio stack: Scott will probably look at it. I know I didn't even try to update it since there might be some hidden trap ;-) G:S === We need to decide how to push 2.26.1 to G:S:2.26. I won't do the work myself, but I guess the best approach is to have people test 2.26.1 in G:F for 2-3 days, and if everything is fine there, copy the 2.26.1 packages from G:F to G:S:2.26 (will be easier than doing all updates again) There are a few packages that have the build disabled in G:S:2.26 and I've no idea why. We should probably have a wiki page for this. But I guess some are just errors (I don't see why we wouldn't build glib2, eg). We now have some good documentation on how to use G:S:2.26: http://en.opensuse.org/GNOME/2.26 Feel free to edit the page to improve it. We also have a tracker bug for G:S:2.26 bugs: https://bugzilla.novell.com/show_bug.cgi?id=493750 osc gnome ========= Magnus and I worked to make sure the database gets updated even when I'm travelling (like right now :-)). So there should be no more downtime there. There was also a small bug for modules hosted on sourceforge: "osc gnome update" didn't work for them. It should be fixed now. Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

3 4

RE: [opensuse-gnome] GNOME status
by Andrew Wafaa 15 Apr '09

15 Apr '09

Vincent, Sorry for the delay & lack of response, I'll look at Monsoon. Regards, Andy -- Sent from a Nokia E71 Andrew Wafaa, openSUSE Member: FunkyPenguin. openSUSE: Get It, Discover It, Create It at http://www.opensuse.org . -----Original Message----- From: Vincent Untz Sent: 15/04/2009 18:34:01 Subject: [opensuse-gnome] GNOME status Hey, (I stopped calling those mails G:F status since we can also put some G:S thing in there :-)) G:F === As of now, nearly all GNOME 2.26.1 is in G:F. AFAIK, we're missing gdm (because there's a patch that needs some investigation -- hpj, can you look at the gdm-xauthlocalhostname.patch patch and see if it's still needed in 2.26.1?) and evo/eds (well, we have 2.26.1, but not 2.26.1.1) It's all compiling right now, but please test when it's ready. Packages to update: + NetworkManager stack: I guess everybody is hoping Tambet will do it ;-) + avahi: shouldn't be hard. Any volunteer? + epiphany/metacity: there are 2.27 versions there. We are waiting a bit, but we might want to go ahead + gnome-do: should be straightforward. We might also want to add gnome-do-plugins. Any volunteer? + gnucash: I know Magnus looked at this. Not sure if something went wrong? + gobby: we're still waiting for someone to review the new packages. Maybe we should just request help from opensuse-packaging? + libtasn1: the new version removes libtasn-config, which could break many things. Maybe we should create libtasn2 instead? + liferea: will do it now + monsoon: still nobody wanting to update it? + pulseaudio stack: Scott will probably look at it. I know I didn't even try to update it since there might be some hidden trap ;-) G:S === We need to decide how to push 2.26.1 to G:S:2.26. I won't do the work myself, but I guess the best approach is to have people test 2.26.1 in G:F for 2-3 days, and if everything is fine there, copy the 2.26.1 packages from G:F to G:S:2.26 (will be easier than doing all updates again) There are a few packages that have the build disabled in G:S:2.26 and I've no idea why. We should probably have a wiki page for this. But I guess some are just errors (I don't see why we wouldn't build glib2, eg). We now have some good documentation on how to use G:S:2.26: http://en.opensuse.org/GNOME/2.26 Feel free to edit the page to improve it. We also have a tracker bug for G:S:2.26 bugs: https://bugzilla.novell.com/show_bug.cgi?id=493750 osc gnome ========= Magnus and I worked to make sure the database gets updated even when I'm travelling (like right now :-)). So there should be no more downtime there. There was also a small bug for modules hosted on sourceforge: "osc gnome update" didn't work for them. It should be fixed now. Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

2 1

[opensuse-gnome] Metacity won't use the GTK colors?!
by smurfd 14 Apr '09

14 Apr '09

Hi, so i have been using OpenSUSE for a while as a virtual macine/dev lab/dev machine, for a while, but there's one thing, It does not seem to be possible to get metacity to use the colors as the GTK theme "tells" it to use? usually becomes some black or dark green default color instead? is this some known bug/issue? i know its been like this for 11.x but im not sure about 10.x cant remember... Best regards /smurfd ps. if you reply, please cc me :) -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

1 0

[opensuse-gnome] G:S:2.26 status
by Vincent Untz 10 Apr '09

10 Apr '09

Hey, So after today's meeting (and the various things that people did after), I think we have a better view of the G:S:2.26 status. It looks like most issues just come from the fact that people were not using all packages from G:S:2.26. By default the updates repository has a priority of 20 while the repositories you manually add (like G:S:2.26) have a priority of 99. At least that's what I had on my test install. And the lowest value means highest priority. So we need to document this clearly. Do we have a wiki page explaining how to install GNOME 2.26? Federico updated the X server in G:B:2.26, so the 100% CPU bug should also be gone. That leaves us with the gnome-keyring issue and nothing else, as far as I know. Still waiting for a stack trace :-) For all other bugs you encounter, please file them and add them to this tracker: https://bugzilla.novell.com/show_bug.cgi?id=493750 (well, try to avoid filing upstream bugs there, but just the really annoying bugs that make G:S:2.26 not a good experience) Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

2 2