November 2010 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Introducing wicked
by Olaf Kirch 26 Nov '10

26 Nov '10

Presenting wicked network configuration ======================================= This is the first public release of wicked, an experimental framework for network configuration. You may ask, don't we have enough of those already? Don't we have NetworkManager, connman, netcf, and a few more? The point I started from was the desire to unify what is usually provided through the traditional ifup script kudzu, with some of the more desktop oriented services provided by facilities like NetworkManager. I also wanted to move towards a more powerful set of functionality written in C, which is able to subsume functionality provided by ifconfig, ip(8), brctl, vconfig, ethtool, etc, and be able to drive these through an extensible XML representation of the network configuration. Kind of the Grand Unified Theory of network configuration :-) Right now, this implementation uses a daemon service and a command line utility. These two communicate securely via a local UNIX socket, allowing the server to validate the client's user id. The server offers a REST interface to various aspects of network configuration. The client application uses REST calls to retrieve interface configuration and status, or to reconfigure interfaces. The path space used by the API can be extended to cover other aspects of network configuration as well, such as reading, writing and restoring the resolv.conf file. After having hacked on this for a while, I want to release this to the community for feedback. If you're interested in finding out more, you will find a README and several manpages in the source code, which is available from http://gitorious.org/wicked Regards, Olaf Kirch <okir(a)suse.de> -- Neo didn't bring down the Matrix. SOA did. (soafacts.com) -------------------------------------------- Olaf Kirch - Director Server (okir(a)novell.com) SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

6 6

[opensuse-factory] Proposal for a multimedia team.
by Dave Plater 26 Nov '10

26 Nov '10

Hi, we need a multimedia team, I know from watching submit requests that there are at least three other potential members besides me. A little bit more communication between us would be beneficial to the mmaps and mmlibs projects especially multimedia:libs which contains packages that can wreak havoc if broken. ATM when I need help I use the packaging list but sometimes the help is blind to the needs of multimedia ie. jack, it would be nice to be able to discuss these things with more experienced multimedia oriented people. I've cc'ed this to opensuse-multimedia list but I wonder how many people actually subscribe to it? Regards Dave P -- 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] RFC: syslog-ng 3.2 beta1
by Peter Czanik 25 Nov '10

25 Nov '10

Hello, Syslog-ng 3.2 beta1 was released over the weekend. It has many interesting new features: - modularized, so /usr is no more a problem - patternize - automatic pattern generation from logs - correlation - for more info see blogs - SCL - a config library to ease configuration generation For a complete list of changes, see the lead developers blog: http://bazsi.blogs.balabit.com/2010/10/syslog-ng-ose-3-2beta1-released/ The final version of 3.2 will be released before openSUSE 11.4 feature freeze, so I'd like to update syslog-ng to 3.2. Questions / problems: - it is not yet a final version. Can I push it to factory (once some problems are solved), or I need to wait for the final release coming end of November? - for database support, libdbi is needed. Currently it is available only in Contrib. Could it be imported to factory so database support could be enabled? - I get one error and some warning messages regarding libraries. Could someone take a closer look at them and help me out? - AppArmor: there are some new files and directories, which is an easy fix (see below). The problem is SCL, but also affects syslog-ng.conf, if someone wants to call an external application as log source or destination. I got some advice previously, but that did not help, calling external apps still does not work, only when disabling AppArmor completly. For now I don't use the new features from SCL to avoid this problem, but would be nice, if we could demo some easy steps to modify /etc/apparmor.d/sbin.syslog-ng than saying that if one needs to call external apps, then should disable AppArmor... A working but not yet perfect version of syslog-ng 3.2 beta1 is available in the oBS: https://build.opensuse.org/package/show?package=syslog-ng32&project=home%3A… - it has glib fixes for factory (thanks go to cristian.rodriguez(a)opensuse.org) - ssl is enabled - no database support yet (libdbi is in contrib) - system() from SCL is not yet used due to AppArmor troubles - AppArmor needs some manual editing: --- sbin.syslog-ng.orig 2010-07-05 13:21:25.000000000 +0200 +++ sbin.syslog-ng 2010-09-29 10:09:51.001748203 +0200 @@ -36,9 +36,10 @@ /etc/hosts.deny r, /etc/hosts.allow r, /sbin/syslog-ng mr, + /usr/share/syslog-ng/** r, # chrooted applications @{CHROOT_BASE}/var/lib/*/dev/log w, - @{CHROOT_BASE}/var/lib/syslog-ng/syslog-ng.persist rw, + @{CHROOT_BASE}/var/lib/syslog-ng/syslog-ng.persist* rw, @{CHROOT_BASE}/var/log/** w, @{CHROOT_BASE}/var/run/syslog-ng.pid krw, @{CHROOT_BASE}/var/run/syslog-ng.ctl rw, Please give it a try, let me know if you have any problems or fixes (sr :-) )! Bye, -- Peter Czanik (CzP) <czanik(a)balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 5

