December 2009 - openSUSE Factory - openSUSE Mailing Lists

Re: [opensuse-factory] RFC: Announcing important changes in the distribution
by Robert Schweikert 12 Dec '09

12 Dec '09

Robert Schweikert Software Engineer Consultant rschweikert(a)novell.com 781-464-8147 Novell Making IT Work As One >>> Andreas Jaeger 12/10/09 9:52 AM >>> On Thursday 10 December 2009 15:03:45 Jano Kupec wrote: > On 12/10/2009 11:05 AM, Andreas Jaeger wrote: > > On Wednesday 02 December 2009 18:57:45 Lubos Lunak wrote: > >> [...] > >> The place for such announcements would be this list, with some specific > >> subject to make it easier to spot them (and perhaps some more firm > >> pointing to the right list would be needed for those who create noise, > >> or something from > >> http://lists.opensuse.org/opensuse-factory/2009-09/msg00354.html would > >> be needed). > > > > I see some consensus for this, so what tag should be used in the subject > > to mark it? Let's reword the proposal to work with missing details... > > > > I also suggest to have a factory development page that links to all these > > announcements, so that we reference them from one place. What do you > > think? > > What i don't like about the wiki is that it is hard to see incremental > changes to it, like you would see on a dedicated announce mailing list. > And you can reply to the announcement (in-lining the text) and further > discuss on opensuse-factory. > > I agree with Lars in the other mail, that we should use some exising > mailing lists, because we have too many, but opensuse-announce is for > user announcments, what we discuss here is more a developer thing. I > still see opensuse-factory for discussion (RFC or otherwise tagged > mails) and some dedicated list only for announcmements (low traffic, > only the results) as the best solution. > > But i'm also fine with just discussion on opensuse-factory and the wiki. > 'RFC' in the subject is fine for me. My proposal was to discuss on -factory and just have a pointer in the wiki to it so that somebody can easily lookup these some time later - so I think we're in agreement, Andreas I like the wiki and I like [ANNOUNCE] as a prefix. I still think we should have a more prominent place for this information on the main page (www.opensuse.org). With the wiki in place a link to the wiki page should suffice. I am mostly thinking of users not subscribed to any mailing list and people not necessarily in tune with checking the wiki for important information. Robert

6 9

[opensuse-factory] php5 question/issue/proposal ?
by Joop Boonen 11 Dec '09

11 Dec '09

Dear all, I'm building package php5-gtk because of the scan directory I have an issue when php5-gtk is installed in combination with apache2 i.e. for instance cacti doesn't work any more as php tries to start up with php-gtk when it's installed. I think it would be better to have outside of the /etc/php5/conf.d also /etc/php5/apache2/conf.d and /etc/php5/cli/conf.d in which specific ini files can be put that are only used for either apache2 or cli. In my case the php5-gtk.ini would reside in /etc/php5/cli/conf.d as it's a cli implementation only. I think the php5.spec file can be change in the following way: --with-config-file-scan-dir=%{php_sysconf}/conf.d %{php_sysconf}/$sapi/conf.d I've read that --with-config-file-scan-dir can now have more than one directory. Regards, Joop. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 4

[opensuse-factory] submitreq 26278 - Package menu-cache (LXDE core dependency)
by Andrea Florio 11 Dec '09

11 Dec '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 going on with LXDE related submitrequests here some infos: bugowner : anubisg1 (me); the package is a core LXDE dependency, no bugs reported. The package is well test from various distros like fedora/mandriva/ubuntu and for example it's already into fedora and mandriva repositories. upstream project is [1] the upstream bugtracker is here: [2] and no security issue found yet (a review from security team maybe still be needed ) i want to maintain this package into Factory because i want to provide the full LXDE desktop enviroment and this package is one the components. see openfate feature [3] and bugzilla enhacement here [4] again, please consider that this is the most important BuildRequire for all LXDE enviroment License is GPLv2 Regards Andrea [1] http://lxde.org [2] http://sourceforge.net/tracker/?group_id=180858&atid=894869 [3] https://features.opensuse.org/307729 [4] https://bugzilla.novell.com/show_bug.cgi?id=561145 - -- - ------------------------------------------ Andrea Florio QSI International School of Brindisi Sys Admin openSUSE-Education Administrator openSUSE Official Member (anubisg1) Email: andrea(a)opensuse.org Packman Packaging Team Email: andrea(a)links2linux.de Web: http://packman.links2linux.org/ Cell: +39-328-7365667 - ------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAksin4kACgkQyCZT87TFPuiwHwCg5/R6XW4UPFFTA1HkvmUAnCQ+ b5EAnRqVSfBvYgIcUi0X7ngVLlEbim4u =rpLH -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2

[opensuse-factory] [ANNOUNCE] ZYpp source repositories on gitorious.org/opensuse
by Duncan Mac-Vicar Prett 11 Dec '09

11 Dec '09

The ZYpp repositories previously published at git.opensuse.org repositories are now available on http://gitorious.org/opensuse http://gitorious.org/opensuse/sat-solver http://gitorious.org/opensuse/libzypp http://gitorious.org/opensuse/zypper http://gitorious.org/opensuse/zypp-utils (previously zypp/tools) http://gitorious.org/opensuse/libzypp-bindings http://gitorious.org/opensuse/libzypp-testsuite http://gitorious.org/opensuse/zypp-dialogsolver http://gitorious.org/opensuse/cmpi-zypp http://gitorious.org/opensuse/zypp-zmd-backend (previously zypp/backend) There is an initial opensuse-zypp team defined with access to those repositories. To switch you only need to edit your .git/config origin remote If before it was git@git.opensuse.org:projects/zypp/zypper.git Now it would be: git@gitorious.org:opensuse/zypper.git The repositories in git.opensuse.org are still accessible, but you can't push to them anymore. They will stay there until no repositories are left on that machine. Gitorious provides feeds for each repository pushes, and per each branch commits. To make it easier to follow the overall project, I have created this feed which merges various feeds and make the titles more similar to the old mails: http://pipes.yahoo.com/pipes/pipe.info?_id=36dc1dc1c0380cca92df9ddaa5b6e26d In the next days we will look for a solution to mail those feed updates to the commits mailing list. -- Duncan Mac-Vicar P. - Engineering Manager, YaST SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] submitreq #26939 and #26940 : xmms2 and LXMusic (LXDE Music player)
by Andrea Florio 11 Dec '09

11 Dec '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi guys, this two are my next LXDE submitreq. here some infos: (submit req #26940) bugowner : anubisg1 (me); the package is here (X11:lxde) since about augoust, no bugs reported. The package is well test from various distros like fedora/mandriva/ubuntu and by me (almost daily use). upstream project is [1] the upstream bugtracker is here: [2] and no security issue found yet (a review from security team maybe still be needed ) i want to maintain this package into Factory because i want to provide the full LXDE desktop enviroment and this package is one the components. see openfate feature [3] and bugzilla enhacement here [4] Users will use it will be any LXDE user, and anyone needs a lightweight picture viewer License is GPLv2 please consider that his most important BuildRequire is provided by submitreq #26939 (submit req #26939) bugowner : anubisg1 (me); the package is here (X11:lxde) since long time, no bugs reported. The package is well tested maily by fedora and other distros that provides packages [5]. upstream project is [6] the upstream bugtracker is here: [7] and no security issue found yet (a review from security team maybe still be needed ) i want to maintain this package into Factory because i want to provide the full LXDE desktop enviroment and this package is one the components. see openfate feature [3] and bugzilla enhacement here [4] package use differet licenses for some plugins like LGPLv2+, GPLv2+ and BSD, all restricted modules has been disabled please consider that this is the most important BuildRequire for lxmusic submitreq #26240 Regards Andrea [1] http://lxde.org [2] http://sourceforge.net/tracker/?group_id=180858&atid=894869 [3] https://features.opensuse.org/307729 [4] https://bugzilla.novell.com/show_bug.cgi?id=561145 [5] http://wiki.xmms2.xmms.se/wiki/Download_XMMS2 [6] http://wiki.xmms2.xmms.s [7] http://bugs.xmms2.xmms.se/ - -- - ------------------------------------------ Andrea Florio QSI International School of Brindisi Sys Admin openSUSE-Education Administrator openSUSE Official Member (anubisg1) Email: andrea(a)opensuse.org Packman Packaging Team Email: andrea(a)links2linux.de Web: http://packman.links2linux.org/ Cell: +39-328-7365667 - ------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAksiKj4ACgkQyCZT87TFPug/kACcDP4xZdd1c1GTLLj7VZ50C4fo xbgAoKZbvatwlLBxffLGovJQ7O8SSBBr =TaMk -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 8

[opensuse-factory] VLAN Config SLES11
by Günther J. Niederwimmer 11 Dec '09

11 Dec '09

Hello, can any tell me the way to configure vlan's for external on a SLES 11 System (my Server) On my system it is not possible to connect the router (5 IP's), I found nothing what is wrong in the logs? Is vlan not working on a SLES11 systems for external Network ? -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] usb printer tracking
by Donn Washburn 11 Dec '09

