March 2009 - openSUSE GNOME - openSUSE Mailing Lists

[opensuse-gnome] Updating Gnome 2.24 to 2.26
by Sebastian Roesgen 31 Mar '09

31 Mar '09

Hallo all, now that GNOME 2.26 is in the GNOME:/STABLE: repository, I gave it a try and installed it (on three different PCs). Worked fine for me, but I asked myself a question: On All three machines the 100% CPU error occured and I had to add the http://download.opensuse.org/repositories/home:/MBoman/openSUSE_11.1/ repository. So will there be some fix in a more official repository soon? Wouldn't it be more logical to put the fix in either the GNOME:/STABLE:/2.26 repository or the X11 repository to spare other users adding an extra rep? (I assume that those who give the 2.26 repository a try will, at least in most cases, also use the X11 repository) I personally made the epxerience that the more reps you add to your repository list, the more often you will encounter dependency problems (and in some cases even heavier problems). I suppose you know these problems (if not I can give you examples). Or is this problem already fixed? If this is the case take my apologies for asking unnecessary questions. Thanks in advance, Sebastian Rösgen -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

3 2

[opensuse-gnome] Upgrade Gnome 2.26 for openSUSE 11.0
by Rastislav Krupanský 29 Mar '09

29 Mar '09

Hi all. Just a short question. How can i upgrade Gnome 2.26 for openSUSE 11.0? I can't find any repo for 11.0, only for 11.1 - http://download.opensuse.org/repositories/GNOME:/STABLE:/2.26/ Thanks a lot. -- S pozdravom / Best regards, Rasto -- 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] Today's meeting cancelled
by Bryen 26 Mar '09

26 Mar '09

Due to lack of attendance, we have had to cancel today's regularly-scheduled meeting. Our next meeting will be next week, same time Thursday at 19:00 UTC unless you voice concerns about that new time frame. Thanks, -- Bryen Yunashko openSUSE Board Member openSUSE-GNOME Team Member GNOME-A11y Team Member -- 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] openSUSE GNOME Team Meeting at 19:00 UTC
by Bryen 26 Mar '09

26 Mar '09

Hello all... Sorry for the late send out. Today, the openSUSE GNOME Team will have its regular weekly meeting at its newly set up regular weekly time (did I just say a mouthful?). Meeting time: 19:00 UTC Meeting place: #opensuse-gnome on Freenode IRC network Dress Code: Business Casual Today, we'll be discussing ideas to recommend for the openSUSE COmmunity Week in April, plus status of moving the new GNOME 2.26 setup from GNOME:FACTORY to GNOME:STABLE. See you all there. -- Bryen Yunashko openSUSE Board Member openSUSE-GNOME Team Member GNOME-A11y Team Member -- 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] WEBEX
by James Tremblay aka SLEducator 25 Mar '09

25 Mar '09

Is there any way someone could create some configuration instructions to run WEBEX on openSUSE? The Ubuntu ones don't seem to solve the issue of being rejected as incompatible. -- James Tremblay Volunteer openSIS Product Specialist http://www.os4ed.com e-mail james "at" os4ed.com e-mail sleducator "at" opensuse.org CNE 3,4,5 MCSE w2k CLE in training Registered Linux user #440182 http://en.opensuse.org/education

1 0

[opensuse-gnome] Default torrentclient in Gnome
by Alan McGovern 25 Mar '09

25 Mar '09

(And once again forwarding to the list :) ) Hey, On Tue, Mar 24, 2009 at 9:28 PM, Christian Jäger <christian.jaeger(a)rub.de> wrote: > Hi Alan, > > you have a great way of marketing your application; I remember that > before the first inclusion of Monsoon as default BT app you also let it > sound as if all we had to do was to send in some reports to fix the very > few remaining bugs; There is currently one major issue open in bugzilla: #485459. That bug has already been fixed in SVN of monotorrent (http://anonsvn.mono-project.com/viewvc?view=rev&revision=129752) about 3 days after it was reported. > and now years have gone by and Monsoon STILL is a pile of ...problems. See above. > Let's face it; it WON'T be fixed quick! Take your time, gather willing > beta-testers and polish your product. Nothing will be fixed if I don't know about it. > But DON'T try to push Monsoon down our throats and turn thousands of > openSUSE users into unwilling guinea-pigs. You are free to choose as you will. If you choose (along with opensuse) to not use monsoon as the default, there's nothing I can do about that. If you decide as a personal choice to not use it even if it's the default, there's nothing I can do about that either. All I can do is fix known issues and improve features and maybe one day attract you back through technical merit. Alan. > > Cheers, > Chris > > -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