[opensuse-factory] systemd integration - sysvinit compatibility?
by Per Jessen 25 Nov '10

25 Nov '10

Having just read Kays posting about system integration, one question that came to mind was: how about sysvinit compatibility for user-written sysvinit scripts - will they continue to work or will we need to rewrite/rework them? -- Per Jessen, Zürich (0.0°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2

Re: [opensuse-factory] getting LLVM into factory
by Duncan Mac-Vicar P. 25 Nov '10

25 Nov '10

On 11/23/2010 04:06 PM, İsmail Dönmez wrote: > Sure thing, I'll be working on this coming weeks. BTW LLVM 2.8 is already on devel:tools:compiler It builds fine, but it has apidocs generation disabled as those fail. I will submit to Factory once that is fixed. If anyone wants rights to touch the package, just ask me. -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ 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

2 1

[opensuse-factory] Status: Distribution
by Stephan Kulow 25 Nov '10

25 Nov '10

Hi, Normally I would upload Milestone4 to the mirrors around now, but unfortunately my own experience in using Factory right now forbids this. There are too many regressions in there atm - I don't even have network (possibly already fixed in http://bit.ly/f8yt6S) So I would like to have them fixed first and then release early next week. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 5

[opensuse-factory] RFC: glib version for openSUSE 11.4
by Vincent Untz 25 Nov '10

25 Nov '10

Hi, I just found out about https://bugzilla.novell.com/655561. The short story is that the update to glib 2.27 is breaking LXDE (and maybe XFCE, not sure) at the moment, because an extension point in glib got removed. That's my fault as I didn't think it would impact something else than GNOME. Apologies for breaking stuff. The extension point that got removed is used to know which application should be used to open a URI scheme (for example: mailto => evolution). The reason it got removed is that instead of using a desktop-specific approach, it was decided to put the relevant information in .desktop files and use the MIME type system for this. This means that glib can handle this properly by itself, instead of requiring a desktop-specific extension. I explained this in http://lists.opensuse.org/opensuse-gnome/2010-10/msg00021.html It's worth pointing out that upstream believes that the extensions points are not part of the API/ABI stability guarantee. We were planning to use glib 2.28 in openSUSE 11.4 as it'll get released in December, and will help provide a GNOME 3 preview. However, the fact that this breaks other desktop is something that means we should revisit this decision. As explained in the bug, I see three options: a) keep glib 2.28. This implies that we need to fix the extensions provided by LXDE (and maybe XFCE?), and that we should fix .desktop files as explained in my mail to opensuse-gnome earlier. Both of those are not difficult, and it's future-proof: that is what is going to happen upstream. b) go back to glib 2.26. This should be okay, but it might break a few packages. It will break the whole gtk3 stack for sure, at least, since it requires glib 2.27/2.28. So this means accepting that we won't have gtk3 at all in openSUSE 11.4. (It will make the job of doing a GNOME 3 Preview much harder) c) patch glib 2.28 to add back the extension point. We have two sub-options here: c1) add the extension point just to keep the ABI. This means the extensions won't be used at all, and we still need to fix .desktop files. c2) revert the change completely in glib 2.28, and make use of the extensions again. I'd like to hear what people think. FWIW, we had chosen option a when we thought it only implied GNOME. I still think it's the right approach, though. Thanks, Vincent -- 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

7 8

Re: [opensuse-factory] Status: Distribution
by Karsten König 24 Nov '10

24 Nov '10

Am Mittwoch, 24. November 2010, 11:52:17 schrieb Vincent Untz: > Le mercredi 24 novembre 2010, à 11:14 +0100, Stephan Kulow a écrit : > > Hi, > > > > Normally I would upload Milestone4 to the mirrors around now, but > > unfortunately my own experience in using Factory right now forbids this. > > > > There are too many regressions in there atm - I don't even have network > > (possibly already fixed in http://bit.ly/f8yt6S) > > > > So I would like to have them fixed first and then release early next > > week. > > Is there a list of regressions people can help with? Or do we already > have people working on all of them? > > Thanks, > > Vincent There is a pretty cool result page for the automated image testing but I lost the url and can't find it on the testing team wiki =/ It was suggested that the page is a good reference point on the usability of factory, might also be fine for finding big regressions and tracking down at what time it broke Cheers, Karsten -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 2

[opensuse-factory] zypper in opera
by Donn Washburn 24 Nov '10

24 Nov '10

I loaded only zypper in opera from known repos sites And as usual openSuSE 11.4 M3 is replying with an error. /home/donn # opera < as root or user No protocol specified opera: cannot connect to X server :0. Error: Connection refused opera [crash logging]: CRASH!! /usr/lib/opera/opera got signal SIGSEGV at address 0805AB8B Log was created here: /var/tmp/crash20101123191540.txt Killed This KDE 4.5.# control of everything is a problem. DRM and nouveau and security is ruining openSuSE Linux When nouveau substituted NVidia-#.run things went down hill. -- 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 -- 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] Building kernel modules for Factory fails
by Stephan Kleine 23 Nov '10

23 Nov '10

Hi guys, 2nd try since the last one remained unanswered: I noticed that all my modules built for factory currently fail with: RPM build errors: File not: found: /usr/src/packages/BUILDROOT/r8168-8.020.00-1.1.i386/lib/modules/Updating- xen File must begin with "/": 2.6.36-18 Which doesn't make much sense to me since I, naturally, don't have a %files section in my .spec. Examples are e.g. the stuff in "drivers:nic". Also there were several other people e.g. in -buildservice who run into the same problem. Is that a bug or was there some change regarding how to build kernel modules? regards, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] evince can't be called as root
by Werner LEMBERG 23 Nov '10

