January 2013 - openSUSE Factory - openSUSE Mailing Lists

Re: [opensuse-factory] No os on disk after fresh install of 12.3B1 trough USB
by Jogchum Reitsma 28 Jan '13

28 Jan '13

Op 27-01-13 21:19, Andrey Borzenkov schreef: > В Sun, 27 Jan 2013 20:24:26 +0100 > Jogchum Reitsma <j.reitsma(a)hccnet.nl> пишет: > > According to this output you indeed do not have any partition boot > block. It may be a bug or it may be misconfiguration (i.e. you > selected wrong device/partition during installation). I suggest you > open bug report. Attach installation logs from /var/log/YaST2 and > RESULTS.txt from bootinfoscript. Quoting this above information in bug > report text makes it more obvious. Entered bug #800889 regards, Jogchum -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] cleanup for 12.3: not packaging files / directories in /var/run, /var/lock (and /run)
by Frederic Crozat 28 Jan '13

28 Jan '13

Hi all, as some of you might have noticed with recent systemd, you can see a warning at startup stating : var-lock.mount: Directory /var/lock to mount over is not empty, mounting anyway. (To see the over-mounted files, please manually mount the underlying file system to a secondary location.) var-run.mount: Directory /var/run to mount over is not empty, mounting anyway. (To see the over-mounted files, please manually mount the underlying file system to a secondary location.) This warning is caused by some packages installing either files or directories in /var/run (or /var/lock) which are later bind-mount to /run (/run/lock) which is a tmpfs, hiding files beneath. Robert Milasan has fixed some packages like dbus, avahi and unscd (moving them also from /var/run to /run) but feel free to help, making sure packages never create files nor directories in /var/run (and at the same time, migrate them to use /run instead) nor /var/lock. If a directory or a file needs to be created with specific permissions, package a tmpfiles.d file instead (see manpage). And if you want a file / directory to be "owned" by a package but at the same time, it will be stored on a tmpfs mount point (/var/run , /var/lock, /run), use %ghost so rpm will not write the file on disk. Thanks for your help. -- Frederic Crozat <fcrozat(a)suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Purpose of aaa_base x sysvinit-init conflict?
by Michal Kubeček 28 Jan '13

28 Jan '13

Hello, yesterday I installed 12.3 Beta 1 and I was quite surprised that when I attempted to install sysvinit-init, zypper told me it would have to uninstall almost everything. Quick investigation led me to line Conflicts: sysvinit-init in aaa_base.spec. I tried to think of the reason for this but I couldn't find any except, of course, liberally making using System V init impossible - but I hope OpenSuSE is not _that_ far down the slope. Can someone explain me the purpose of this artificial conflict? Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 11

[opensuse-factory] [Tumbleweed] Calibre 0.9.13 failed to install
by Trent Hawkins 28 Jan '13

28 Jan '13

See bash output below. "error: unpacking of archive failed on file /usr/share/calibre/fonts/liberation: cpio: rename failed - Is a directory" I noticed that this path points to an empty directory - should it be empty? There are symlinks to other font files: trent-vostro-3350:/usr/share/calibre/fonts # dir total 12 -rw-r--r-- 1 root root 3216 Jan 4 16:02 calibreSymbols.otf drwxr-xr-x 2 root root 4096 Dec 26 01:12 liberation lrwxrwxrwx 1 root root 20 Jan 28 12:41 liberation;5105d752 -> ../../fonts/truetype lrwxrwxrwx 1 root root 20 Jan 28 12:49 liberation;5105d927 -> ../../fonts/truetype lrwxrwxrwx 1 root root 20 Jan 28 12:49 liberation;5105d92a -> ../../fonts/truetype lrwxrwxrwx 1 root root 20 Jan 28 12:49 liberation;5105d92d -> ../../fonts/truetype lrwxrwxrwx 1 root root 20 Jan 28 12:54 liberation;5105da45 -> ../../fonts/truetype lrwxrwxrwx 1 root root 20 Jan 28 13:05 liberation;5105dcf4 -> ../../fonts/truetype lrwxrwxrwx 1 root root 20 Jan 28 13:05 liberation;5105dcf6 -> ../../fonts/truetype lrwxrwxrwx 1 root root 20 Jan 28 13:05 liberation;5105dcf7 -> ../../fonts/truetype lrwxrwxrwx 1 root root 20 Jan 28 13:24 liberation;5105e16b -> ../../fonts/truetype lrwxrwxrwx 1 root root 20 Jan 28 14:59 liberation;5105f77d -> ../../fonts/truetype drwxr-xr-x 2 root root 4096 Dec 26 01:12 prs500 Anyone else experienced this problem? Cheers, Trent <code> trent-vostro-3350:/home/trent # zypper dup Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Loading repository data... Reading installed packages... Computing distribution upgrade... The following package is going to be upgraded: calibre The following package is going to change vendor: calibre obs://build.opensuse.org/openSUSE:Tumbleweed -> obs://build.opensuse.org/KDE 1 package to upgrade, 1 to change vendor. Overall download size: 15.7 MiB. After the operation, additional 116.6 KiB will be used. Continue? [y/n/?] (y): y Retrieving package calibre-0.9.13-102.2.x86_64 (1/1), 15.7 MiB ( 35.8 MiB unpacked) Retrieving: calibre-0.9.13-102.2.x86_64.rpm ................................................................................................................................[done (402.1 KiB/s)] Installing: calibre-0.9.13-102.2 ............................................................................................................................................................... Installation of calibre-0.9.13-102.2 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: warning: /etc/bash_completion.d/calibre saved as /etc/bash_completion.d/calibre.rpmsave error: unpacking of archive failed on file /usr/share/calibre/fonts/liberation: cpio: rename failed - Is a directory error: calibre-0.9.13-102.2.x86_64: install failed error: calibre-0.9.11-6.1.x86_64: erase skipped </code> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] No os on disk after fresh install of 12.3B1 trough USB
by Jogchum Reitsma 28 Jan '13

