openSUSE Factory July 2010

factory@lists.opensuse.org

118 participants
93 discussions

by Michal Seben

Hi all! Next week I will move cronie[1] package to Factory, so it will replace old cron. If someone is against this step, please just write what's wrong. As I announced earlier, you could find Cronie in Base:System repo [2] there is also prepared wiki about known changes after switch to cronie [3] [1]https://fedorahosted.org/cronie/ [2]https://build.opensuse.org/package/show?package=cronie&project=Base%3ASys… [3]http://en.opensuse.org/Cron_replace#Differences_between_old_openSUSE.27s_… -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

9 years, 5 months

syslog-ng update

by Peter Czanik

Hello, I prepared updated syslog-ng packages with the close supervision of Marius Tomaschewski, the maintainer of the syslog-ng package. They are available in home:czanik in the openSUSE BS. I would like to see these packages included in Factory, to replace the ancient 2.0 syslog-ng, but MT seems to have disappeared (no response to e-mails in the past two weeks). Questions: - it works fine on my machines, but could anybody else test it? - what is the proper way to get syslog-ng updated in factory, if the maintainer seems to be unavailable? - I have now both 3.0 and 3.1 packages there, called syslog-ng and syslog-ng31. The ultimate goal is to include 3.1. Should I drop the current syslog-ng package and rename syslog-ng31 to syslog-ng? Bye, CzP -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

9 years, 11 months

Is the upgrade from 32 bits to 64 bit supported? Question for devs O:-)

by Carlos E. R.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm asking here a question not related to factory directly, because I want to reach the devs. You can reply on opensuse list instead if you prefer. To keep it short (longer post in the opensuse list), I'm attempting to upgrade from 11.0 to 11.2 (32 bits) using the retail DVD, wich turns out it has only the x64 version. It offers to upgrade to 64 bit the 32 bit install: The architecture of the system installed in the selected partition is different from the one of this product" [continue] [cancel] I said "continue", then I checked the package list. As far as I could see, it intended to replace all packages with those corresponding to the 64 bits version. If this works, fine... but I was afraid, and I cancelled. Not because risking data (it is a copy), but because of possible waste of time. I thought I'd better RFC. Has anybody done this, an upgrade from 32 to 64 bits? Does it work? Is it "supported"? - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAktvNHIACgkQU92UU+smfQVsTwCfSYFG8N7Owo/PWNu0ylYKGqmr fuQAoJQSLDrMlTDMYeRihU5SfBa0fVz8 =zvu9 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

10 years, 1 month

Status: distribution

by Stephan Kulow

Hi, Not much news, but I put a first scretch of an 11.4 roadmap here: http://www.suse.de/~coolo/opensuse_11.4/ But I'm thinking about leaving out Milestone1 (which of course would actually mean Milestone7 is Milestone6 ;) - mainly because I'm on vacation in august, but I know many more are. As the feedback for the 11.3 release was pretty small I did the 11.4 roadmap very much based on the 11.3 data - with a bit more room around new year. We'll see how this works out - KDE 4.6 should at least fit perfectly for the last milestone and I have not yet seen plans for the release after GNOME 3.0, so I don't know - but I guess 11.4 will have GNOME 3.0.X. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

10 years, 3 months

removing xulrunner 1.9.1.*

by Wolfgang Rosenauer

Hi, now that 11.3 is released I will request removal of mozilla-xulrunner191 as it won't be supported for openSUSE <next> anymore (most likely). osc shows the following dependencies: mozilla-xulrunner191 : OpenOffice_org OpenOffice_org-bootstrap OpenOffice_org-components OpenOffice_org-libs-extern chmsee kdebase4-workspace libgluezilla0 moonshine These packages need to be checked if it's possible to build them against xulrunner192 or if the deps are bogus (inherited from a package down the chain?). Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

10 years, 3 months

wireless - iwlagn Microcode SW error

by Juergen Orschiedt

I repeatedly see "Microcode SW error detected. Restarting" in /var/log/messages when I connect to a 802.11n network. As side effect, connection speed drops to 1MBit/sec. Problem doesn't show up when connecting against 802.11ab. Hardware is Latitude E6500 with 2.6.34-9-desktop x86_64 kernel. Jun 10 08:13:40 .. iwlagn 0000:0c:00.0: Microcode SW error detected. Restarting 0x2000000. Jun 10 09:17:50 .. iwlagn 0000:0c:00.0: Microcode SW error detected. Restarting 0x82000000. Jun 10 09:17:50 .. iwlagn 0000:0c:00.0: Microcode SW error detected. Restarting 0x82000000. Jun 10 09:23:53 .. iwlagn 0000:0c:00.0: Microcode SW error detected. Restarting 0x2000000. cheers, Jürgen -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