5 9

[opensuse-gnome] Default torrentclient in Gnome
by Alan McGovern 24 Mar '09

24 Mar '09

(Doh, resending again as i forgot to make the email plain text) Hey, > Not even the latest version from Gnome-community works > as it should. Maybe the packager's fault, but as an end-user: what do I > care? All I want is a working BT-client. Exactly. End users just want something that works. No amount of features can replace stability. I couldn't agree more. So, with that in mind, what exactly isn't working? As the old saying goes, if there are no bug reports, there are no bugs. A bug report on bugzilla would be the best place to report any issues you're having. > I DON'T want to have to file bug-reports for the standard components of my desktop! Which is exactly how I felt when opensuse regressed and broke *keyboard* support with my laptop rendering a new install unusable. Or when my wireless stopped working. Or when YaST crashed every time it was started. Or zypper still being unable to install packages reliably if the same package name exists in multiple repositories. All of which are so much more critical to the desktop than any old torrent client, yet we still file bugs on them even though they are core components. That's the only way things can get fixed. Alan. > > > Greets, > Chris > > Am Dienstag, den 24.03.2009, 19:56 +0000 schrieb Alan McGovern: > > (Sending again, i think it failed the first time) > > > > Hey > > > > I've read through the thread and all I really have to add is this. > > Note, I am cherry picking quotes from different emails here: > > > > > Not much has happend upstream > > > > > > What exactly do you define as upstream. Since Monsoon was originally > > chosen as the client, there have been two releases of monsoon and five > > releases of the backend torrent library. I have scheduled a bugfix > > release (0.71) of the backend library to happen pretty soon, which > > will make 6 releases of the backend. So if you're implying there is no > > active upstream work being done at all, you'd be wrong ;) > > > > > and no other distros (that I know of) has made monsoon their client too. > > > > I can't comment on that. What I can say is that Monsoon is packaged > > in a number of different distros. > > > > > > > > The problem with using a unknown/unused client is that we are the only > > > ones providing bugs and/or patches. And since I have a strong belife > > > that most of us deletes monsoon for a different client, even less bugs > > > get upstreamed. > > > > > > There are quite a number of users of the backend library who > > contribute bug reports (and sometimes patches) and also a few > > recurring contributors. So issues relating to freezing/crashing/poor > > performance in the backend library have a lot more people than just > > opensuse reporting bugs. > > > > > we should really not judge it based on the (small) duration between 11.0 and 11.1 (during which, frankly, monsoon did not end up a finished product). > > > > Yes, I did concentrate more heavily on the backend throughout the 11.0 > > -> 11.1 cycle (as can be seen from the number of releases mentioned > > above). There are currently two major GUI features planned for Monsoon > > 0.30. > > 1) A smart queuing system (in progress in svn) > > 2) Addin support (patch to be contributed by a 3rd party in the near future) > > > > > What merits does Monsoon have vs. going with Transmission? Are there any benefits? Transmission is fully working today and has a tremendous amount of support > > > > It's worth pointing out that Novell will not ship any torrent client > > with DHT enabled [1] due to legal risks. However for the 0.30 release > > I'll split the DHT code out of monotorrent into a separate library > > (3-5 hours of work). Then Monsoon can ship as 'DHT Ready', which means > > it has the capability to use DHT but will ship with zero DHT code. > > Then, using Mono.Addins, the DHT library can be installed and > > activated seamlessly at runtime. This will provide a *great* feature > > that no other torrent client provides out of box for opensuse. > > Normally you'd have install a package from a 3rd party repository > > where DHT isn't disabled. Transmission has no support for DHT to the > > best of my knowledge. > > > > So that pretty sums up my thoughts after reading the thread. If anyone > > has any specific feature requests, bugs or general comments, feel free > > to file a bug report on bugzilla so the ideas don't get lost. If you > > want a general discussion, I'll keep responding here. Or maybe a > > separate thread might be in order and we can keep this one for default > > client discussions. > > > > Thanks, > > Alan. > > > > [1] I'm not actually 100% sure if dht is disabled in all torrent > > packages in opensuse even though it should be. ktorrent and Monsoon > > disable for sure. I'm not sure if deluge does or not. If there is a > > torrent package shipping from opensuse repositories which does *not* > > have DHT disabled, I'm sure opensuse legal would love to hear about it > > ;) I can forward the relevant emails from my discussion with them to > > anyone interested, or you can email them yourselves. > -- 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] Default torrentclient in Gnome
by Alan McGovern 24 Mar '09