23 Nov '10

[evince 2.32.0-1.1] I'm using KDE on my GNU/Linux box which I've completely updated to factory a few days ago, and calling evince as non-root works just fine. However, calling it as root it aborts with Failed to get bus connection: The connection is closed ** GLib-GIO:ERROR:gdbusconnection.c:2152:initable_init: assertion failed: (connection->initialization_error == NULL) Is this a known problem? Werner -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

7 10

[opensuse-factory] rsyslog vs. syslog-ng
by Peter Czanik 23 Nov '10

23 Nov '10

Hello, No, this e-mail is not about features, as I'm quite biased on the topic, see my signature :-) It's about installation. Right now one needs to fight with the base system and know quite a lot of about how syslog is implented in openSUSE if one wants to run syslog-ng. The problems seems to be, that rsyslog is tied too deeply to the base system: linux-ym5q:/var/log # rpm -e rsyslog error: Failed dependencies: rsyslog is needed by (installed) patterns-openSUSE-base-11.3-30.1.x86_64 If I remove it during installation, it will result in a broken system (at least was so when I last tried). If I remove it later by rpm, it comes back with an upgrade. Which is obviously not a nice situation, considering, that if rsylog is present on the machine, then it is started even if syslog-ng is installed. Even if I set SYSLOG_DAEMON to "syslog-ng" in /etc/sysconfig/syslog, it is set back to "" or "rsyslog" when rsyslog is updated. So right now the only situation when syslog-ng works correctly on openSUSE, when I remove rsyslogd after(!) installation by breaking patterns-openSUSE-base and lock it, so it can't come back. Well, lets say, that it's an ugly solution... I'd like to ask how resolve this situation. I'm quite sure, that rsyslog needs to be removed to patterns-openSUSE-base. But I'm not so sure in the next steps as I'm not (yet) an rpm expert. Could all of the syslog packages provide "syslog" functionality, which is required by the base pattern, and the syslog packages (rsyslog, syslog-ng and syslogd) conflict each other? This way syslog was still required, but only the chosen implementation would be installed on the system. Bye, -- Peter Czanik (CzP) <czanik(a)balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

