May 2010 - openSUSE Users - openSUSE Mailing Lists

HP Laser 1020
by Alfredo Cole 08 May '10

08 May '10

Hi: I just bought this printer, thinking it would work right out of the box. I'm running SUSE 9.3 with CUPS, and it does not seem to support this model. Anybody got this printer to work? Any pointers would help. Best regards. -- Alfredo Cole-Tuckler

11 19

[opensuse] openSUSE Weekly News 122 is out!
by Sascha 'saigkill' Manns 08 May '10

08 May '10

We are pleased to announce: Issue 122 of openSUSE Weekly News is out! [0] [0] http://news.opensuse.org/2010/05/08/opensuse-weekly-news-122-is-out/ In this week's issue: * 1 Editors Note * 2 Announcements o 2.1 openSUSE 11.3 Milestone 6: The Dust Begins to Settle o 2.2 openSUSE News: Updates Go Twitter o 2.3 openSUSE News: openSUSE@LinuxTag 2010 * 3 Status Updates o 3.1 Distribution + 3.1.1 Thomas Biege: SELinux and openSUSE 11.3 Milestone 6 + 3.1.2 Bugzilla * 4 Team Reports o 4.1 Boosters Team + 4.1.1 What are the Boosters up to? + 4.1.2 Changes in Staff o 4.2 Build Service Team + 4.2.1 Build Team Meeting + 4.2.2 OBS 1.7.4 .... your weekend present ;) + 4.2.3 Build Service Statistics o 4.3 Mono Team + 4.3.1 Miguel de Icaza: MonoDevelop's New Search Bar o 4.4 openFATE Team + 4.4.1 Andreas Jaeger: Preparation for Mounting /var/run as tmpfs + 4.4.2 Clean temporary data in SUSE + 4.4.3 Rename chromium + 4.4.4 improve system administration from commandline + 4.4.5 Clean temporary data in SUSE + 4.4.6 osc multiple package submit request + 4.4.7 Statistics o 4.5 Translation Team + 4.5.1 Localization o 4.6 Wiki-Team + 4.6.1 Rajko Matovic: Wiki: Background + 4.6.2 Rajko Matovic: Expanding use of portal page concept * 5 In the Community o 5.1 Shayon Mukherjee: Part 1 : Marketing – the other way or the highway o 5.2 Events o 5.3 openSUSE for your ears o 5.4 From Ambassadors + 5.4.1 Agustin Chavarria: FLISOL Nicaragua 2010 + 5.4.2 Alex Barrios: Second round of pictures from the FLISOL Venezuela + 5.4.3 Roger Whittaker: Oggcamp event -- Liverpool + 5.4.4 Vincent Untz: Marketing Hackfest: Day 1 o 5.5 openSUSE in $COUNTRY o 5.6 Communication o 5.7 Contributors * 6 New/Updated Applications @ openSUSE o 6.1 xmms2 0.7-999.pm.57.3 (openSUSE 11.2/x86_64) o 6.2 Dominique Leuenberger: VLC 1.0.6 Packages for openSUSE o 6.3 Kohei Yoshida: mdds 0.3.0 released! o 6.4 Gabriel Burt: Banshee 1.7.0 * 7 Security Updates o 7.1 SUSE Security Announcement: Linux kernel (SUSE-SA:2010:023) * 8 Kernel Review o 8.1 h-online/Thorsten Leemhuis: Kernel Log: Coming in 2.6.34 (Part 3) - Graphics o 8.2 LinuxUSER&Developer/Jon Masters: The kernel column #86 o 8.3 Rares Aioanai: Kernel Review with openSUSE Flavor (Week18) * 9 Tips and Tricks o 9.1 For Desktop Users + 9.1.1 MakeUseOf/Ryan Dube: 3 Audacity Tips To Enhance Any Recorded Interview o 9.2 For Developers and Programmers + 9.2.1 HowtoForge/Falko Timme: How To Integrate ClamAV Into PureFTPd For Virus Scanning On OpenSUSE 11.2 * 10 Planet SUSE o 10.1 Holger Hetterich: SMB Traffic Analyzer v2 and the new clients o 10.2 Holger Hetterich: SMB Traffic Analyzer v2 on SambaXP 2010 o 10.3 Pascal Bleser: openSUSE repository URL shortening o 10.4 Cornelius Schumacher: The quest for the perfect permalink o 10.5 Andrew Wafaa: Getting openSUSE from A to Y o 10.6 Klaas Freitag: A Blog on Sourceforge o 10.7 Andrew Wafaa: openSUSE and the ways of a11y * 11 openSUSE Forums o 11.1 64 or 32 bit on core2duo? o 11.2 openSUSE 11.2 Graphics problem o 11.3 Help re-sizing or expanding SUSE partition o 11.4 openSUSE 11.3 M6 on 5 different PC's * 12 On the Web o 12.1 Announcements + 12.1.1 KDE Software Compilation 4.4.3 Released: Codename "cuality" + 12.1.2 Jason McDonald (Qt Development Frameworks): Qt 4.7.0 Beta1 o 12.2 Reports + 12.2.1 Phoronix/Michael Larabel: OpenSUSE Says Farewell To RadeonHD Driver + 12.2.2 Linux Journal/Justin Ryan: Linux Foundation Announces LinuxCon Keynotes o 12.3 Reviews and Essays + 12.3.1 OStatic/Joe Brockmeier: Too Many Forges, Too Little Time + 12.3.2 Computerworld/Steven J. Vaughan-Nichols: Linux needs to do more for programmers * 13 Feedback / Communicate / Get Involved * 14 Credits * 15 Translations For a list of available translations see this page: http://en.opensuse.org/OpenSUSE_Weekly_News/122/Translations -- Sincerely yours Sascha Manns openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English) -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] VNC to display on :0 (Suse 11.2)
by James D. Parra 08 May '10

