openSUSE Packaging August 2018

packaging@lists.opensuse.org

34 participants
18 discussions

[opensuse-packaging] Pthread error while building weechat package for SLE12-SP2
by MOHIT B. 22 Aug '18

22 Aug '18

Hello Everyone, I am new to RPM packaging and I am trying to package weechat for SLE12-SP3 and am facing `prhread_getspecific` error, > `/home/abuild/rpmbuild/BUILD/weechat-2.2/src/plugins/perl/weechat-perl.c:352: undefined reference to `pthread_getspecific'` I searched over the internet to find the solution but I am unable to understand on how to implement this in packaging, like where to add/remove that certain flag (pthread). Following is the pastebin for my system details, build log, spec file and other links. [System][1] [Spec File][2] [meta prj][3] [Build log][4] [Build commands][5] [lpthread references in the code][6] [1]: https://pastebin.com/ZvmaUSPS [2]: https://build.opensuse.org/package/view_file/openSUSE:Backports:SLE-15/weec… (without %makejobs macro) [3]: https://pastebin.com/u7TmXiXj [4]: https://pastebin.com/H8i6bhu3 [5]: https://pastebin.com/9MB3hKY0 [6]: https://pastebin.com/AKKkKzLb -- Regards, Mohit Bansal (philomath) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 13

[opensuse-packaging] osc dependency download not working
by Todd Rme 14 Aug '18

14 Aug '18

For about a week now, when I try to use osc to build packages locally, the downloading of build dependencies doesn't work. It just hangs, like so: (openSUSE:Factory) libpopt0-1.16-30.5.x86_64.rpm 0% | | 0 B --:-- ETA Does anyone have any idea what is going on and how I can fix it? I have done two TumbleWeed updates and three restarts with no change. -- 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] Python singlespec and localization files
by Todd Rme 13 Aug '18

13 Aug '18

Is there a solution yet to handling localization files with singlespec python packages? I recently had a package submission declined [1] because it doesn't handle the localization files, but last time I checked there was no way to handle them properly. Is there a way to deal with them now? [1] https://build.opensuse.org/request/show/627893 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] %fdupes not expanding correctly
by John Paul Adrian Glaubitz 09 Aug '18

09 Aug '18

