April 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] after dup fro 12.2 to 12.3 grub menu still 12.2
by Daniele 05 Apr '13

05 Apr '13

Hi guys, I'm not a big fun of zypper dup but I did it ! New system is up and running but grub menu still show 12.2 instead of 12.3. Under Yast, boot loader options: Distributor and Default section -> openSUSE 12.2 Is a known issue ? worth a bugreport ? Better way to fix menu entry ? I never touched grub 2 configuration files... Daniele. -- *** Linux user # 198661 ---_ ICQ 33500725 *** *** Home http://www.kailed.net *** *** Powered by openSUSE *** -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 15

[opensuse-factory] Intentional breakage of feature? or Bug? SASH no longer StandAloneSHell
by Linda Walsh 05 Apr '13

05 Apr '13

I had a problem a few weeks ago where I was having libc problems booting off a rescue disk -- used to be I could usually boot from a rescue disk, mount root on /mnt, chroot /mnt, mount the rest, and look at startup scripts 1-by-1. Now that doesn't come close to working. But even when I got the paths set right (LDLLIBPATH) etc... BASH/DASH/SH/ were still having problems loading due to suse's adding OW's patches that make linked binaries incompat with standard libc/glibc I.e. -- instead of a dynamic load of OW, and giving reduced functionality, it was hardcoded in to prevent anything from working. Ok... so I thought -- AH Standalone shell... it doesn't depend on anything. SURPRISE -- it's now dynamically linked with a custom libc as well...so it wouldn't work either! Um... FAIL!!!! SASH is called SASH because it is supposed to be Stand-Alone and need no libs to link as well as having builtin basic commands: Manpage: DESCRIPTION The sash program is a stand-alone shell which is useful for recovering from certain types of system failures. In particular, it was created in order to cope with the problem of missing shared libraries or impor- tant executables. ^^^^^^^^^^^^^^^^^^^^^^^^ Um...HELLO... breaking basic functionality? Had a bitch of a time recovering since xfsdump bumped it's version num to '3' to correct several kernel bugs. For some reason my xfsrestore's even from the disk kept saying '2'... Well it appears I couldn't run xfsrestore from any repair disk as they all had v2 of the libs (v3 appeared in mid Jan). But I couldn't link with the new versions on disk due to libc problems. Finally was able to rebuild xfs from git running on the repair disk and install xfsrestore onto the repair disk where the libc wasn't corrupted with a non-standard OW extension. But, that was an aside. Um...main beef .. NOT EVEN SASH?!?! statically linked? system recovery tools like xfsrestore likely should be too (as an afterthough/aside)... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 45

[opensuse-factory] mutliple displays bug
by Petr Danecek 05 Apr '13

05 Apr '13

Hello, I am experiencing a curious problem: My mouse pointer thinks that my screen is in some sense smaller. As a consequence the pointer cannot be used for copying text and it does not change from arrow-style pointer to the text-selection-style pointer in any application, be it gnome-terminal, evolution composer, or firefox. My primary screen is an external monitor and my laptop's screen is turned off. A workaround is to turn on both screens and turn the laptop's screen off again. After that, I can use the pointer normally until next reboot. Any help would be much appreciated. Best wishes, Petr -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] Multiple repos during installation?
by Andrey Borzenkov 05 Apr '13

05 Apr '13

Is it possible to use multiple repo (like primary and update) during installation? I do not see where I can add them in installer. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

13 30

[opensuse-factory] New Package: videolan's VLC
by Raymond Wooninck 04 Apr '13

04 Apr '13

Hi List, One of the goals for openSUSE 13.1 is to drop the old gstreamer version 0.10. At this moment this would cause quite some issues for KDE as that the phonon- backend for gstreamer only works with this older version. Attempts are currently on the way to port this phonon backend to gstreamer 1.0, but we seem to be still far away from a working version. In order to make sure that KDE is more independent from Gstreamer, I would like to start working on the preparation for the second phonon backend, which is based on VLC. I am aware that VLC comes with all kind of bad plugins to support the bad bad codecs, but it seems that we are able to build VLC with only support for the opensource codecs. This would enable us to build a similar package as with Xine, where the bare necessity was build on OBS and the full package could be downloaded from packman. For VLC this would be the same, however users would have a choice of downloading it from Packman or to install it from the videolan repo (maintained by DimStar). Based on the the legal acceptance of the ffmpeg sources in Chromium, I believe we can make this happen. VLC in Factory would also mean that we could build more packages that depends on the VLC library. I see the following steps to be done: 1) Decide on the best location for the VLC package (multimedia:libs) ? 2) Submit the VLC package to Factory for legal review. 3) Adjust the VLC package in such a way that it can be used directly on packman (building the same source, etc) 4) Check with Dominique if we could achieve the same for the videolan repository Steps 3 and 4 should enable us to have only one location where to maintain the package and have it build in two or three places. I would appreciate if people could let me know what the best place for this package would be. Thanks Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 11