08 May '10

Hello, Can someone direct me to a link describing how to have the vnc server allow connects to view what is on the local terminal. Tried; vncserver :0 Warning: server:0 is taken because of /tmp/.X0-lock Remove this file if there is no X server server:0 A VNC server is already running as :0 <snip> I am guessing X has exlusive use of :0. Many thanks in advance. James -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 3

[opensuse] Notepad++ replacement needed
by arygroup＠gmail.com 08 May '10

08 May '10

Hi, guys! OpenSuse 11.2, x64, KDE 4.3.5 I've been looking for a long time for something like notepad++. I want something enough light. I tried many editors. Not I use Kwrite and Scite. But Kwrite has few functions, it's very inconvenient. I managed to configure Scite to be more conviniet, but it, i.e. cannot open files from archives, from FTP. And still, there are too many limitations. Even tabs with open files cannot be reordered. Please, don't advise vi or vim (-: Thanks! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

16 36

[opensuse] Amarok interface
by Jay C Vollmer 08 May '10

08 May '10

Hello all. I've recently installed openSUSE 11.2 and have a question about the interface of Amarok. Previously I had been using KDE3.5 on openSUSE 11.0 and I think it was Amarok 1.9. In my previous experience with Amarok, when I would use it to load podcasts onto my iPod, I could simply right-click on the podcast and indicate that the file should be placed in the Media Device Queue. Once the queue is full, I would hit the Transfer button and everything in the queue would be moved into the iPod. Now just as I'm getting used to KDE4.3.5, I discover that I can't figure out how to load podcasts into my iPod using the new Amarok (version 2.1.1.) I had no trouble figuring out how to download my favorite podcasts, but I can't figure out how to get them from there into my iPod. I don't see any sign of a Transfer Queue. I've looked on the KDE website and the Amarok website, but haven't found anything helpful. I have to assume that I must be colossally stupid. Is there someone out there who can help me out by telling me how to do this? aTdHvAaNnKcSe -- JAY VOLLMER Il n'y a aucune honte en étant un paria. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] chkconfig pure-ftpd error
by Marco Calistri 08 May '10

08 May '10

