September 2012 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Xf86- packages give me a problem
by Constant Brouerius van Nidek 26 Sep '12

26 Sep '12

After today zypper dup I got a new xorg.x11-driver-video with 28 new Xf86- packages. My system did come to init 5 and only showed a blinking cursor. Did not seem to find the right X11 driver. System worked after reinstalling the old xorg.x11-driver-video. which got automatically rid of all 28 new drivers. I am using factory. -- Linux User 183145 using KDE4 on a Pentium IV , powered by openSUSE 12.3 Milestone 0 (i586) Kernel: 3.5.0-1-desktop KDE Development Platform: 4.9.1 "release 561") 16:22pm up 1:15, 1 user, load average: 0.60, 0.27, 0.37 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: /run/media/$USER (Re: [opensuse-factory] usb devices not showing in kde)
by "Stefan Brüns" 26 Sep '12

26 Sep '12

Am 09/26/12, schrieb Karl Eichwalder <ke(a)suse.de>: > Someone out there who know how you can use these tools without too much > pain from the command line? Hm, depends on what you want to achieve: 1. mount all SD cards 2. mount any USB storage when it becomes available 3. mount some storage with a known name/label For the last point, you can use one of the symlinks in /dev/disk/by-*. For the other ones, I think you have to write some script which either parses the output of --monitor/--dump respectively, or directly talk to udisks(2) via dbus. Regards, Stefan -- 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] Better support for third-party JREs
by Michal Vyskocil 25 Sep '12

25 Sep '12

Hallo all, from time to time I got the complaints from the users want to use our Java packages, but not the JVM itself. As Oracle retired the permission to distribute their own JVM, most of the users want to manually install the Oracle JVM instead of openjdk we distribute. In a past, we have changed a logic of alljava.sh, so it search for jvm in /usr/java/latest and /usr/java as well, so can setup the proper JAVA_HOME for third-party JVM. The next unsolved problem are dependencies. In a bug#776951 I've got an proposal to introduce the fake package with java, but I do not like that approach. We don't need to deal with a dependencies at all, if we intentionally break them. https://bugzilla.novell.com/show_bug.cgi?id=776951 Instead of it, I propose following - change all Requires: java in openSUSE:Factory to Recommends: java. For default openSUSE setup, it won't make any difference. For people wanting to have third-party java installed, they can add lock for distributed JVMs and put their preffered JVM. There is only one problem - users can turn the recommends off, but I don't see that as a probable case for Java software, so I would go forward. Any objections, or other ways to go? Regards Michal Vyskocil

14 68

[opensuse-factory] GStreamer dependencies change in Factory
by Dimstar / Dominique Leuenberger 25 Sep '12

25 Sep '12

Hi all, as announced earlier and as a dependency to GNOME 3.6, we submitted GStreamer 1.0 to Factory, as package name gstreamer. In the past, gstreamer-0_10 provided a virtual symbol gstreamer and gstreamer-0_10-devel provided gstreamer-devel. They were conveniance provides, which had to be removed, as they would; for obvious reasons clash with the actual package called gstreamer and gstreamer-devel. So, if you get a "Nothing provides gstreamer-devel" (which is currently possible, as gstreamer 1.0 is in review mode towards Factory), that means you should switch to use gstreamer-0_10-devel (or, even better pkgconfig(gstreamer-0.10), then you don't have to worry about the actual package names). Or, as an even better solution, get your package up to GStreamer 1.0 (likely discussion with upstreams are needed). There is a rather extensive 'how to port to GStreamer 1.0' documentation available; a bunch of APIs got sanitized and unsane ones have been removed... Hope to have you informed before you wasted all your spare time you don't have on trying to figure out what is going on. Best regards, Dominique / DimStar -- 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] Why does OpenSuSE disabled the default of allowing multi-core use in Coreutils 'sort'??
by Linda Walsh 25 Sep '12

25 Sep '12

I wondered why I wasn't getting multi-cpu support in my sorts of >128k line files, even when I specified that it should use multiple threads. It seems SuSE adds a patch to set the max CPU's my machine has to 1, so no matter what I set in --parallel, it uses the smaller of (1, number I ask for). The default is to use min(available CPU's, number I ask for)... Yet the OSuSE version is hard-coded to disallow parallel usage. Could someone point me at the discussion in the archives as to why this was decided? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

13 33

Re: [opensuse-factory] Re: What is the purpose of the systemd journal service?
by Frederic Crozat 25 Sep '12

25 Sep '12

Le mardi 25 septembre 2012 à 12:46 +0200, Andreas Jaeger a écrit : > On Tuesday, September 25, 2012 12:39:59 Stephan Kulow wrote: > > On 25.09.2012 11:42, Andreas Jaeger wrote: > > > On Thursday, September 20, 2012 21:51:35 Peter Czanik wrote: > > >> Hello, > > >> > > >> Before we all end up in flames, a hopefully not too biased view > > >> from > > >> syslog-ng upstream :-) > > >> > > >> First of all, systemd journal is a perfect solution for about 90%+ > > >> of > > >> openSUSE users, which have stand alone workstations and don't care > > >> at > > >> all about logging. They don't need rsyslog or syslog-ng. The > > >> journal > > >> collects logs under /var/log/journal into some binary files. By > > >> default it does not take more than 5% of available disk space, so > > >> logs can't fill up the partition accidentally. It's very limited, > > >> but > > >> user friendly. Actually I don't really understand, why syslog is > > >> still installed on openSUSE (ArchLinux removed syslog from systemd > > >> based installations to avoid dual logging...), but this is a > > >> different questions... > > > > > > Thanks Peter for the info. So, let's remove syslog/rsyslog from the > > > default install now. > > > > > > Coolo, could you do the change - if you agree with it, please? > > > > So this kind of puts the last nail in the sysvinit coffin? > > Ah, you're right - let's do it one by one and not start from the end. > > Frederic, what steps do you propose - here's my suggestion: > 1. update to systemd 185 I'm working on it, which will merge udev package (but I've kept udev as a separate package for now) and move udev and systemd to /usr. > 2. Change grub to not offer switch for init packages not sure it is worth, since grub2 "graphical" boot doesn't have the feature. So, switching to grub2 by default will remove the feature. > 3. Change sysvinit-init package (or however it's called) We just need to no longer generate this subpackage (from sysvinit source package, which is still needed for some tools). > 4. Remove syslog from default install. Sounds good. -- 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] Releasing Milestone 0
by Stephan Kulow 25 Sep '12

25 Sep '12

Hi, I would like to start the 12.3 game for real. We have a new KDE a new Xorg stack - at least. I would like to add kernel 3.6 into the mix and then release Milestone 0 "last change to use sysvinit" :) After that we can go into OSC12 and discuss how to continue. Greetings, Stephan -- 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] Access denied to bugzilla and running Factory day to day
by Catalin Iacob 24 Sep '12