[opensuse-factory] pro-tips
by Jos Poortvliet 04 Apr '13

04 Apr '13

Heya, A while ago we published an article about 'openSUSE for non-geekos' with tips for those transitioning from other distro's to Green: https://news.opensuse.org/2013/03/22/opensuse-for-new-geekos/ Again, thanks to all who contributed to it and spread it around! This was a rather popular article but some people commented to me that current users are left out a bit. So, how about doing an article with some 'pro' geeko tips? I'd need tips for that, however. Anyone having ideas can dump them in this piratepad: http://piratepad.net/opensuse-for-ubuntu-refugees Thanks, Jos

2 1

[opensuse-factory] 'su' seems to ignore "-p" (preserve environment)... in factory...
by Linda Walsh 03 Apr '13

03 Apr '13

Plays havoc with my remoteX stuff... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 44

[opensuse-factory] Conflicting packages / dbus services
by Dominique Leuenberger a.k.a. Dimstar 02 Apr '13

02 Apr '13

Hi all, Coolo (rightly) declined a package submissions of mine against openSUSE:Factory, where a conflict between two packages was identified but not marked as such in the meta data. The reasoning is clear.. now we're looking for the best solution (please, only people that have implementation recipes speak up.. we don't want to organise full workflows and change the distribution). Issue: ====== Two packages involved: * apper * gnome-packagekit Both provide the file /usr/share/dbus-1/services/org.freedesktop.PackageKit.service and implement the PackageKit dbus service (they are the respective frontends for KDE and GNOME). Now, already visible, correctly, they conflict on file level. The last thing I am planning to do is Conflicts: apper in gnome-packagekit (even though this would solve the issue at hand... but it's not the 'right' thing per se and does not scale). Proposed solution: ================== Packages have to provide their dbus service in the metadata, in the form Provides: dbusservice(org.freedesktop.PackageKit) And generally, all those provides should be also specified as Conflicts: otherproviders(dbusservice(org.freedesktop.PackageKit)) Now, obviously, this would best be done automagically (not targetting 'one' case, but actually all possible usecases. Suggestions? Ideas? Better solutions? The Provides: part is rather simple to implement using rpm find/prov hooks.. can this be done to also add Conflicts the same way? Followup issue: =============== Now, whereas this is rather simple to solve on a technical / packaging level (somebody might have better Ideas for above), this leave the problem that a machine with KDE AND GNOME installed would end up with only one provider of org.freedesktop.PackageKit (which is not different to what is now, just that it's clear on the pkg metadata). What are the expectations around this? Similar issues: =============== The same problem is also observed between Empathy and KDE Telepathy (ktp). Looking forward for your inputs! Dominique (in the name of the KDE and GNOME teams, I'd say) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 3

[opensuse-factory] 'which' missing from 'base build root'
by Dimstar / Dominique Leuenberger 02 Apr '13

02 Apr '13

Hi all, What a nice surprise I had to see this morning: some 'old' package (last touched > 12 months ago) suddenly fails to build.. Builderror? -bash: which: command not found yes, right: which was split out into a sep. package. No consideration or pre-announcement was done (or I missed it). And to make the whole story fun: BuildRequires: which => unresolvable: nothing provides which great stuff! I think everybody would appreciate if such fundamental changes, if not handled transparently, would be communicated upfront. As a wrapup: the 'submit' came in with: https://build.opensuse.org/request/show/161218 The submitter added as submit text: "Please wait for which, adjtimex, time to go in first since those packages have been split from util-linux." * Are we (packagers) now supposed to add BuildRequires: which to whatever uses it (I don't object it.. but where does it stop?) * When can we expect 'which' to actually appear in Factory, so that builds are possible again? Best regards, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 20

[opensuse-factory] Change in util-linux breaks packaging of many packages
by Johannes Weberhofer 02 Apr '13

02 Apr '13

Hello! In util-linux I see the following change in factory: ------------------------------------------------------------------- Sun Mar 17 20:39:47 UTC 2013 - jengelh(a)inai.de - Split "which", "time" and "adjtimex" off util-linux This modification breaks many packages, e.g. most PHP packages as the build process depends on "which", that is no longer in the util-linux package. Best regards, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5