Hi! I have tried to use the %fdupes macro in my aws-sdk-cpp package [1]: Index: aws-sdk-cpp.spec =================================================================== --- aws-sdk-cpp.spec (revision 27e40ee71aa9d59fa4dc57c72b2b274f) +++ aws-sdk-cpp.spec (working copy) @@ -52,7 +52,7 @@ low- and high-level SDKs, while minimizing dependencies and providing platform portability (Windows, OSX, Linux, and mobile). -This package contains the shared libaries. +This package contains the shared libraries. %package devel Summary: AWS SDK for C++ - development files @@ -86,7 +86,7 @@ %files devel %defattr(-,root,root) -%{_includedir}/aws/ -%{_libdir}/cmake/ -%{_libdir}/pkgconfig/ +%{_includedir}/aws +%fdupes -s %{_libdir}/cmake +%{_libdir}/pkgconfig %changelog However, when I try to build the package, the %fdupes macro is not expanding correctly and I get the following mess: [ 2425s] Processing files: aws-sdk-cpp-devel-1.5.7-0.x86_64 [ 2425s] error: File must begin with "/": _target=""; [ 2425s] error: File must begin with "/": _symlinks=0; [ 2425s] error: File must begin with "/": _symlinks=1; [ 2425s] error: File must begin with "/": fdupes [ 2425s] error: File must begin with "/": -q [ 2425s] error: File must begin with "/": -p [ 2425s] error: File must begin with "/": -n [ 2425s] error: File must begin with "/": -H [ 2425s] error: File must begin with "/": -o [ 2425s] error: File must begin with "/": name [ 2425s] error: File must begin with "/": -r [ 2425s] error: File must begin with "/": | [ 2425s] error: File must begin with "/": while [ 2425s] error: File must begin with "/": read [ 2425s] error: File must begin with "/": _file; [ 2425s] error: File must begin with "/": do [ 2425s] error: File must begin with "/": if [ 2425s] error: File must begin with "/": test [ 2425s] error: File must begin with "/": -z [ 2425s] error: File must begin with "/": $_target [ 2425s] error: File must begin with "/": ; [ 2425s] error: File must begin with "/": then [ 2425s] error: File must begin with "/": _target="$_file"; [ 2425s] error: File must begin with "/": else [ 2425s] error: File must begin with "/": if [ 2425s] error: File must begin with "/": test [ 2425s] error: File must begin with "/": -z [ 2425s] error: File must begin with "/": $_file [ 2425s] error: File must begin with "/": ; [ 2425s] error: File must begin with "/": then [ 2425s] error: File must begin with "/": _target=""; [ 2425s] error: File must begin with "/": continue [ 2425s] error: File must begin with "/": ; [ 2425s] error: File must begin with "/": fi [ 2425s] error: File must begin with "/": ; [ 2425s] error: File must begin with "/": if [ 2425s] error: File must begin with "/": test [ 2425s] error: File must begin with "/": $_symlinks [ 2425s] error: File must begin with "/": = [ 2425s] error: File must begin with "/": 1; [ 2425s] error: File must begin with "/": then [ 2425s] error: File must begin with "/": ln [ 2425s] error: File must begin with "/": -sf [ 2425s] error: File must begin with "/": ${_target#/home/abuild/rpmbuild/BUILDROOT/aws-sdk-cpp-1.5.7-0.x86_64} [ 2425s] error: File must begin with "/": $_file [ 2425s] error: File must begin with "/": ; [ 2425s] error: File must begin with "/": else [ 2425s] error: File must begin with "/": ln [ 2425s] error: File must begin with "/": -f [ 2425s] error: File must begin with "/": $_target [ 2425s] error: File must begin with "/": $_file [ 2425s] error: File must begin with "/": ; [ 2425s] error: File must begin with "/": fi [ 2425s] error: File must begin with "/": ; [ 2425s] error: File must begin with "/": fi [ 2425s] error: File must begin with "/": ; [ 2425s] error: File must begin with "/": done [ 2425s] [ 2425s] [ 2425s] RPM build errors: [ 2425s] File must begin with "/": _target=""; [ 2425s] File must begin with "/": _symlinks=0; [ 2425s] File must begin with "/": _symlinks=1; [ 2425s] File must begin with "/": fdupes [ 2425s] File must begin with "/": -q [ 2425s] File must begin with "/": -p [ 2425s] File must begin with "/": -n [ 2425s] File must begin with "/": -H [ 2425s] File must begin with "/": -o [ 2425s] File must begin with "/": name [ 2425s] File must begin with "/": -r [ 2425s] File must begin with "/": | [ 2425s] File must begin with "/": while [ 2425s] File must begin with "/": read [ 2425s] File must begin with "/": _file; [ 2425s] File must begin with "/": do [ 2425s] File must begin with "/": if [ 2425s] File must begin with "/": test [ 2425s] File must begin with "/": -z [ 2425s] File must begin with "/": $_target [ 2425s] File must begin with "/": ; [ 2425s] File must begin with "/": then [ 2425s] File must begin with "/": _target="$_file"; [ 2425s] File must begin with "/": else [ 2425s] File must begin with "/": if [ 2425s] File must begin with "/": test [ 2425s] File must begin with "/": -z [ 2425s] File must begin with "/": $_file [ 2425s] File must begin with "/": ; [ 2425s] File must begin with "/": then [ 2425s] File must begin with "/": _target=""; [ 2425s] File must begin with "/": continue [ 2425s] File must begin with "/": ; [ 2425s] File must begin with "/": fi [ 2425s] File must begin with "/": ; [ 2425s] File must begin with "/": if [ 2425s] File must begin with "/": test [ 2425s] File must begin with "/": $_symlinks [ 2425s] File must begin with "/": = [ 2425s] File must begin with "/": 1; [ 2425s] File must begin with "/": then [ 2425s] File must begin with "/": ln [ 2425s] File must begin with "/": -sf [ 2425s] File must begin with "/": ${_target#/home/abuild/rpmbuild/BUILDROOT/aws-sdk-cpp-1.5.7-0.x86_64} [ 2425s] File must begin with "/": $_file [ 2425s] File must begin with "/": ; [ 2425s] File must begin with "/": else [ 2425s] File must begin with "/": ln [ 2425s] File must begin with "/": -f [ 2425s] File must begin with "/": $_target [ 2425s] File must begin with "/": $_file [ 2425s] File must begin with "/": ; [ 2425s] File must begin with "/": fi [ 2425s] File must begin with "/": ; [ 2425s] File must begin with "/": fi [ 2425s] File must begin with "/": ; [ 2425s] File must begin with "/": done [ 2425s] [ 2425s] epyc failed "build aws-sdk-cpp.spec" at Wed Aug 8 11:42:34 UTC 2018. [ 2425s] Does anyone know what the problem is? I used %fdupes as documented in [2]. Adrian > [1] https://build.opensuse.org/package/show/home:glaubitz:branches:Cloud:Tools/… > [2] https://en.opensuse.org/openSUSE:Packaging_Conventions_RPM_Macros#.25fdupes -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 8

[opensuse-packaging] Splitting up binary packages for large SDKs
by John Paul Adrian Glaubitz 08 Aug '18

08 Aug '18

Hello! I am currently working on the AWS SDK for C++ by Amazon, the package is called "aws-sdk-cpp" [1]. After some fiddling and disabling the testsuite for the time being due to an upstream bug [2], I am at the point where I have to decide how to distribute the SDK files among binary packages. Since I haven't built any larger packages for openSUSE before, in particular not any SDKs or library packages which include development files such static libraries, cmake files and header files, I'm wondering whether anyone can give me a heads-up what the common policy is. In Debian, we usually put all shared library files into a lib$NAME$SOVER package where $NAME is the library name and $SOVER it's SO version. Development files such as headers, cmake files and static library archives go into a lib$NAME-dev package. What's the policy for openSUSE? Also, while the package built fine on my AMD EPYC machine (except for the failing installation process due to the missing %files statements), on OBS the package occasionally fails with out-of-memory errors or even the compiler segfaulting. Is there any chance to schedule large packages onto beefier build instances? In case anyone wonders, the package is required within the Public Cloud Team. Adrian > [1] https://build.opensuse.org/package/show/home:glaubitz:branches:Cloud:Tools/… > [2] https://github.com/aws/aws-sdk-cpp/issues/929 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 21

[opensuse-packaging] RPM Boolean Dependencies
by Sean Marlow 07 Aug '18

07 Aug '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi Packagers, Sorry in advance for crossposting (opensuse-buildservice) as I'm not sure the best list to query. Is there support for Boolean Dependencies [1] in the pipeline for openSUSE build service (osc)? It would be nice for example with packages that depend on Django which has two possible packages python-Django and python-Django1. E.g. Requires: (python-Django1 >= 1.11.0 or python-Django >= 2.0.0) A quick test results in failure. It seems the format_spec_file script [2] chokes on boolean dependencies and splits them all up. Requires: (python-Django1 >= 1.11.0 Requires: python-Django >= 2.0.0) Requires: or [1] http://rpm.org/user_doc/boolean_dependencies.html [2] https://github.com/openSUSE/obs-service-format_spec_file/blob/master/prepar… Thanks, - -- Sean Marlow Public Cloud Developer sean.marlow(a)suse.com -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEqA16xWoe2L38VgYCJ30GzZDdUEsFAltoyJ4ACgkQJ30GzZDd UEuyew/9EkHOzz5XsbqpDakXGj+2Y8AUHv40jlvaC2+8m8WWYf/K6LGSKvjsGtVf n/Hj12AsNjXjwYWqz60s5TMhfLOhYUCQEnJX5D1AkeRK46KXKrXIBFW9gOo0OZ3I K6/umtUuPGZ1xbSsaYKZd6ORZ6s9hKVmZHuSRpxGjDkHLGqtJkCqRJFIR8YR98/I O1yy5fkqEDxwfI4N4Wt9wCpvdK64+gXxTcfoOmEA1u41yLeLBHoROpi3wQT/DXR/ vDtu4v7b8BorZT/bpK/IYmgNPd5M+bKpY00a0ZnTRsmKpilO55x0gDhDRdqvxOjs eRWvdqER08d+ONa6nZxOt4TiRE9TygV56uaWLi9e1t0nNi+v4X8XH7SsffwuzbVq GAY39PkU4IhhsE9GJPtxXKGDxqiJGzayJI0m3IYtchGba0mAh+zEo/Iw1TyW+TB/ qvGnvSZEC3tpDSPawPYNEZWYMGhCL6B6bkiqPq95vd2ozDe5hdcWLTRoD77rbUBk LOCDSwhiJCF8t4lwYM83C9iV7hCIrmwf0bpwEgLkOiGrgaphQ6GX3rOigMlWL+vg cflWeyxoGhuoF9ADdymjUAOLWiv9fTkTpacCUpWaobmUCKF0plFSgtHLADIL4Ztc P1FVVvSfqj61oj56GzuopjuT9WoXQCR005OqYdvVAqdYnlcdOvI= =rzmZ -----END PGP SIGNATURE----- N��r��y隊Z)z{.��ZrF��x>�{.n�+��Ǩ��r��i�m��0��ޙ��$j��0��Ǩ�

2 3

[opensuse-packaging] osc build not using all cores
by John Paul Adrian Glaubitz 03 Aug '18

03 Aug '18

Hi! I am currently test-building my new package aws-sdk-cpp [1] on a fast dual-CPU AMD EPYC machines with a total of 32 cores. Looking at htop shows that the build is not using all cores. Building without osc, i.e. just using the upstream source in the normal system environment works in parallel. I have already passed -j 32 to osc but that doesn't help. Any ideas? Adrian > [1] https://build.opensuse.org/package/show/home:glaubitz:branches:Cloud:Tools/… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 8

[opensuse-packaging] Lib name ends with a number
by Torsten Gruner 03 Aug '18

03 Aug '18

Hi, I am currently building a library package that name ends with a number (libfido2) and the version is 0.2.0. The naming convention says it have to end with the major version, but in this case is 0. The package name could be libfido20. But it is a bit confusing. With solution is preferred here? Torsten -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 5

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging August 2018