February 2014 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Broken horde4 packages in server:php:applications
by Johannes Weberhofer 07 Feb '14

07 Feb '14

Dear horde maintainers, there is a list of projects named horde4* and php5-pear-Horde_DataTree which all are linked to openSUSE_Factory; all thise links are no longer valid, therefore I suggest to remove all those packages. Best regards, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] Some python help please
by Robert Schweikert 06 Feb '14

06 Feb '14

Trying to create a package from source that has no setup.py. THus to keep things simple I figured I'd create one myself ;) . But that's not working out the way I figured it would, thus I could use a hint or two. The source tree has packages in the lib directory, i.e. lib/a lib/b lib/c exist. The problem now is that some of these are dependencies that are already packaged. For simplicty lets say I am only interested in installing b. Thus in my setup.py file I have setuptools.setup( ..... .... packages=setuptools.find_packages('lib', exclude=['a','c']), package_dir={'': 'lib'} ) Based on the info that I found the "exclude" argument should tell find_packages to not consider those packages and this works. When running in an active session and printing the results of find_packages I get only stuff in "b". However when I run setup.py I still get "a" and "c" installed in the target directory :( I've played around with various settings for "package_dir" but couldn't figure out a way to make setup happy and only get the "b" package installed into the target directory. How do I do that? Help is appreciated, Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead Public Cloud Architect rjschwei(a)suse.com rschweik(a)ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 5

[opensuse-packaging] Adding a new package which depends on others
by Guillaume Gardet 05 Feb '14

05 Feb '14

Hi, I would like to add a new package (pocl) which depends on non-standard packages : * hwloc-devel which is in Factory and developped at devel:libraries:c_c++ * ocl-icd-devel which is in Education * opencl-headers which is in Education * uthash which is in devel:libraries:c_c++ I think devel:libraries:c_c++ or devel:tools projects may be fine for pocl package. Is there anything better? What would be the best way to integrate all of thoses deps? Not sure about the right RPM Group: 'Productivity/Other' or 'System/Libraries'? Guillaume -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 3

[opensuse-packaging] Weird behaviour in libreoffice-openclipart in LibreOffice:Factory
by Tomáš Chvátal 04 Feb '14

04 Feb '14

Hello guys, I have some kind of weird activity in there. The build itself uses /usr/lib/libreoffice/program/gengal.bin which fails to properly resolve its symbols there. abuild@bugaboo:/home/abuild> ldd /usr/lib64/libreoffice/program/gengal.bin linux-vdso.so.1 (0x00007fff3c7f4000) libmergedlo.so => not found libuno_sal.so.3 => not found libcomphelper.so => not found libuno_cppu.so.3 => not found libuno_cppuhelpergcc3.so.3 => not found libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f636c4fd000) libm.so.6 => /lib64/libm.so.6 (0x00007f636c1fb000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f636bfe4000) libc.so.6 => /lib64/libc.so.6 (0x00007f636bc38000) /lib64/ld-linux-x86-64.so.2 (0x00007f636c805000) On the other hand when I install libreoffice in to my machine itself the gengal is working just fine. Any idea what is going on there? Some missing ldconfig? Tom

2 1

[opensuse-packaging] apache2-mod_authnz_external depending on Apache version
by vetter＠physik.uni-wuerzburg.de 04 Feb '14

04 Feb '14

Hi, this is probably answered before, but I didn't find anything in the archives and Packaging Guidelines. apache2-mod_authnz_external comes upstream in different versions for different apache versions: 3.3.x is for Apache 2.3/2.4 3.2.x is for Apache 2.2 Currently in https://build.opensuse.org/project/show/Apache:Modules we have version 3.2.6, working and compiling only for apache 2.2. So it does not build for newer distros, i.e. openSUSE 13.1 and newer. I branched and updated my branch to 3.3.2. It builds for the openSUSE 13.1 and newer and for most Apache_* targets. What is the best way to bring 3.2.6 for older distros and 3.3.2 for newer distros to the Repositories? I thought about including version number in the package name. That would probably mean to also change name of the existing package? Is there is a way to build different versions depending on either distribution/repository or even better depending on apache version? TIA. -- Mit freundlichen Gruessen, Andreas Vetter -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 3

