June 2016 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Building just one subpackage?
by Johannes Kastl 23 Jun '16

23 Jun '16

Dear list, is it possible to build just one of the subpackages that one obs package has? I need to use iptables directly on openSUSE hosts and tried to build the iptables-service that CentOS has as a package, but this is being built from the iptables package, which has some subpackages. So I would like to build just that one subpackage... Anyone done this? Any hints? Or is it possible to only publish one of the packages, not all of them? (I guess not...) Thanks in advance, Johannes

3 3

[opensuse-packaging] Changed versioning scheme
by Sebastian 23 Jun '16

23 Jun '16

Hi, I deal with a package which has a changed versioning scheme. Upstream now has 2.6, while the currently packaged version is 3026 (probably at a time where now version was available from upstream?). As epoch is not used in openSUSE and is ignored. How could I deal with this situation? Looking in the wiki, there is: https://en.opensuse.org/openSUSE:Package_naming_guidelines But I'm not sure which separator I should use. '_', '+', and '.' are explicitly not forbidden. But nothing is explicitly allowed. Is there any recommendation or guideline? My case: I want to update vimplugin-gnupg to the current upstream version: https://build.opensuse.org/package/show/editors/vim-plugins https://github.com/jamessan/vim-gnupg Sebastian -- python programming - mail server - photo - video - https://sebix.at cryptographic key at https://sebix.at/DC9B463B.asc and on public keyservers

3 2

[opensuse-packaging] zypper repo-URLs
by Michael Ströder 23 Jun '16

23 Jun '16

HI! How can I reliably construct the correct repo-URL of e.g. devel:languages:python with information available on the system? How to derive the SuSE-version-specific part? http://download.opensuse.org/repositories/devel:/languages:/python/SLE_12_S… ^^^^^^^^^^ http://download.opensuse.org/repositories/devel:/languages:/python/openSUSE… ^^^^^^^^^^^^^^^^^^^^ Even better if someone even knows an ansible play where this is done. Ciao, Michael.

5 8

[opensuse-packaging] How to proceed about permissions-file-setuid-bit
by Zygmunt Krynicki 22 Jun '16

22 Jun '16

Hi I’m packaging snappy for openSUSE in my home:zyga repository [1]. Snappy is comprised of two parts, snap-confine and snapd. snap-confine contains a setuid executable and rpmlint complains [2]: [ 29s] snap-confine.x86_64: E: permissions-file-setuid-bit (Badness: 10000) /usr/lib/snap-confine is packaged with setuid/setgid bits (04755) [ 29s] If the package is intended for inclusion in any SUSE product please open a bug [ 29s] report to request review of the program by the security team Where should I report the bug exactly (which product, etc) and is there any template I should use for this? Best regards ZK [1] https://build.opensuse.org/package/show/home:zyga/snap-confine [2] https://build.opensuse.org/package/live_build_log/home:zyga/snap-confine/op… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 2

[opensuse-packaging] Subj: Packaging R extensions
by Luigi Baldoni 21 Jun '16

21 Jun '16

Hello, I've recently had the need of some R extensions, so I packaged a few, but I couldn't find any SUSE guideline. Most of the ones I found are in devel:languages:R:CRAN-packages and they seem to be Fedora-related, but they hardly work. Is devel:languages:R:released the correct staging project for the ones that build? Any suggestion will be appreciated! Regards -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 12

[opensuse-packaging] What's the easiest way determine the version of a python3 package during build?
by Dave Plater 21 Jun '16

21 Jun '16

I've looked through python3-numpy package and the only trace of version I can find is in: /usr/lib64/python3.4/site-packages/numpy-1.9.3-py3.4.egg-info and cat /usr/lib64/python3.4/site-packages/numpy-1.9.3-py3.4.egg-info|grep Version produces two lines: Metadata-Version: 1.1 Version: 1.9.3 The one I want is at the bottom. I need to ensure that the version required by blender is the one built against due to python3 abi differences. Thanks Dave P -- 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] Fuse chunkfs undefined reference to `fuse_main_real_compat25'
by Thomas Wagner 05 Jun '16

05 Jun '16

Hi, I tried to package fuse-chunkfs. However, I get linker errors and have no clue why. Manually it builds fine. (Manually means: extracting the archive and doing a "make"). When building on the OBS i get these errors: [ 33s] chunkfs.o: In function `main': [ 33s] chunkfs.c:(.text.startup+0x175): undefined reference to `fuse_main_real_compat25' [ 33s] chunkfs.c:(.text.startup+0x341): undefined reference to `fuse_main_real_compat25' [ 33s] chunkfs.c:(.text.startup+0x3ae): undefined reference to `fuse_main_real_compat25' [ 33s] collect2: error: ld returned 1 exit status Here is the corresponding package: https://build.opensuse.org/package/show/home:Aikhjarto/chunkfs Has anyone an idea why it builds manually with "make" but not via the OBS system? BR Thomas -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 2

[opensuse-packaging] python3 - Symbol PYTHON-NOT-FOUND
by Axel Braun 05 Jun '16

05 Jun '16

Hello, in between I managed to get some python3 packages build. But on Installation I get an error from an unsolved requirement: Requires python < PYTHON-NOT-FOUND python >= PYTHON-NOT-FOUND python python3 python(abi) = 3.4 python3-base .... Anyone seen this before? and knows how I could suppres the requirement? Thanks Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 8

[opensuse-packaging] SuperLU 5.2.1 and CMake: Please review and test
by Christoph Grüninger 02 Jun '16

02 Jun '16

Dear openSuse packagers, I created a merge request for SuperLU to update it to version 5.2.1 and switch to CMake as the build-sytem. I am pretty sure that not everything works now, both packaging-wise and compatiblity-wise. SuperLU 5 changed the signature for dgssvx et al. and packaging relying on SuperLU must be updated. So please help me improving the package by reviewing and testing it. I am not sure whether my merge request should be accepted and we try to fix it in the devel project. SR 398781: https://build.opensuse.org/request/show/398781 My forked and updated package: > https://build.opensuse.org/package/show/home:mathletic:branches:devel:libra… Bye Christoph -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 8