28 Jan '13

Hi, After a failure upgrading my experimental disk from 12.2 to 12.3 (see https://bugzilla.novell.com/show_bug.cgi?id=799296 I downloaded the DVD-iso (openSUSE-DVD-Build0348-x86_64.iso), applied isohybrid to it and installed from the then created USB stick. Installation goes without any warning or error, but after it's finished the system won't boot up from the disk: No operating system. Something I have done wrong, or something in the install process that faulty? regards, Jogchum -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 7

[opensuse-factory] Error - Amarok
by Kyrill Detinov 27 Jan '13

27 Jan '13

Hello. Mostly info for KDE Team. I'm running openSUSE 12.3 Beta 1 (x86_64). Installed from net.iso and then constantly updated from openSUSE:Factory:Oss repository. Xfce 4.10. I have a reason to install Amarok. # zypper in amarok The following NEW packages are going to be installed: amarok kde4-filesystem kdebase4-runtime kdebase4-runtime-branding-openSUSE kdelibs4 kdelibs4-branding-openSUSE kdelibs4-core libakonadi4 libakonadiprotocolinternals1 libattica0_4 libdbusmenu-qt2 libdmtx0 libfftw3-3 libgpod4 libkactivities6 libkde4 libkdecore4 libkdepimlibs4 libksuseinstall1 liblastfm1 libloudmouth-1-0 libmtp9 libmygpo-qt1 libmysqlclient18 libmysqld18 libnl-config libnl3-200 libntrack-qt4-1 libntrack0 libpolkit-qt-1-1 libpoppler-qt4-4 libprison0 libqca2 libqjson0 libraptor2-0 librasqal3 libredland0 libsoprano4 libssh4 libstrigi0 libtag-extras1 nepomuk-core ntrack-libnl3_x oxygen-icon-theme shared-desktop-ontologies soprano soprano-backend-redland taglib The following recommended package was automatically selected: soprano-backend-redland Starting Amarok from the main menu; I see Amarok splash and a window: *Error - Amarok* The amarok database reported the following errors: GREPME MySQLe query failed! (2000) Can't find messagefile '/usr/share/mariadb/errmsg.sys' on init In most cases you will need to resolve these errors before Amarok will run properly. The only button in the window is "OK". Then I hit OK and Amarok started as expected (I hope). amarok-2.7.0-1.1.x86_64 -- WBR Kyrill

2 2

[opensuse-factory] autorefresh on firstboot - does it ever not fail?
by Felix Miata 27 Jan '13

27 Jan '13

I can't remember YaST ever not stopping to complain about autorefresh failure and me needing to tell it to skip during firstboot process. This happened as is usual here using fixed IP installing HTTP from download.opensuse.org's factory-snapshot minutes ago. Does it ever not happen to anyone? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] mis-formed/truncated menues, 12.3b1
by Patrick Shanahan 26 Jan '13

26 Jan '13

Noticed a visual discrepancny, the popup menu for "show hidden icons" is truncated, both height and left width. Screenshot: http://wahoo.no-ip.org/~pat/scrn-shot.jpg Popup menu that was called "kicker" is also truncated width right; height appears ok. Unlocking widgets, the pop-out menu is also either truncated or doesn't clear the area it configures, approx 1/2. While this is only visual, it is quite disconcerting. I can provide screen shots if necessary. Bug report? -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 4

[opensuse-factory] Re: system scripts using BASHism's but invoked as "#!/bin/sh"
by Guido Berhoerster 26 Jan '13

26 Jan '13

* Linda Walsh <suse(a)tlinx.org> [2013-01-26 02:30]: > According to the opensuse list: > > > -------- Original Message -------- > Subject: system scripts using BASHism's but invoked as "#!/bin/sh" > Date: Thu, 24 Jan 2013 09:52:54 +0100 > From: Bernhard Voelker <mail(a)bernhard-voelker.de> > CC: SuSE Linux <opensuse(a)opensuse.org> > References: <5100F40B.8050909(a)tlinx.org> > > Wow, not bad (on a 12.1 system): > > $ find /etc/init.d -maxdepth 1 -mindepth 1 -type f | \ > xargs checkbashisms 2>&1 | wc -l > 400 > > Have a nice day, > Berny > ------------------------- That's quite meaningless since it counts the lines of output of checkbashisms, including stuff like "could not find any possible bashism in". > > Also they use arrays and double square brackets which dash doesn't support > (I'd update the bug, but it's closed for maintenance). > Yes, there are problematic scripts in /etc/init.d. Feel free to file specific reports against the corresponding packages, or even better fix the shebang line and send a submitrequest. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Re: [opensuse] Re: system scripts using BASHism's but invoked as "#!/bin/sh"
by Linda Walsh 26 Jan '13

26 Jan '13

Per Jessen wrote: > Linda Walsh wrote: > >> Werner Flamme wrote: >>> Linda Walsh [24.01.2013 09:42]: >>>> I'm constantly seeing system scripts starting with #!/bin/sh >>>> yet I'll see "BASHism's" in the script. >>> Why don't you open a ticket (or one per script) at the bugzilla? >> --- >> Why would you suggest such a huge waste of time? > > Just _a_ bug report. ---- Far more reasonable: Bug 800607 Submitted system scripts should be scan'ed for bashims, and have 1st line update to bash if used -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 6