24 Sep '12

Hello everybody, First a bit on my background: I've been running openSUSE for a year, and switched almost exclusively (have a 12.2 chroot that I only had to use once) to Factory on my home system for about 2 months now (too brave? until now it worked great). The plan was to run the lastest software, help by reporting bugs, learn more about packaging and OBS and maybe try to help with some SRs. So far this has worked great, I did all of the above except reporting bugs (I'm only affected by one that I'll report soon). I do zypper dup every day, sometimes it complains about problems. If that happens I cancel the update and try again the next day, usually in at most a few days it gets into an upgradable state again. However, it's been a while since I get: Problem: marble-4.8.5-1.7.x86_64 requires marble-data = 4.8.5, but this requirement cannot be provided Looking at this, it seems plasma-addons stayed at 4.8.5 and it requires marble-4.8.5 which is gone. Why did plasma-addons stay at 4.8.5? Because SR [1] was declined by somebody in the legal team. The decline reason points to [2] where I get: You are not authorized to access bug #779736. That's not very nice, I'm now completely in the dark as to why plasma-addons wasn't upgraded and how long will it keep blocking the rest of my upgrade. I understand that the legal issues might be sensitive but I have a feeling this time they're not and I think it's bad to split the community into SUSE employees that can see everything and "the rest". Exactly at this point I want to postpone the upgrade anyway until the Xorg and Mesa issues Coolo pointed out get fixed (thanks for that by the way! very important for people testing day to day to avoid major breakage if it's already known) but the principle remains: everybody should be able to see why a SR got rejected to know what can be done about it to move forward. To summarize: * having some bugs available just to SUSE employees is in my opinion bad * what should happen to plasma-addons so that it gets upgraded to 4.9.1? * am I doing things correctly to stay on top of Factory? are others doing the same? is Factory meant to be used day to day if you have some troubleshooting and system recovery skills? * thanks for a great distribution, and a very stable development version of it, keep up the good work! [1] https://build.opensuse.org/request/show/133585 [2] https://bugzilla.novell.com/show_bug.cgi?id=779736 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 4

[opensuse-factory] New develprj: X11:RemoteDesktop:x2go
by Jan Engelhardt 24 Sep '12

24 Sep '12

As per http://en.opensuse.org/openSUSE:How_to_contribute_to_Factory#How_to_add_a_n… , I am to propose here a new develprj. Dear Build Service maintainers, please tell me what to do next :) X11:RemoteDesktop:x2go already existed when I started my involvements in 2012-Feb. Is X:R:x2go acceptable as new develprj or should the packages be migrated to some other DP? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 3

[opensuse-factory] Moving forward with systemd
by Cristian Rodríguez 24 Sep '12

24 Sep '12

Hi: Above, there is a list of tasks, which are "up for the grabs" after we completely remove the old sysvinit system from the distribution. * We have to remove ConsoleKit, ASAP. its functionality has been replaced by systemd logind, apparently is enough to build polkit with systemd support to achieve this goal. * build the kernel with CONFIG_AUDIT_LOGINUID_IMMUTABLE=yes (From these point on sysvinit waves his old arse goodbye) * See if acpid can be replaced by logind features HandlePowerKey,HandleSleepKey,HandleLidSwitch etc.. * we must ensure that packages have proper tmpfiles.d(5) configuration files and remove/obsolete all the CLEAR_TMP_DIRS_AT_* sysconfig kludges in /etc/sysconfig/cron and boot.cleanup script. Related to this : daemons must run with PrivateTemp set to true and see a way to provide exclusive temporary directories to users in a sensible manner such as pam_mktemp (?) or similar. * Yast or $whatever is doing the job, must learn how to setup remote filesystems mount points according to what systemd.automount(5) and systemd.mount(5) describe. * migrate away from pm-utils scripts to /usr/lib/systemd/system-sleep/ ..systemctl suspend.. systemctl hibernate..etc.. Im very likely missing something else, but this is enough to start :-) Cheers. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

14 24