November 2011 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] libgadu and kdenetwork
by todd rme 05 Dec '11

05 Dec '11

I have been trying to get kdenetwork to detect libgadu for gadu protocol support without success. libgadu is available, and it is in the buildrequires. Here is the cmake message: -- checking for module 'libgadu' -- found libgadu, version 1.11.0 -- Found LIBGADU: /usr/lib64/libgadu.so grep: /usr/local/include/libgadu.h: No such file or directory -- libgadu must be compiled with pthreads support Note that libgadu IS being built with pthreads support enabled. Also note that cmake appears to be searching /usr/local/include/. Include files are not installed there, they are installed in /usr/include/, and kdenetwork is told to search in /usr/include, it searches in /usr/include for every other package it needs, and libgadu.pc says to look in /usr/include. I looked at the cmakelists.txt files and couldn't find anything obviously wrong. Does anyone have any ideas what might be going on here? -Todd -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 6

Re: [opensuse-factory] Re: Apper disaster - Can´t get my beloved 11.4 KpackageKit back
by jdd 03 Dec '11

03 Dec '11

Le 19/11/2011 00:24, Greg Freemyer a écrit : > what I see (via zypper patch). I see that zypper up do *not* update flash, but zypper patch give the option to do (changing repo) is zypper patch a prefered way to make an update, I didn't use it before thanks jdd -- 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] Tumbleweed 12.1 Postfix and network don't start at boot
by Vahis 30 Nov '11

30 Nov '11

I'm not sure if 12.1 is on topic here anymore, but Tumbleweed should be :) This issue of course occurs in both: First there's no system mail. Then I see via YaST runlevels that Postfix is not running. I start it and he wants to start also network. (Which obviously was not running either but I had no idea. There's nothing wrong there, in networking) Now system mail works, fine. But the settings disappear after reboot, no mail again. No difference whether I boot with systemd or sysvinit. I wonder what is causing this. Vahis -- http://waxborg.servepics.com openSUSE 11.4 (x86_64) 2.6.37.6-0.9-default main host openSUSE 12.1 (x86_64) 3.1.0-1.2-desktop Tumbleweed in VirtualBox openSUSE 12.1 (i586) 3.1.0-1.2-desktop in EeePC 900 -- 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] obsolete init scripts: cpufreq
by Cristian Rodríguez 30 Nov '11

30 Nov '11

Hi: I have been looking at all sorts of init scripts, the first that caught my attention is /etc/init.d/cpufreq it essentially only load kernel modules that as far as I undestand is a work for udev, is there a reason why it is still done this way or I should fill a bug report ? -- 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] Python 2 and 3 packaging without conflicts
by todd rme 30 Nov '11

30 Nov '11

For many python packages, packages are installed in directories that are named after the python version. This works well with installing python 2 and python 3 versions of packages in parallel. Some packages, however, install files in common directories, such as %{_bindir}. In these cases the python 2 and python 3 version of the packages may conflict, potentially causing errors. Obviously changing all the python 2 version of packages would be prohibitive. The solution would be to change something in the python 3 packages. It would be possible to create new directories for the python 3 versions, like %{_bindr}/python%{py3_ver} (/usr/bin/python3.2, for example). These would needed to be added to PATH, but that shouldn't be a problem. However, creating a new directory in /usr/bin should probably not be done trivially. I was wondering if this was a good idea, or if anyone has any other ideas. I cannot find a way to selectively rename the script files, although if there was that might be better. -Todd -- 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] changing distro freeze limit
by jdd 29 Nov '11

29 Nov '11

