November 2010 - openSUSE Factory - openSUSE Mailing Lists

[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