Listmates, Attempting to start pure-ftpd on 11.2 x86_64 fails: linux-turion64:/home/marco # chkconfig pure-ftpd 35 insserv: warning: script 'K01nxserver' missing LSB tags and overrides insserv: warning: script 'K01nxsensor' missing LSB tags and overrides insserv: Script jexec is broken: incomplete LSB comment. insserv: missing `Required-Stop:' entry: please add even if empty. insserv: Script jexec is broken: incomplete LSB comment. insserv: missing `Required-Stop:' entry: please add even if empty. insserv: Script jexec is broken: incomplete LSB comment. insserv: missing `Required-Stop:' entry: please add even if empty. insserv: Script jexec is broken: incomplete LSB comment. insserv: missing `Required-Stop:' entry: please add even if empty. insserv: Script jexec is broken: incomplete LSB comment. insserv: missing `Required-Stop:' entry: please add even if empty. insserv: Script jexec is broken: incomplete LSB comment. insserv: missing `Required-Stop:' entry: please add even if empty. insserv: Script jexec is broken: incomplete LSB comment. insserv: missing `Required-Stop:' entry: please add even if empty. insserv: Script jexec is broken: incomplete LSB comment. insserv: missing `Required-Stop:' entry: please add even if empty. insserv: Script jexec is broken: incomplete LSB comment. insserv: missing `Required-Stop:' entry: please add even if empty. insserv: warning: script 'nxsensor' missing LSB tags and overrides insserv: warning: script 'nxserver' missing LSB tags and overrides insserv: Script jexec is broken: incomplete LSB comment. insserv: missing `Required-Stop:' entry: please add even if empty. insserv: There is a loop between service stoppreload and boot.localfs if started insserv: loop involving service boot.localfs at depth 2 insserv: loop involving service boot.clock at depth 1 insserv: There is a loop between service nxserver and boot.crypto if started insserv: loop involving service boot.crypto at depth 1 insserv: loop involving service boot.lvm at depth 2 insserv: loop involving service boot.dmraid at depth 3 insserv: loop involving service boot.swap at depth 5 insserv: There is a loop between service stoppreload and boot.localfs if started insserv: There is a loop between service stoppreload and boot.rootfsck if started insserv: loop involving service boot.rootfsck at depth 1 insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxserver depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Starting nxsensor depends on stoppreload and therefore on system facility `$all' which can not be true! insserv: Max recursions depth 99 reached insserv: loop involving service xdm at depth 2 insserv: loop involving service boot.startpreload at depth 1 insserv: There is a loop at service nxserver if started insserv: There is a loop between service nxserver and boot.loadmodules if started insserv: loop involving service boot.loadmodules at depth 2 insserv: loop involving service boot.udev at depth 1 insserv: loop involving service boot.sysctl at depth 5 insserv: There is a loop between service stoppreload and boot.cleanup if started insserv: loop involving service boot.cleanup at depth 5 insserv: loop involving service boot.device-mapper at depth 1 insserv: exiting without changing boot order! /sbin/insserv failed, exit code 1 Any suggestions? Cheers, -- Marco Calistri <amdturion> Universal history, the history of what man has accomplished in this world, is at bottom the History of the Great Men who have worked here. -- Thomas Carlyle -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 3

Re: [opensuse] Notepad++ replacement needed
by David C. Rankin 07 May '10

07 May '10

On 05/07/2010 05:44 AM, arygroup(a)gmail.com wrote: > On 07/05/10 11:39, David C. Rankin wrote: > >> >> If you use kde, then use kate (just learn it) >> >> If you use gnome, then use gedit (just learn it) >> >> Kate has all the bells and whistles you could ever want and it will blow >> notepad++ away. As a matter of fact, I even corresponded with the npp developer >> and talked about the features from kate I would like to see in npp. It's that >> good. enjoy :p >> > > Thanks. But I tried to find out how to move line up and down in Kate > (like it's possible in notepad++, not via ctrl+x - ctrl+v). In notepad > it's ctrl+up/ctrl+down. > I didn't find. Can you tell me where it is? Maybe a plugin need to be > installed, but I didn't manage to find it. > Hmm, I don't understand? Are you talking about a 'vertical' selection where you just select the first 15 or so characters of each row? If that is what you are talking about, you may have me there. When I think of 'line up', I think of 'indentation' and kate rocks as far as indentation goes. The only thing I had difficulty doing in kate was learning the search/replace tricks to be able to replace newline characters, etc. Other than that, I have had kate do just about everything you could think of making a text editor do. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] Re: Changing zypper command
by Joachim Schrod 07 May '10

07 May '10