10 years, 3 months

few tips for crash catching, work with core files, debuginfo installation

by Stanislav Brabec

Well, some applications in 11.3 accidentally crash. But most of them does not want to crash in a moment I am debugging them in the gdb, I searched in the documentation and found a simple solution. Collect cores: 1. Set SOFTCORELIMIT in /etc/sysconfig/ulimit to "unlimited" or do this just now by: ulimit -c unlimited 2. mkdir /cores ; chmod +t /cores ; chmod og+rw /cores 3. Add a line to /etc/sysctl.conf: kernel.core_pattern = /cores/%e-%t-%u.core or do this just now by: echo "/cores/%e-%t-%u.core" >/proc/sys/kernel/core_pattern Core files will be stacked to /cores and ordered by application name and time and will never overwrite. You can easily find a most crashing application there. Install debuginfo: gdb often complains on missing debuginfo packages. You can easily install all of them by copy and paste it to the console input of following command: eval zypper install $(sed -n 's/Try: zypper install//p') Well, you can do the same using the gdb log file and then reading it: eval zypper install $(sed -n 's/Try: zypper install//p' <gdb.log) And in gdb use: Nebo v gdb set logging file gdb.log set logging file on set pagination off attach {pid of application I want to debug} detach attach {pid of another application I want to debug} Well, and if you have a core file, do the final well known: bt or thread apply all bt Notes: Don't forget to check the backtrace in Bugzilla and submit unique crashes. If it is an accidental crash, it makes sense to submit the backtrace to the upstream Bugzilla, if the crash makes a big problem to use particular application or if you suspect that it is openSUSE specific, submit it to the Novell Bugzilla as well. Well, if the core comes from npviewer, feel free to run: rm /cores/npviewer* It does not make sense to report them anywhere. All these crashes I have seen were triggered by Adobe Flash or Adobe Reader and I have no chance to fix them. Wanted: An easy manual how to be always ready for kernel crash dumps. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 966, +49 911 740538747 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

10 years, 3 months

Call for Testers : Compiz 0.9.0

by Dominique Leuenberger

Dear All, Factory has been opened again and we start getting wild. As many of you doubtlessly heard or read ( http://dominique.leuenberger.net/blog/?p=112 ) Compiz 0.9.0 has been released. This marked the first released snapshot of the new C++ rewrite of Compiz (the rewrite was not just to purely change the language, but a lot of limitations were removed, and serialization using libboost for example added). Now as Factory is open again, I will prepare the packages in X11:Compiz to be updated to 0.9.0 and then forward them to Factory. As brave Factory user, I would like to 'warn' you about any possible breakage from this update (even though I don't hope for any). Should you see any bugs, feel free to report them in the usual way in Bugzilla, component Compiz. As we have a good link to the upstream project I'm confident that we will be able to resort any kind of problems we might run into. Users that are running Compiz 0.8.6 on their systems and that have X11:Compiz enabled might want to switch to X11:Compiz:Compiz-0.8, which contains the Compiz 0.8 bugfix tree (currently still at 0.8.6). Hope you will continue having a lot of fun, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

10 years, 3 months

openSuSE and Flightgear

by Donn Washburn

OpenSuSE 11.3 GM seems to have a problem with either KDE or nouveau kernel module. I have downloaded and compiled two different git weeks and still have the same problem after git Simgear, Flightgear and FGData have been compled and reinstalled. That is that in both cases fgfs comes up with the bootsplash and seems to load models up the Scenery loading part and then crashes, blow up or whatever disappears. Anyone have an idea for seen the same. Both programs were checked and watched for compile errors none noted. I have removed most of the nouveau stuff and installed an NV.run module. And lsmod shows it is clean of nouveau which had bad GL problems. -- 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

10 years, 4 months

History function in zypper?

by Marcel Hilzinger

Maybe it's already there and I'm just missing something, but I just thought about a cool feature zypper hist showing you the packages installed and removed within last 24h or one week or one month. Is there already such a function? -- Mit freundlichen Grüßen, Marcel Hilzinger Linux New Media AG, Putzbrunner Str. 71, 81739 München, Germany Tel: +49 89 99 34 110, Fax: +49 89 99 34 1199 mhilzinger(a)linuxnewmedia.de - http://www.linuxnewmedia.de ---------------------------------------------------------- Linux New Media, the Pulse of Open Source: Lawrence, KS - Málaga Manchester - München - São Paulo - Warszawa ---------------------------------------------------------- Sitz der Gesellschaft: Putzbrunner Str. 71, 81739 München Amtsgericht München: HRB 129161 Vorstand: Brian Osborn, Hermann Plank Aufsichtsratsvorsitzender: Rudolf Strobl -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

10 years, 4 months

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory July 2010