24 Mar '09

(Sending again, i think it failed the first time) Hey I've read through the thread and all I really have to add is this. Note, I am cherry picking quotes from different emails here: > Not much has happend upstream What exactly do you define as upstream. Since Monsoon was originally chosen as the client, there have been two releases of monsoon and five releases of the backend torrent library. I have scheduled a bugfix release (0.71) of the backend library to happen pretty soon, which will make 6 releases of the backend. So if you're implying there is no active upstream work being done at all, you'd be wrong ;) > and no other distros (that I know of) has made monsoon their client too. I can't comment on that. What I can say is that Monsoon is packaged in a number of different distros. > > The problem with using a unknown/unused client is that we are the only > ones providing bugs and/or patches. And since I have a strong belife > that most of us deletes monsoon for a different client, even less bugs > get upstreamed. There are quite a number of users of the backend library who contribute bug reports (and sometimes patches) and also a few recurring contributors. So issues relating to freezing/crashing/poor performance in the backend library have a lot more people than just opensuse reporting bugs. > we should really not judge it based on the (small) duration between 11.0 and 11.1 (during which, frankly, monsoon did not end up a finished product). Yes, I did concentrate more heavily on the backend throughout the 11.0 -> 11.1 cycle (as can be seen from the number of releases mentioned above). There are currently two major GUI features planned for Monsoon 0.30. 1) A smart queuing system (in progress in svn) 2) Addin support (patch to be contributed by a 3rd party in the near future) > What merits does Monsoon have vs. going with Transmission? Are there any benefits? Transmission is fully working today and has a tremendous amount of support It's worth pointing out that Novell will not ship any torrent client with DHT enabled [1] due to legal risks. However for the 0.30 release I'll split the DHT code out of monotorrent into a separate library (3-5 hours of work). Then Monsoon can ship as 'DHT Ready', which means it has the capability to use DHT but will ship with zero DHT code. Then, using Mono.Addins, the DHT library can be installed and activated seamlessly at runtime. This will provide a *great* feature that no other torrent client provides out of box for opensuse. Normally you'd have install a package from a 3rd party repository where DHT isn't disabled. Transmission has no support for DHT to the best of my knowledge. So that pretty sums up my thoughts after reading the thread. If anyone has any specific feature requests, bugs or general comments, feel free to file a bug report on bugzilla so the ideas don't get lost. If you want a general discussion, I'll keep responding here. Or maybe a separate thread might be in order and we can keep this one for default client discussions. Thanks, Alan. [1] I'm not actually 100% sure if dht is disabled in all torrent packages in opensuse even though it should be. ktorrent and Monsoon disable for sure. I'm not sure if deluge does or not. If there is a torrent package shipping from opensuse repositories which does *not* have DHT disabled, I'm sure opensuse legal would love to hear about it ;) I can forward the relevant emails from my discussion with them to anyone interested, or you can email them yourselves. -- 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] Default torrentclient in Gnome
by Bjørn Lie 24 Mar '09

24 Mar '09

We've had Monsoon as the default torrent client for some releases now, and as far as I can tell it's not been a great success. Not much has happend upstream, and no other distros (that I know of) has made monsoon their client too. I propose we reopen the default torrent client discussion again, just to see what the general opinion is. I've personally tried to use it, but never felt comfortable with it. Normally ending up in me installing Transmission or Azureus. What do you all think? Bjørn Lie -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