8 9

[opensuse-factory] getting LLVM into factory
by Duncan Mac-Vicar P. 23 Nov '10

23 Nov '10

LLVM is getting popular as BuildRequires for other packages. Right now the rubinius, Mono, Freemat matlab clone and even the KDE Unstable repo needs it. As an extra, you get clang, a C/C++ compiler which is very interesting as it can be used as a library and/or static analyzer. Actually FreeBSD builds now entirely with clang and it seems the BSD world is trying to do a switch from gcc. I have updated the packman package to 2.8 (latest) release (home:dmacvicar/llvm). There is only a bug left with apidocs/doxygen, which are right now disabled by default via a bscond. I would like to submit this package to a "right project". devel:tools:compiler looks like the best right now. Yes, I volunteer to be the maintainer. I admit I am not experienced enough yet with it, but it will improve :-). The original package maintainers are also invited to co-maintain. Once it is on a project, I would like to get it into Factory so that it shows up on 11.4. I guess the packman people could try to get my changes back into packman, except for factory where we should have a common one. Cheers Duncan PD: BTW, I tried to look for the Mono maintainers email by doing rpm -q --changelog mono-core, and the result is empty. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

8 20

[opensuse-factory] universal package names
by jdd 22 Nov '10

22 Nov '10

Hello, I'm in a dependency hell trying to make a perl application work (not to be discussed here), mostly because packages don't have the same name in openSUSE and ubuntu. is there any page on the wiki or elsewhere giving compatibility between distros on package level? if so it should be better advertised, if not, may be created? thanks jdd -- http://www.dodin.net http://pizzanetti.fr -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] Procmail is not mantained
by Carlos E. R. 22 Nov '10

22 Nov '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have been told by the fetchmail people that procmail has been without upstream maintenance for years (10 years!), and they strongly recomend using maildrop instead. Wikipedia concurs on this. I'd be happy to keep using procmail, but the abandoware status for an important package scares me. A lot. Does openSUSE have a recomendation on this, as a project? I've been checking this, but maildrop depends on the entire courier-imap package - this won't do. I'm told that there is no such dependecy, on source. Can this dependency be removed? Or do you want a Bugzilla report instead? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAkzir5EACgkQtTMYHG2NR9WFRACeMs9PL2DIk8+Lc0TPruJ4fHP5 pgwAn3JQSy1vhqGB5V6ZXEQ6gCmKNE6W =3pr2 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

18 73

[opensuse-factory] syslog-ng apparmor question
by Peter Czanik 21 Nov '10

21 Nov '10