11 Dec '09

Hey Group; enclosed is an attempt to track out the reason my Brothers MFC7840W USB printer fails to work with openSuSE and Brothers free drivers. I see nothing in these errors that appears wrong. "lp", cups and libusb all seem to be working. The kernel module is mounted. I downloaded a standard Linux kernel and built it up even to try a different usblp kernel module - no help. http://localhost:631 amd Yast2 have been tried Can anyone suggest another idea to check - i have tried it as root and a user I have been tracking a error cusing a Brother's MFC7840W printer with Brother's -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316

1 0

[opensuse-factory] Changing alsa default sample rate
by Sid Boyce 10 Dec '09

10 Dec '09

My sound cards say they should be capable of 192K sample rate, but alsa seems to have a default of 48K. I tried the following in /etc/asound.conf, but it doesn't effect the change. I need it for alsa direct rather than for pulseaudio. # o /etc/asound.conf defaults.pcm.rate_converter "samplerate" Any clues? Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 12

[opensuse-factory] Fate #306591: entropy daemons in 11.2 - Kernel Removal IRQF_SAMPLE_RANDOM
by Rob OpenSuSE 10 Dec '09

10 Dec '09

I have taken an interest in Fate #306591 https://features.opensuse.org/306591 Andreas Jaeger has mused on community volunteer to package something. Now, I took a look at few suggestions, but 2 of them weren't "just work" in sense that they required webcam or mic, which seems like a possible can of worms to me. So I wondered about using timing jitter from user space? As a prototype I've knocked up short piece of C, which uses calls : nanosleep( &tsleep, 0); clock_gettime(CLOCK_REALTIME, &ttnow) This has been tested on i686 Athlon MP & P4 (Celeron Willamette) and x86_64 Athlon 64 x2; and I do appear to get a useful amount of unpredictable bits from this, even if the raw timings are not random. The timing jitter provides an externally unobservable measurement, and would allow sysadmin to tune to some extent eg) run 10 times/s (80bits/s) - 25 times/s (400bits/s). If this sounds like a useful approach, then I'd propose to continue on and develop a small daemon which gathers entropy bits from timing unpredictabilities caused by scheduler & interrupts, and also periodically gathers extra entropy (especially on startup) borrowing from techniques uses in the perl egd daemon (which would need modifying in any case). Obviously I'm a bit concerned about any move on power saving, this would obviously requires N wake ups, perhaps precautions would be needed to avoid them getting squeezed together by power saving patches which aim to batch up, code that sleeps like this? Rob -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2