9 13

RE: [opensuse-gnome] Default torrentclient in Gnome
by Andrew Wafaa 22 Mar '09

22 Mar '09

As the person that did the initial review[0] of BitTorrent clients over ~18months ago for 11.0, it was myself that recommended Monsoon. The choice was not mine alone but that of the community. As such if the community feels it is prudent to review this choice and make ammendments then I am all for it. In my review I had Transmission as the #2 choice so I'm happy to use that. As for lack of releases for Monsoon, I'm not so sure that is necessarily a bad thing. I have experienced very few issues with it and there have been a couple of releases since the initial inclusion in 11.0. As for others using it, one distro I know of is Foresight, so we are not alone (and so what if we were?) ;-) As I have very little usage of other distros what do the likes of Fedora/Debian/Mandriva/Ubuntu/etc. use, also what is the default client upstream? Regards, Andy [0] - http://en.opensuse.org/User:FunkyPenguin/TorrentReview -- 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: Bjørn Lie Sent: 21/03/2009 21:19:17 Subject: [opensuse-gnome] Default torrentclient in Gnome We've had Monsoon as the default torrent client for some releases now, and as far as I can tell it's not been a great success. Not much has happend upstream, and no other distros (that I know of) has made monsoon their client too. I propose we reopen the default torrent client discussion again, just to see what the general opinion is. I've personally tried to use it, but never felt comfortable with it. Normally ending up in me installing Transmission or Azureus. What do you all think? Bjørn Lie -- 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] G:F status, osc gnome news & G:S
by Vincent Untz 19 Mar '09

19 Mar '09

Hi all, I guess it makes sense to send a quick mail about all this before the meeting. We'll be able to discuss all this if needed during the meeting. G:F status ========== GNOME:Factory has GNOME 2.26.0 (except for anjuta and sound-juicer, I believe). The build against Factory itself should be finished before the meeting (actually, it might be finished before I'm done with this mail). The build against 11.1 will take a bit longer, but it seems it might be done in the next few hours too. Here's the list of packages we need to update: + epiphany/metacity: we have 2.26.0, but there are already some 2.27 tarballs. We block them for the moment. + g-wrap/libmcs: I filed drop requests. + NetworkManager and friends: we have permission from Tambet to update them, but it might be non-trivial :-) + abiword: just appeared. It shouldn't be hard, except that I think we should split abiword-plugins in its own package. There's no real point in having both tarballs there, I think + gnome-do: shouldn't be hard. Any gnome-do enthusiast? I also saw that there's a gnome-do-plugins tarball that we might want to package. + gnome-phone-manager: Magnus is working on it, iirc. + gnucash: same. + gobby: we have submissions for this. Help to review libinfinity is welcome, since it ships with a system daemon and I don't trust my review abilities for this... + gstreamer-0_10-plugins-farsight: I'm blocking this for now, since some plugins were moved to gstreamer-0_10-plugins-bad, but we need a new upstream release of gstreamer-0_10-plugins-bad for them. + libwebkit: any volunteer? Else, I might give it a try... + monsoon: I think it requires monotorrent, or something like this. Someone should look at that. + rhythmbox: just appeared. Let me take it :-) osc gnome news ============== While waiting for GNOME 2.26.0 to build (locally in my jhbuild, and in the build service for packages), I worked a bit on osc gnome to bring two new things: + the first one is self-explanatory: osc gnome todo --project GNOME:STABLE:2.24 Yes. We can use osc gnome with GNOME:STABLE! For now, the todo command will only list packages that are part of the official GNOME release. If we want to update other packages, it's possible with some small work. + the second one is that osc gnome is now completely independent from oS:F and G:F: those projects are not used anywhere anymore in the code (except for the default values, which people can easily change). This means the plugin is getting more and more ready to conquer the world ;-) It's all in the git repo right now, and if it works fine after a few days, I'll update the osc-plugins-gnome package in openSUSE:Tools. Note that I need to change a bit the way reservations work so that they are per-project. Right now, if you reserve gnome-panel in G:F, it will also mark it as reserved in G:S:2.24, which is obviously wrong. I'll fix this before next week (I might have time for it tonight) GNOME:STABLE ============ With osc gnome working with GNOME:STABLE, it's now possible to easily update everything that needs to be updated in GNOME:STABLE. There are some questions to discuss (the meeting sounds like a good time for that): + creation of G:S:2.26: when? And when it's created, should we move G:F to 2.27? + what kind of package updates go in. I think it doesn't make sense to do work on cleaning the packaging (this is something that should be done in G:F) unless it fixes a bug. So I propose to only package new upstream versions, or add patches to fix bugs. + handling of security issues: if there's a security update for 11.1, we need to make sure the relevant patch also appears in G:S. How can we do this? 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 1