Hello, I'm trying to package syslog-ng 3.2-git, and ran into some troubles. V3.2 has an interesting new feature, called SCL (system configuration library), which tries to ease syslog-ng configuration. This works nicely when apparmor is disabled. SCL uses a script to generate part of the configuration. So, when system(); is used in syslog-ng.conf, it actually calls a script, which generates the missing parts based on the OS. In case of Linux, it's: linux-6y8u:~ # /usr/share/syslog-ng/include/scl/system/generate-system-source.sh unix-dgram("/dev/log"); file("/proc/kmsg" program-override("kernel") flags(kernel)); When apparmor is enabled, this script is not run, instead I see "permission denied" in the strace output. Question: how should I modify /etc/apparmor.d/sbin.syslog-ng to be able to run external scripts and/or applications. This is not only a problem for SCL, but syslog-ng can use these both as log source and destination. Once a solution is know, I'd put some comments in sbin.syslog-ng, so users could extend the AppArmor ruleset easily instead of disabling it... Bye, -- Peter Czanik (CzP) <czanik(a)balabit.hu> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 8

[opensuse-factory] Fwd: observed significant performance improvement in XFS a real-world application
by Linda Walsh 21 Nov '10

21 Nov '10

Forward this from the linux-xfs list, in hoping that decision-makers will consider XFS as the default suse OS install choice. It continually bests other file systems in optimized configuration performance tests and these new improvements sound like they only add more speed to the equation. For nearly all systems, disk speed is the bottle neck, so using the best solution possible should be strongly considered the default choice for all users -- regardless of 'political' concerns (which seem to often over-rule practicality, unfortunately). Linda p.s. I am not part of the xfs project. I've just used it with open suse (or previously, Suse) since ~ 2002 and have never regretted it. Current filesystem read rates using XFS are about 1GB/second on sustained multi-gigabyte reads. Using 1Gbit ethernet, Samba gets 97MB/s read from disk to 115 MB/s read from memory and 125MB/s writes to memory or disk. -------- Original Message -------- Subject: observed significant performance improvement using "delaylog" in a real-world application Date: Tue, 10 Aug 2010 18:01:33 +0200 From: Peter Niemayer <niemayer(a)isg.de> To: linux-xfs(a)oss.sgi.com Hi all, we use XFS for a very I/O-intensive, in-house developed real-time database application, and whenever we see new or significantly changed file-systems becoming available, we run a benchmark using this application on a conserved, fixed real-world data set. I'm pleased to state that using the experimental "delaylog" mount option (in vanilla linux-2.6.35) we measured a 17% performance increase for our benchmark scenario. (Other mount-options in use both before and after the "delaylog" option: noatime,nodiratime,nobarrier) That's a lot given that XFS was the fastest performing file-system for this application already. It's also a promising result regarding stability, as several other tests (using e.g. reiser4 or ceph) in the past led to crashes in the same benchmark scenario. So thanks to all contributing developers for this significant optimization! Regards, Peter Niemayer _______________________________________________ xfs mailing list xfs(a)oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

17 42

[opensuse-factory] glibc plans for 11.4
by Petr Baudis 21 Nov '10

21 Nov '10

Hi! My original plan has been to have glibc-2.13 in 11.4, however it is still completely unclear when will it be actually released. In case it is not soon enough, I would prefer to stay with glibc-2.11 in 11.4 instead of upgrading to glibc-2.12. Downsides are not terribly huge: - Missing these: * New interfaces: pthread_getname_np, pthread_setname_np * New Linux interface: recvmmsg * STT_GNU_IFUNC implemented for Sparc by David Miller. * The dynamic linker now recognizes supported ABI versions from the EI_ABIVERSION field in the ELF header. * New locales: kok_IN, sq_MK, cv_RU - Missing few more SSE string routine ifuncs. This can be also regarded as a plus since there are probably still some bugs lingering within, but it means SUSE won't be part of the testing process... Upsides: - 2.11 stable branch is getting a lot more bugfixes than 2.12 stable branch, therefore it should be less buggy and this gap will still widen over time - 2.11 is also better tested - Easier maintenance for me ;-) Does anyone have an opinion either way? And when would be the last suitable moment for glibc-2.13 entering Factory? Thanks, -- Petr "Pasky" Baudis The true meaning of life is to plant a tree under whose shade you will never sit. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