Hello, Please, redirect me to feature, bugzilla or an other list if necessary. * I notice an unexpected number of severe bugs on 12.1 (at least on my HW) * I notice most of these bugs come late in the process. Several things worked in beta (or where not possible to test) and do not work in GM * I do not blame anybody. I know the extraordinary effort done. But we can't find testers from the wild. Also we now have tumbleweed for people liking the next extra step right now. So I think we should take feature/distro freeze (I'm not sure of what is what) a month earlier, to get a month more to test and debug. In the same time we have to give somemore attention to packman, because many very important packages are held there and many do not work at all (just tested pitivi, openshot, avidemux and I couldn't even install kdenlive) Of course, if somebody have a better idea to have the same result, I take it! Just to give an idea, I planned to work for the marketting team after OSC and was stuck in debugging weird bugs since (sure, my knowledge and time are very limited, so this effort may not have changed most of the things :-() thanks jdd -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

16 41

[opensuse-factory] systemd: What open questions do you have?
by Andreas Jaeger 29 Nov '11

29 Nov '11

I've seen a couple of bugs and quite some confusion about systemd. systemd comes with great man pages, there are upstream blog post and we have our own wiki. But still there are open questions. So, let's try to collect the open questions - like Wolfgang's - and then answer them in a second step. I'll go through the questions and will try to answer some and I hope others (Frederic, please!) help as well. Here's the wiki page and as a start I added the questions by Wolfgang. http://en.opensuse.org/openSUSE:Systemd_status#Open_Questions_that_should_b… Please update the page, Andreas -- Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5

[opensuse-factory] packagekit still in 12.1?
by Greg Freemyer 29 Nov '11

29 Nov '11

All, I thought packagekit was removed from 12.1? I have run zypper dup twice in the last 2 days. Both times it claimed packagekit had locks in place and I needed to wait. With 11.4 I certainly had similar things happen on rare occasion, but 2 out of 2 seems excessive. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

20 32

Re: [opensuse-factory] Hello, regarding gcc plugin support
by Bombshellz Administrator 29 Nov '11

29 Nov '11

On 11/29/2011 8:18 AM, Michael Matz wrote: > Hi, > > On Tue, 29 Nov 2011, Bombshellz Administrator wrote: > >>>>>> I would like to make a correction, it's not implicitly dependent >>>>>> on GCC plugin headers being available but without it, the >>>>>> drawback is a less secure kernel >>>>> So, which plugin do you use to increase security of your kernel? >>>> I personally didn't write the patch but here is the snippet of the >>>> actual code in the Makefile that introduces the GCC plugins in the >>>> build: >>> Thank you. So it's the PaX kernel patch that meanwhile also >>> distributes GCC plugins. Okay, I'm considering a new sub package >>> containing the headers. >> I'm sending this E-Mail to inquire about the latest updates about the propose >> packages? Is there a time table so I can schedule my service for a Kernel >> Update? > Nope. openSUSE work has low priority. If you want something earlier I > happily accept package submissions against devel:gcc. > > > Ciao, > Michael. Hello, It's very unfortunate... My only grievance is that whilst other distributions like Debain have GCC plugin headers available, yet openSuSE does not because openSuSE is reluctant because the possibility of additional bug reports. Although I empathize with openSuSE developers, it would be very unfortunate and disheartening to drop openSuSE as a production server altogether because of missing package. The real issue here is that there maybe some unforeseen issues in the future in reference to additional packages that maybe required that are already available in other distributions that could be missing as well. To make matters worst, while I'm focusing on resolving technical issues such as this, I'm spending less time on my organization and growth. If I or a staff member on my team (which is 3, me included) had the time and the know how. We could have help contribute. :( -- Best Regards, The Admin Team Intended for the recipent eyes only -- 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] package systemd migration
by Wolfgang Rosenauer 29 Nov '11

29 Nov '11

Hi, I might have missed important systemd information during the 12.1 development phase but haven't had to deal with it for my packages up to now. A recent package update now introduced systemd services and I found it's not obvious to me what to do. It already starts with trivial questions where I have an my own understanding but not absolutely sure. The package provides an init script currently and now added systemd service files. So the following questions came to my mind: Do I still package the sysvinit files? I guess that's a yes because we still offer the sysvinit boot process. The package has a sysconfig file which only takes a variable to modify the daemon options. Can I use that for systemd as well? How to do that? The daemon is currently started by default when installed. What happens after the update to the new version which includes systemd files? Will it be enabled by default? (I've actually tried the update and the service was running afterwards so I guess it will be enabled in update case but not for a fresh installation?) For the service it makes a lot of sense to use systemd's socket activation feature. So what do I need to do exactly to have the service disabled but have the socket enabled to start the service automatically (in terms of system configuration)? Is the only way to have services/sockets enabled by default to modify some certain systemd package and not from within a package installation? This sounds strange and rather unfortunate so it's for example not possible to install/update a package which then starts a service by default w/o updating an official central distribution package? I've tried to find answers to those questions in the wiki but had no luck. Any hints? Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 10