[opensuse-gnome] openSUSE-GNOME Team meeting: NEW TIME!
by Bryen 19 Mar '09

19 Mar '09

Well, we've been experimenting with best times for our weekly meetings for the openSUSE-GNOME Team, and *hopefully* we've found our sweet spot. This week's meeting will be held at the new time of 19:00 UTC on Thursday, March 19th, 2009 in the #opensuse-gnome channel on the Freenode network. This will be the permanent time for us (i.e., no more timeshifted meetings) This week, we'll be continuing JPR's proposal for core team maintainers. It should be a good discussion. Also, GNOME 2.26 has been released and is about to be in GNOME:Factory. We'll be discussing plans for the next step (2.27) going into Factory. Special kudos goes to Magnus (captain_magnus) and Luis (metalgod) for their hard work getting this done. You know, we were supposed to have a packaging day organized for this week, but those guys actually finished most the work ahead of time! And of course, we'll have the great policy review session from Vuntz. He's always bringing up interesting topics for us to think about. So see you all at the meeting. New time and hopefully permanent time! -- Bryen Yunashko openSUSE Board Member openSUSE-GNOME Team Member GNOME-A11y Team Member -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

2 2

[opensuse-gnome] What is the top 5 things that should be fixed/improved for GNOME in openSUSE 11.2?
by Magnus Boman 16 Mar '09

16 Mar '09

Hello, Since we have 8 months before the 11.2 release, would it be possible to compile a list with the top 5 most annoying things in GNOME/openSUSE and try to fix them? We obviously need to be realistic about these goals. Issues might include stuff like, "Panel should be at the top of the screen", "We should use the default GNOME menu", "Tomboy should not be started by default" etc? Other annoying things might not be as simple as I just mentioned but, you get the idea... Also, please don't include PA in this discussion... It's being discussed/fixed elsewhere :-) Cheers, Magnus -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

8 13

[opensuse-gnome] openSUSE-GNOME Team meeting minutes from 05-March-2009
by Luis Medinas 11 Mar '09

11 Mar '09

Hi These are the meeting minutes from the openSUSE-GNOME Team on 05-March-2009: * 11.2 planning: -The Team agreed with shipping GNOME 2.28 for this release still we need to have some hard work to get everything in time because we have to break feature freeze for 11.2. * Random Bugs: - We stated that we should remove ggreeter from GNOME and write a new application called "About openSUSE" or "About My Computer" in order to give the same information without spamming the user at the first boot. - Discussed Pulseaudio problems, sreeves is doing his best to fix as much bugs as possible by providing packages with and without Glitch Free. * GNOME:Factory Status: - The current GNOME:Factory repository contains the latest GNOME 2.25.92 (release candidate). There's just a few minor issues but it's ready to be used (it was already migrated for oS:F and build for 11.1). - The Team also agreed that some package specs needs to be cleaned. - Also there are some packages that needs to be removed from G:F such as eel, ncb and probably a few others. * Mailing List Threads: - Nautilus-cd-burner removal: There are patches in upstream for f-spot and recently Rhythmbox start using Brasero (replacement for n-c-b). Luis -- 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] GNOME:Factory status
by Vincent Untz 11 Mar '09

11 Mar '09