11 23

[opensuse-factory] pullin-msttf-fonts doesn't work
by Werner LEMBERG 20 Nov '10

20 Nov '10

In factory, installing pullin-msttf-fonts-11.4-1.8 doesn't trigger the installation of the MS TTFs. There is a line Recommends: fetchmsttfonts in the RPM but this script seems to be missing. Werner -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

7 9

[opensuse-factory] getting patch2mail into Factory
by Christian Boltz 20 Nov '10

20 Nov '10

Hello, I'll send a SR to include patch2mail in Factory in some minutes. Some information about the package according to http://en.opensuse.org/openSUSE:How_to_contribute_to_Factory : > the name and purpose patch2mail is a small script that sends a mail to root if new patches are available. It runs via cron.daily. On the technical side, it uses "zypper --xmlout lu -t patch" and xsltproc to make the output human-readable. > how long has it been around? It's in the Contrib repo since 11.2, and has been in my home repo before. Since some days, it's also in system:packagemanager which will be the devel project. patch2mail supports all zypper versions since openSUSE 10.2 (as long as you build for the respective release), but in practise this won't help you much for the no longer supported releases ;-) In theory the 11.1 package should also work for SLES 11, but I never had a SLES installation available to test it. > how well has it been tested? Since it consists only of a small script and some XSLT, there isn't too much to go wrong ;-) Changes in the commandline parameters or XML format of zypper are the only exceptions (both happened already in older distribution releases). That said: Well-tested on 11.3 and older, not yet tested in Factory by me because I'm still on 11.3. As long as the zypper interface didn't change, it will also work in Factory. > what is the upstream project? "project" is a big word for 16 lines of shell script and 120 lines of XSLT ;-) but basically I am also the upstream developer. I'll announce new versions etc. in my blog - http://blog.cboltz.de or http://blog.cboltz.de/plugin/tag/patch2mail if you want only articles about patch2mail. > does it have a track record of security issues? No :-) > what is the purpose of having it in the distribution? It is a useful tool for servers (where you don't have a desktop to show the update applet ;-) to inform the admin when new updates (to be exact: patches) are available. > who are its users? Administrators of servers - and of any system you don't use personally (for example if you have to maintain some desktops in the office). > what is the license? GPL 2 or later Regards, Christian Boltz -- "What, you don't think "insmod emacs" is a good idea?" -- Joe Moore -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 1

[opensuse-factory] Adding mintmenu to openSUSE
by william witt 20 Nov '10

20 Nov '10

On Fri, Nov 19, 2010 at 1:14 PM, Nelson Marques <nmo.marques(a)gmail.com> wrote: > > Hi, > > Though I'm not an expert, I would probably recommend you to install > spec-cleaner from Vincent Untz home[1] project and run it on the spec > file. I've now done and am building the result on my "unstable" home repo. > > Additionally I would also consider you to check out if mint slab menu > is to use with GNOME, if so... You might want to try to submit request > it to GNOME:Apps, and eventually sign the opensuse-gnome mailing list. MintMenu is primarily used on GNOME, but can be used anywhere (like I said in my OP, I've used it in it's own window on FluxBox and OpenBox). If it fits better as a GNOME app, I can submit it there. > > There are a couple of stuff you can improve on the spec... the > %find_lang macro is one of the things that pop into sight. I was unfamiliar with the %find_lang macro until rpmlint started complaining about it the .mo files not being in %lang. In fact I didn't worry about localisation in general until on of the users I have wanted it translated into Spanish. I pulled in the translations from Linux Mint, but all of their translations are in one package and distributed as one tarball (so I have to pare that list down into just mintMenu translations). What I ended up with is admittedly kludgey, but works and does not make rpmlint complain. In the end what I really need is a good example on how to appropriately use %find_lang and %lang; I tried googling but didn't see any real examples, mostly unanswered questions on how to use it or errors people were getting. Will -- 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] Libraw1394-8 and the state of linux h323 and other telephony [RFC]
by Dave Plater 20 Nov '10

