May 2018 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Problems configuring systemd services in package scripts
by John Paul Adrian Glaubitz 22 May '18

22 May '18

Hi! I'm having trouble with systemd services that are supposed to be configured on package update. In particular, I want one service of the previous package version to be stopped and removed and a new service that is being shipped with the new package version to be installed and started. The package in question is google-compute-engine and the affected services are google-ip-forwarding-daemon (to be stopped and removed) google-network-daemon (to be installed and started). I have been following the packaging guidelines from [1] and added the services in question to %pre/post and %preun/postun. However, when installing the new package version over the old one, google-ip-forwarding-daemon gets disabled but not stopped and google-network-daemon is enabled but not started. Hence, a reboot is necessary to make the desired changes effective. I have tried adding "-f" to %service_del_preun and %service_del_preun but that didn't help. Analyzing the RPM scripts with "rpm --scripts -qf <RPM file>" showed that the postinstall script uses "systemctl preset ..." which explains why the services are enabled but not started. Looking at the generated scripts for preuninstall and postuninstall, it seems the case of stopping and removing a service upon upgrade does not seem to be covered. The generated script contains "systemctl try-restart ...". Does anyone have a suggestion what the correct way is to achieve the service changes I have mentioned above? The spec file can be found in [2]. Thanks, Adrian > [1] https://en.opensuse.org/openSUSE:Systemd_packaging_guidelines#Register_syst… > [2] https://build.opensuse.org/package/view_file/Cloud:Tools/google-compute-eng… -- 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] python packages in c:l:p:misc
by Mikhail Terekhov 20 May '18

20 May '18

Hi, Recently the package I maintain (python-eric6) has been moved from c:l:p to c:l:p:misc and I'm not a maintainer any more here. Where it is possible to learn what is going on with c:l:p packages? Regards, Mikhail Terekhov -- 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] Build succeeded in Tumbleweed, but failed in Leap 15.0
by Kyrill Detinov 18 May '18

18 May '18

Hello. Just updated the Viewnior package. Failed in Leap 15.0 with "E: viewnior 64bit-portability-issue ../src/uni-utils.c:109, 110, 111, 112" And is OK in Tumbleweed. Why is this happened? https://build.opensuse.org/package/show/home:Lazy_Kent:devel/viewnior -- WBR Kyrill

2 1

[opensuse-packaging] nothing provides go when building packages in obs for SLE15
by Jordi Massaguer Pla 15 May '18

15 May '18

Hi, I just enabled SLE15 in a project in obs (devel:CaaSP:Head:ControllerNode) and I have all this unresolvables about nothing providing the go package. I checked in the SUSE:SLE-15:GA project and go, go1.7, go1.8 and go1.9 are there. Thus, what is wrong? What am I missing? -- 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] Is there a way to debug exceptions occurring in the %check section in OBS?
by Johannes Weberhofer 14 May '18

14 May '18

Dear all! I have a project where a single test fails with "free(): invalid pointer" running the tests but only in a specific architecture and a specific software environmelnt. I see how that I can use gdb and coredumpctl to debug but I don't see the failing lines. I get: (gdb) bt #0 0xf6fbfec9 in ?? () #1 0x00000000 in ?? () which isn't enough to see where it fails. Is there a way that allows me to debug that problem directly within obs? Best regards -- 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

3 2

[opensuse-packaging] Disabling systemd services in %post for upgrades
by John Paul Adrian Glaubitz 14 May '18

14 May '18

Hi! I am working on updating the google-compute-engine package which needs to disable two systemd services that have been removed in the upstream package. Upstream contains this systemd-specific code to achieve that in %post [1]: if [ -f /lib/systemd/system/google-ip-forwarding-daemon.service ]; then systemctl stop --no-block google-ip-forwarding-daemon systemctl disable google-ip-forwarding-daemon.service fi if [ -f /lib/systemd/system/google-network-setup.service ]; then systemctl stop --no-block google-network-setup systemctl disable google-network-setup.service fi Since we have RPM macros for disabling services on preun and post [2], namely %service_del_preun and %service_del_postun, I was wondering whether there is an equivalent that can be used in %post. Or should I just use systemctl as above but limit the use with suse_version to > 1140? Thanks, Adrian > [1] https://github.com/GoogleCloudPlatform/compute-image-packages/blob/master/s… > [2] https://en.opensuse.org/openSUSE:Systemd_packaging_guidelines#Register_syst… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 7

[opensuse-packaging] Question related to analyzing failing checks
by Johannes Weberhofer 09 May '18

09 May '18

Dear all! I have the following lines in a spec: --------------- %check make %{?_smp_mflags} PHP_EXECUTABLE=%{__php} NO_INTERACTION=1 test && STAT=0 || STAT=$? for f in `ls tests/*.out`; do cat $f ; done exit $STAT --------------- The intention is to show me the contents of ".out" files in a directory to find the reasons for failing tests (which don't fail in my local environment). Unfortunately I get the following result: --------------- [ 472s] make: *** [Makefile:134: test] Error 1 [ 472s] + STAT=2 [ 472s] ++ ls tests/229_Tutorial_fxAnalyzeImage_case1.out tests/236_Imagick_identify_basic.out [ 472s] + for f in `ls tests/*.out` [ 472s] + cat tests/229_Tutorial_fxAnalyzeImage_case1.out [ 472s] ** ERROR: process timed out **+ for f in `ls tests/*.out` [ 472s] + cat tests/236_Imagick_identify_basic.out [ 472s] free(): invalid pointer [ 472s] [ 472s] Termsig=6+ '[' 2 -ne 0 ']' [ 472s] + exit 2 [ 472s] error: Bad exit status from /var/tmp/rpm-tmp.fDnsLs (%check) --------------- Any idea what's wrong? For the reference: The project is https://build.opensuse.org/package/show/home:weberho:branches:server:php:ex… Best regards -- 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

4 9

[opensuse-packaging] submitting 2 packages with the same source
by Jordi Massaguer Pla 08 May '18

08 May '18

Hi packagers :) , I have these two packages which have the same source. I've seen sometimes we have a package foo with 2 spec files, foo.spec and bar.spec, and then we have another package, bar, which is a link to foo. This way, both share the same source. I tried to do that, but when I submitted (osc sr) foo and bar to another project, the link was lost, and instead I had two independent packages with a copy of the same source. Is there a way to keep the link? I tried the "--update-link" option but didn't make a difference. Thanks in advance jordi -- 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] Python package tries to download dependencies during build
by John Paul Adrian Glaubitz 07 May '18