Hey all, Quick status update about GNOME:Factory: + G:F has GNOME 2.25.92 + it's nearly up-to-date wrt upstream versions. There are 18 packages for which we are late: - 2 already submitted packages (pidgin, gnome-bluetooth), needing a review - 1 package blocking on the gnome-bluetooth update (gnome-phone-manager) - 5 reserved packages (gnome-icon-theme, gnome-packagekit, gthumb, ldtp, sound-juicer) - 2 packages that I think we should just drop (g-wrap, libmcs) - gobby which is hard. There's actually an update available in another project (see bug #473320), so if someone can look at it, that'd be great - NetworkManager and NetworkManager-gnome that, I think, most people just leave to Tambet. But Tambet welcomes help here :-) There are many patches (most of them are upstream now), so it might be difficult. - gstreamer-0_10-plugins-farsight which is weird because we have to patch the tarball. I know it stopped me from updating it... - gnome-power-manager, gnucash, nautilus, qtcurve-gtk2: all waiting for an update. I will actually do nautilus and qtcurve-gtk2 right now ;-) + everything builds fine (and should install fine) on both 11.1 and Factory, except: - evolution-sharp: doesn't build because eds is too recent. We need a new upstream version, or a small patch (that should be trivial) - beagle-index: doesn't build on factory because the Xvnc has been disabled at the moment in factory + I pushed everything (125 updated packages) to openSUSE:Factory a few minutes ago 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

1 0

[opensuse-gnome] Updated packages in GNOME:Community
by Ivan N. Zlatev 04 Mar '09

04 Mar '09

Hey, I have updated in GNOME:Community file-browser-applet to 6.0.1. and pidgin to 2.5.5. I had to disable the nonblocking patches because they are no longer applying cleanly. I have no idea what's the story of those patches is but if someone wants to step up and update them and re-enable them - you are welcome. -- Kind Regards, Ivan N. Zlatev -- 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] openSUSE-GNOME Next Meeting
by Luis Medinas 04 Mar '09

04 Mar '09

Hi I want to inform that the team agreed have the meeting tomorrow, March 5 at 17h UTC and NOT at 22h UTC that was planed last week. Cheers Luis -- 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] Removing nautilus-cd-burner from G:F
by Luis Medinas 04 Mar '09

04 Mar '09

Hi For GNOME 2.26, nautilus-cd-burner as been marked deprecated[1] in favor of Brasero. Currently G:F has 3 packages depending on it, rhythmbox, f-spot and gnome-python-desktop. For rhythmbox[2] and f-spot[3] there is a patch on upstream waiting to be reviewed and commited to the tree. As for gnome-python-desktop there are also bindings for brasero in development and the current ncb bindings could be disabled. So should we keep ncb in G:F until 2.28, remove it or move it to G:C ? Luis [1] - http://mail.gnome.org/archives/release-team/2009-January/msg00067.html [2] - http://bugzilla.gnome.org/show_bug.cgi?id=536732 [3] - http://bugzilla.gnome.org/show_bug.cgi?id=569413 -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

2 4

[opensuse-gnome] Moderator for Thursday's Meeting
by Bryen 04 Mar '09

04 Mar '09

I will not be able to attend this Thursday's meeting. If anyone wishes to moderate the meeting on Thursday, please speak up now. :-) -- Bryen Yunashko openSUSE Board Member openSUSE-GNOME Team Member GNOME-A11y Team Member -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

3 2

Re: [opensuse-gnome] Overview of rpmlint warnings in G:F
by Suman Manjunath 01 Mar '09

01 Mar '09

>>> Vincent Untz <vuntz(a)opensuse.org> 02/28/09 10:42 AM >>> > http://tmp.vuntz.net/opensuse-packages/rpmlint.py?type=non-utf8-spec-file There is a problem with fixing this warning. Most of the non-utf8-ness comes from the "Authors" list in the spec file. So, even if we fix it in our local/G:F repos, when it is submitted to oS:F, that fix just gets discarded as the PDB entry for the "Authors" list takes precedence. Any idea how we can avoid that (besides attempting to change the PDB entry itself)? -Suman -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-gnome+help(a)opensuse.org

1 0