20 Nov '10

Hi, I innocently updated a very old libraw1394 a month and a half ago, realizing that a lot depended on it I was careful to try not to break the system but it seems it was like cleaning a mark on the wall to find out that the wall was rotten under the paint layer. I'm assuming that VoIP telephony isn't messed with because it just works but all of the associated software, with the exception of h323plus and GNOME:Factory opal (VoIP) which has updated to the latest since the libraw1394 update. I don't know the state of the other telephony apps that use libraw1394 but I'm pretty sure that any package that fails due to a missing libraw1394.so.8 is depreciated. Anyway this has come back to haunt me and I'm creating the package libraw1394-8 to prevent a sudden loss of telephony packages, it's not as easy as I thought, I have to move the headers in the devel package into a named directory to prevent a conflict with libraw1394-devel. IMHO the VoIP packages need an overhaul so any help will be appreciated - home:plater libraw1394-8, I'm slowly getting snowed under and although I learn rapidly by finding things out by trial and error this time I need some more experienced help to speed the process up. Thanks Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 8

[opensuse-factory] Firefox 4 plans for Factory
by Wolfgang Rosenauer 19 Nov '10

19 Nov '10

Hi, I've been preparing Firefox 4 since quite some time in mozilla:beta (and previously :alpha) and I run it everywhere meanwhile. The initial Firefox roadmap said it would have been ready by october this year but was slipped to something "early 2011" https://wiki.mozilla.org/Firefox/4/Beta which would still fit into the openSUSE 11.4 release. There are still some issues and quite some not updated extensions but to get proper testing I think it makes sense to go for Firefox 4 in Factory soon. My plan is to do the update before Milestone 5 (actually right after milestone 4 to get a feeling before M5 gets done). I do _not_ plan to have an easy fallback to Firefox 3.x in Factory but it will be available in the mozilla repository as always. The reasons are: 1. it's extra work to have a package available for parallel installation 2. the much more important one: There is always a risk for user profiles when doing major downgrades. Please tell me if there are strong arguments not to do it this way. Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 9

[opensuse-factory] Adding mintmenu to openSUSE
by William Witt 19 Nov '10

19 Nov '10

I've been packaging mintmenu (for both SUSE and Fedora) for a while on my own using my home project on OBS. I'd now like to go about getting it included in the openSUSE repositories. For those that don't know, mintmenu is the default menu from Linux Mint, it's written in python and distributed under GPLv2. While it's uses pygtk, and is primarily used in gnome, it can be used in other desktop environments also (I've used it in it's own window with OpenBox and FluxBox). It provides a list of favorite applications, as well as a searchable menu of installed applications. I love using mintmenu over the alternatives and believe that other users would enjoy it as well, if it were installable from official channels. I'm unsure, however, which devel project I should submit it to. Any help in getting the ball rolling would be helpful. My home project: https://build.opensuse.org/project/show?project=home:unamanic Closest thing to upostream: tarballs: http://packages.linuxmint.com/pool/main/m/mintmenu/ git: https://github.com/linuxmint/mintmenu Thanks in advance, Will -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 4

[opensuse-factory] Building kernel modules for Factory fails
by Stephan Kleine 19 Nov '10

19 Nov '10

Hi, I noticed that all my modules built for factory currently fail with: RPM build errors: File not: found: /usr/src/packages/BUILDROOT/r8168-8.020.00-1.1.i386/lib/modules/Updating- xen File must begin with "/": 2.6.36-18 Which doesn't make much sense to me since I, naturally, don't have a %files section in my .spec. Examples are e.g. the stuff in "drivers:nic". Is that a bug or was there some change regarding how to build kernel modules? regards, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0