07 May '18

Hi! I'm currently packaging "python-sshtunnel" but I am unable to build the package as the build fails with setuptools trying to download paramiko during install which is not allowed, of course (see below for the fail of the build log). I have already added paramiko to BuildRequires but setuptools still insists on trying to download paramiko. I couldn't find any reference to the download in the python code though. Any ideas? Adrian =============================================================================== [ 6s] using tox.ini: /home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/setup.cfg [ 6s] using tox-2.9.1 from /usr/lib/python2.7/site-packages/tox/__init__.pyc [ 6s] GLOB sdist-make: /home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/setup.py [ 6s] /home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3$ /usr/bin/python2 /home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/setup.py sdist --formats=zip --dist-dir /home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/.tox/dist >/home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/.tox/log/tox-0.log [ 6s] python create: /home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/.tox/python [ 6s] /home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/.tox$ /usr/bin/python2 -m virtualenv --python /usr/bin/python2 python >/home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/.tox/python/log/python-0.log [ 32s] python inst: /home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/.tox/dist/sshtunnel-0.1.3.zip [ 32s] WARNING:Discarding $PYTHONPATH from environment, to override specify PYTHONPATH in 'passenv' in your configuration. [ 32s] /home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3$ /home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/.tox/python/bin/pip install /home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/.tox/dist/sshtunnel-0.1.3.zip >/home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/.tox/python/log/python-1.log [ 41s] ERROR: invocation failed (exit code 1), logfile: /home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/.tox/python/log/python-1.log [ 41s] ERROR: actionid: python [ 41s] msg: installpkg [ 41s] cmdargs: ['/home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/.tox/python/bin/pip', 'install', '/home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/.tox/dist/sshtunnel-0.1.3.zip'] [ 41s] [ 41s] Processing ./.tox/dist/sshtunnel-0.1.3.zip [ 41s] Collecting paramiko>=1.15.2 (from sshtunnel==0.1.3) [ 41s] Retrying (Retry(total=4, connect=None, read=None, redirect=None)) after connection broken by 'NewConnectionError('<pip._vendor.requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7fac82ed2e10>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',)': /simple/paramiko/ [ 41s] Retrying (Retry(total=3, connect=None, read=None, redirect=None)) after connection broken by 'NewConnectionError('<pip._vendor.requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7fac82ed26d0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',)': /simple/paramiko/ [ 41s] Retrying (Retry(total=2, connect=None, read=None, redirect=None)) after connection broken by 'NewConnectionError('<pip._vendor.requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7fac82ed2fd0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',)': /simple/paramiko/ [ 41s] Retrying (Retry(total=1, connect=None, read=None, redirect=None)) after connection broken by 'NewConnectionError('<pip._vendor.requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7fac82ed2410>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',)': /simple/paramiko/ [ 41s] Retrying (Retry(total=0, connect=None, read=None, redirect=None)) after connection broken by 'NewConnectionError('<pip._vendor.requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7fac82ed2c10>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution',)': /simple/paramiko/ [ 41s] Could not find a version that satisfies the requirement paramiko>=1.15.2 (from sshtunnel==0.1.3) (from versions: ) [ 41s] No matching distribution found for paramiko>=1.15.2 (from sshtunnel==0.1.3) [ 41s] [ 41s] /home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3$ /home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/.tox/python/bin/pip freeze >/home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/.tox/python/log/python-2.log [ 41s] python installed: [ 41s] ___________________________________ summary ____________________________________ [ 41s] ERROR: python: InvocationError: /home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/.tox/python/bin/pip install /home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/.tox/dist/sshtunnel-0.1.3.zip (see /home/abuild/rpmbuild/BUILD/sshtunnel-0.1.3/.tox/python/log/python-1.log) [ 41s] error: Bad exit status from /var/tmp/rpm-tmp.YQ1y3R (%check) [ 41s] [ 41s] [ 41s] RPM build errors: [ 41s] Bad exit status from /var/tmp/rpm-tmp.YQ1y3R (%check) [ 41s] [ 41s] suse-laptop failed "build python-sshtunnel.spec" at Fri May 4 14:59:01 UTC 2018. [ 41s] The buildroot was: /var/tmp/build-root/openSUSE_Tumbleweed-x86_64 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 12

[opensuse-packaging] GCC 8 to become the default in Factory
by Richard Biener 04 May '18

04 May '18

We are in the progress to transition to GCC 8 as the compiler for building packages in Factory. You may already have noticed the various bugs that have been filed for packages that need adjustment. https://bugzilla.suse.com/show_bug.cgi?id=1084649 tracks the remaining failures which are - libyui - elfutils (waiting for an upstream release) - ceph - rust There's the openSUSE:Factory:Staging:Gcc7 project which you can build against (though it isn't 100% up-to-date) and the transition will be staged in one of A-C soon. Please keep replies to opensuse-packaging. Richard. -- Richard Biener <rguenther(a)suse.de> SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 2