Carlos E. R. wrote: > On 2010-05-07 15:25, Joachim Schrod wrote: > >> My question really was above the technical level: What consequences >> has it for an admin if he chooses to use zypper patch instead of >> zypper update? I now see several of them: >> >> -- Only openSUSE updates are installed, not from OBS (or other) >> repos. (Which may be a good or a bad thing, as David's whining >> about his unwanted MariaDB update shows... ;-)) > > Well, this is because the OBS maintainers "neglect" to create update patches. They could do. Yes, I understand. Again, I didn't ask about technical possibilities. I asked about differences that are caused by *policies*, i.e., de-facto results of processes using these technology. >> -- zypper patch might update packages from openSUSE that zypper up >> doesn't touch owing to solver problems, maybe requiring user >> action to resolve problems. > > And the other way round, too. > > zypper patch in my system right now does nothing, whereas zypper up wants to update about 40 MB, > like openoffice and xine. Now, the problem for me is where are those packages coming from... is the > xine coming from packman (good) or from somewhere else (bad)? I can't see that info in the printed > output. Maybe it needs a different command line. zypper list-updates does list repos, that's why I would never issue a zypper up without having seen the according list-updates first. Actually, I have a nightly cron job that does both zypper refresh (I have autorefresh set to false) and zypper list-updates. It proceeds to download the available to-be-installed packages. An email is sent only if output is not identical to the one that appears without any updates available, i.e., only if some error occurs or if updates are available. That establishes a notification of available updates, from which repositories, and uses our Internet bandwidth during the night when nobody else wants to use it. > It is easier for me to fire up YOU, go to selected repos, and tell it to install newer versions if > available. It is probably the same as "zypper up", but I can see each one and choose another version > or another package, one by one. That would be too much manual work for my situation. I have to update roughly 8 workstations and 2 servers. Not really that much, but it's not practicable to do that manually on each system. Maybe some words on my process are of interest: I share zypper configuration and packages cache via NFS to all SUSE systems. (That list-updates-and-download cron job is run only on one system, of course.) I wrote a script that does the announced update without questions on all systems; I can trigger that command via menu or keystroke directly from my mail client when I receive the email mentioned above -- which includes repository information. I won't do that if some critical package like kernel or X server is updated that has to be checked first; e.g., if VMware is still working afterwards. Those packages typically get locked, until I or somebody of my staff has time to do the check. There is also an automatic check that compares rpm packages and their versions over all systems and notifies us if some system differ from a reference system. (A list of all installed rpms is made as part of our nightly backups for each system, so that's very easy to do.) Yet another check determines that there exist neither .rpmnew nor .rpmsave files on any system. All in all a process where very few manual work is involved, but not too much automatism happens that could destroy our working systems. One gets an email at available updates (and only then) and one klicks the "do install" button if they're OK. Finished, maybe 5-10 secs for each update. Well, almost, maybe once per 4-6 weeks one has to lock a package and check its functionality or that it doesn't destroy other things before updating it. (Btw, on Debian that works even better, because apt has a hold feature that zypper is missing.) If something goes wrong, Nagios reminds me later due to failed checks. No manual checks either. My process is build around my opinion that humans are good for pattern matching ("is this list of updates one that we can probably install without problems?") and bad at issuing repetitive commands (calling "zypper up on all systems" or "list-updates once per day"). >> Very interesting. It seems I should add a "check needed patches" >> action to my zypper-up-based update process, to check if the 2nd case >> happens. > > You can do both actions. First run "patch", which will update most of your base system. Hmm, probably not. zypper list-patches currently list updates for packages that I have installed from other repositories, where I definitively *don't* want that update. I'll have to try that in a VM and see what happens if I do the patch. Anyhow, thanks for the interesting discussion. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] Re: Changing zypper command
by Joachim Schrod 07 May '10

07 May '10

Carlos E. R. wrote: > > "up" is safe, normally. > > An alternative is "zypper patch", which is similar to what "you" does: > > patch [options] > Install all available needed patches. > > If there are patches that affect the package management itself, those will > be installed first and you will be asked to run the patch command again. > > This command is similar to 'zypper update -t patch'. > > It is even safer. What means "even safer"? I have always wondered what difference are between patches and "normal" software updates. It's probably not the bandwidth, as long as delta rpms are used, so I suspect it's more a kind of policy thing. Btw, I understand the *technical* difference between a patch and a full/delta rpm, no need to explain me that. What I don't know is the policy difference between those two update methods: Do they carry the same amount of updates? Anybody can shed some light on this? Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

5 6

[opensuse] Latest OpenOffice missing text in bottom status bar
by Roger Oberholtzer 07 May '10

07 May '10

When editing document, the status bar at the bottom has places for text to be located, but the various places are empty. A few of them will get text when I click on them, but most stay empty. Of course, when I click on them, they also change value. It is build 3.2.0.7 Anyone else see this? -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

7 11