[opensuse-factory] [ANNOUNCE] Using the new accessibility stack in GNOME for Factory
by Vincent Untz 10 Dec '09

10 Dec '09

Hi, (please follow-up on opensuse-gnome, unless you have a cross-desktop point) People have been working on a new accessibility stack based on dbus for the past few months, and even though we had preliminary packages in 11.2, it was not really ready for real-world testing. We're reaching this point today. I opened a feature [1] to track this. The goal of doing this change now is to test this new stack, and help us decide if we want to use it in 11.3, or not. This should also help upstream find and fix bugs in the new stack. But for this to really work, we need help from people. How can I help? =============== If you know accessibility, you can certainly help. You'll need factory (or a development version of 11.3), and you'll need to make sure the new stack is installed. And then, just try some accessibility features to see what works, what doesn't work, etc. If you don't know accessibility, just join the GNOME accessibility effort: people will help you start. They have a good wiki page [2] that is the first place you should look. How can I have the new stack? ============================= Make sure at-spi2-core is installed. If you have gtk2, you should automatically get at-spi2-atk too. That's all. You're done. How can I switch to the old stack? ================================== Both stacks are parallel-installable. To use the old stack, you simply need the at-spi package, and you should set the /desktop/gnome/interface/at-spi-corba gconf key to true. While the two stacks are parallel-installable, I'm unsure that using the old one when the new one is installed works (it should, but there might be bugs). If this is the case, you can remove the old stack. But please file a bug too. Why a new stack? ================ The rewrite of the stack was triggered by technical reasons (moving away from corba to dbus). So the goal is not to propose new features, or to remove anything. But there'll probably be regressions. This rewrite should also help KDE share the same infrastructure; I think this is still something being worked on, though (someone else might be better informed). What changes? ============= For people not using accessibility, nothing should change. For people using accessibility: - you should be able to use orca and accerciser in the very same way - I believe the magnifier and the on-screen keyboard will not work fine (gnome-mag and gok). I'm actually not sure we can make them work with the new stack, so maybe we'll have to switch back because of this - accessibility of bonobo objects (that's mainly panel applets at this point) will likely be broken. Vincent [1] https://features.opensuse.org/308451 [2] http://live.gnome.org/Accessibility -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0