[opensuse-packaging] Python Packaging / PEP 426 / Request for involvement
by Tim Serong 04 Feb '14

04 Feb '14

Hi All, One of the talks I saw at linux.conf.au 2014 was Python Packaging 2.0: Playing Well With Others: https://www.youtube.com/watch?v=7An2GobbSWU Nick (the speaker) wanted me to make sure that we in openSUSE were aware of Python package metadata efforts, and is seeking feedback from distro people to make sure Python is doing things we can work with on a packaging front. I'm not especially deep into Python myself, so I'm putting this out here on opensuse-packaging and opensuse-factory in case someone more suitable is around ;) Relevant PEPs are: Metadata for Python Software Packages 2.0 http://www.python.org/dev/peps/pep-0426/ Version Identification and Dependency Specification http://www.python.org/dev/peps/pep-0440/ Standard Metadata Extensions for Python Software Packages http://www.python.org/dev/peps/pep-0459/ Regards, Tim -- Tim Serong Senior Clustering Engineer SUSE tserong(a)suse.com -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] debuginfo
by Wolfgang Rosenauer 03 Feb '14

03 Feb '14

Hi, some years ago I understood some of the stuff but apparently forgot almost everything again. I'm hunting an issue that the Firefox debugsymbols (the google-breakpad ones) which are created in the build step do not match the binaries ending up in the package. This means that crashreports sent to Mozilla cannot be decoded and are useless. Nothing changed in the packages and the way all that is handled and it worked in the past (I cannot exactly tell when it stopped working). For verifying which step of the build could be culprit I've disabled the debuginfo flag in OBS and rebuilt the package. Afterwards the breakpad symbols did match again. I've also verified that stripping the binaries via command strip does not change the ID and therefore stripping itself is not hurting the procedure. Therefore I'm pretty sure something in RPMs find-debuginfo.sh is doing something which changes the breakpad ID. I cannot tell what it is but it wasn't an issue in the past. So the following question: - what does find-debuginfo.sh do which changes the breakpad ID And as a sidequestion out of curiousity: - what is expected when the debuginfo flag is removed from OBS? Do binaries still contain debugsymbols? (apparently no) Do shared libs still contain debugsymbols? (apparently yes) Is that expected? I need to find a solution since the breakpad symbols are actually more useful for me since users don't have to do anything special (using gdb) to report crashes. But the "distro" way is to have the debuginfo packages usable with gdb. If both cannot be achieved at the same time, I'm not sure what to do. Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 3

[opensuse-packaging] W: incoherent-version-dependency-on
by Dmitriy Perlow 02 Feb '14

02 Feb '14

Hello. Any ideas please? Spec file and build log are attached. -- Best regards, Dmitriy DA(P).DarkneSS Perlow @ Linux x64

1 0

[opensuse-packaging] is /usr/lib/games a standard directory or not ?
by Benoît Monin 01 Feb '14

01 Feb '14

Hi, While packaging pcsx-reloaded, I got the following rpmlint warning: standard-dir-owned-by-package /usr/lib/games It only happens for openSUSE 13.1 or above and only for i586. So I tried to only include the subdirectory /usr/lib/games/psemu, which gave me the error: directories not owned by a package /usr/lib/games /usr/lib/games is not listed in the filesystem package, I think the rpmlint warning is a false positive. Is /usr/lib/games really a standard directory ? If so, why /usr/lib/games only and not /usr/lib64/games too ? -- Benoît -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 3

[opensuse-packaging] License question
by Filipe 01 Feb '14

01 Feb '14

Hi all, I would like to package SPHEREPACK for opensuse, but I'm not sure if this license is OK. Can anyone help me? http://www2.cisl.ucar.edu/resources/legacy/spherepack/license Thanks, -Filipe -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1