November 2015 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] How to flexibly express "Requires" dependency to have same version as "BuildRequires"
by Roman Evstifeev 24 Nov '15

24 Nov '15

Hi. Is there any convenient way to force package depend (at runtime) on libfoo version X, where X is the version of libfoo-devel, that was used when package was built? Is it possible to do so, without explicitly specifying version (X) itself in the spec file? So that upgrading libfoo to version X+1 in the same project won't break this package, and just trigger package rebuild with new dependencies on X+1. The problem arises in package Ardour, which detects liblilv version on compile time and uses new api if available. This forces package to have same version of run-time "Requires" dependency as "BuildRequires". -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

8 12

Re: [opensuse-packaging] Doc packages require devel packages?
by Dmitriy Perlow 23 Nov '15

23 Nov '15

Ferdinand Thiessen <f.thiessen(a)gmx.de> Sun, 22 Nov 2015 15:22:36 +0300: > Hello, Hi! > Short question: Should a -doc package require the -devel package? Imho only -devel packages should require -devel packages. > Best regards, > > Ferdinand -- Best regards, Dmitriy Perlow -- 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] golang packaging: build with tags
by Matwey V. Kornilov 22 Nov '15

22 Nov '15

Hello, I need to build the package with '-tags popcntgo', how should I proceed with %gobuild macro? -- 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] Issue with Education / Tumbleweed
by Bruno Friedmann 22 Nov '15

22 Nov '15

I've a package gcompris-qt which fail to build for Tumbleweed. The build is successful for 13.2, Leap, Factory. When I try to build it locally to check what's going wrong I'm getting this warning osc build --clean openSUSE_Tumbleweed --jobs=8 Building gcompris-qt.spec for openSUSE_Tumbleweed/x86_64 Getting buildinfo from server and store to /home/bruno/openSUSE/obs/Education/gcompris-qt/.osc/_buildinfo-openSUSE_Tumbleweed-x86_64.xml Getting buildconfig from server and store to /home/bruno/openSUSE/obs/Education/gcompris-qt/.osc/_buildconfig-openSUSE_Tumbleweed-x86_64 Updating cache of required packages The build root needs packages from project 'openSUSE:Factory:ARM'. Note that malicious packages can compromise the build result or even your system. Would you like to ... 0 - quit (default) 1 - always trust packages from 'openSUSE:Factory:ARM' 2 - trust packages just this time ? The build root needs packages from project 'devel:languages:perl'. Note that malicious packages can compromise the build result or even your system. Would you like to ... 0 - quit (default) 1 - always trust packages from 'devel:languages:perl' 2 - trust packages just this time ? I'm afraid there's a fault in the project configuration. I've opened a bug report https://bugzilla.opensuse.org/show_bug.cgi?id=956164 -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- 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] Doc packages require devel packages?
by Ferdinand Thiessen 22 Nov '15

22 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Short question: Should a -doc package require the -devel package? Best regards, Ferdinand -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJWUbOLAAoJEHh1c9hzJRAHSD0IAI+dl7ocS50l8Bb3LGEkxCdm QmLft0Y0/fo9pmRGjhoQUFbf5ouxYN28x5gbZPl2FFdJxhv/rtxzCbIkB127TEEZ 2rFFNpEz+5XZrlvFvEHe4gcUy+tOJsTUGqFYSuyZp6MahjuyZ7mPEqv5ZGSjD9fR ZpcUs34WRu4+IgKyU/G5+eRwNEcoiTy0hMeK/e0QNlz+5qWgLxO5NM26H5Xeh1Tu 6OeSxXLaN49Px1aO3KtH302HByQGqop9dEHOp81tuMz2MWeV3rWgiy2ftJFsQGUR GcQJr/lS9ZiaJEbdeyK/W05+0Q8A8E9ASLU/k3orYMwf3gVteQa2t4b+QX89HOE= =vTvD -----END PGP SIGNATURE----- -- 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] Is it possible to avoid recompilation on osc build error and continue from there next time?
by Roman Evstifeev 22 Nov '15

22 Nov '15

Hi. Some packages take long time to compile. If i have an error in the spec file, "osc build" will compile and fail after that (if for example %files section is wrong). Is it possible to tell osc to continue from the point just after compilation? O maybe some other trick to avoid loosing time and cpu cycles compiling again? -- 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] ANNOUNCE: meaningful snapshot repository in openSUSE:Factory
by Stephan Kulow 21 Nov '15

21 Nov '15

Hi, I was waiting for a long time for OBS to implement a proper API to clone repositories, so we could integrate the snapshot repository into the Tumbleweed release process. This still didn't happen, but last Tuesday I had a cruel idea for a workaround to this problem. So Dominque and me implemented a way throughout the week. So now whenever we put the current openSUSE:Factory into openQA, we clone the standard repository into openSUSE:Factory/totest repository and whenever we release what openQA tested, we clone the totest repository into openSUSE:Factory/snapshot. We basically created our own API to do that ;) This means: the snapshot repo now contains whatever is on download.opensuse.org/tumbleweed (plus or minus 2 hours) and the OBS has a *chance* to build fitting kernel modules in time. Now we unfortunately buy one problem with the other - the OBS will now rebuild way more often and will be much busier. The introduction of the snapshot repository was to give an answer to people always staring at "scheduled" or "blocked" packages. For details on the OBS copes with that situation, my old blog post is still relevant: https://lizards.opensuse.org/2010/12/16/how-we-use-our-power/ Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- 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] naming: libsord-devel vs libsord-0-devel
by Roman Evstifeev 19 Nov '15

19 Nov '15

libsord-devel: http://download.opensuse.org/repositories/home:/rncbc/openSUSE_13.2/x86_64/… libsord-0-devel: http://download.opensuse.org/repositories/multimedia:/libs/openSUSE_13.2/x8… The former, unlike the latter, have a binary /usr/bin/sord-validate included in the package. Which is the correct one? Or they are both correct? This is painful. Could it be named consistently? -- 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] Problem with python-package - test run
by Axel Braun 19 Nov '15

19 Nov '15

Hi all, I was recently building new modules for the tryton-server. One of the modules runs a test-script: %check python setup.py test Problem: Unlike the installation, which takes all resources from the repository (e.g. the server module trytond), the test wants to download this from pypi: [ 39s] + python setup.py test [ 39s] running test [ 39s] Searching for trytond>=3.8,<3.9 [ 39s] Reading https://pypi.python.org/simple/trytond/ [ 39s] Download error on https://pypi.python.org/simple/trytond/: [Errno -2] Name or service not known -- Some packages may not be found! [ 39s] Couldn't find index page for 'trytond' (maybe misspelled?) [ 39s] Scanning index of all packages (this may take a while) [ 39s] Reading https://pypi.python.org/simple/ [ 39s] Download error on https://pypi.python.org/simple/: [Errno -2] Name or service not known -- Some packages may not be found! [ 39s] No local packages or download links found for trytond>=3.8,<3.9 [ 39s] error: Could not find suitable distribution for Requirement.parse('trytond>=3.8,<3.9') [ 39s] error: Bad exit status from /var/tmp/rpm-tmp.IMguh4 (%check) [ 39s] [ 39s] [ 39s] RPM build errors: [ 39s] Bad exit status from /var/tmp/rpm-tmp.IMguh4 (%check) The idea to add trytond as build requirement did not help either, as this produces dome other funny error messages (about some missing mysql-stuff - which I see first time now) Is there a way to tell the test to *not* download from pypi, but to use local resources instead? 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 6

[opensuse-packaging] Files could not be expanded
by Green Basilisk 17 Nov '15

17 Nov '15

Hello, since I changed the URL in the service file to https://dl.bintray.com/otfried/generic/ipe/7.1/ipe-7.1.9-src.tar.gz it works locally on my laptop but on the build service I get the error Files could not be expanded: Running /usr/lib/obs/service/download_url --protocol https --host dl.bintray.com --path otfried/generic/ipe/7.1/ipe-7.1.9-src.tar.gz --filename ipe-7.1.9.tar.gz --outdir /lxc.tmp.29408/out The content of the service file: <services> <service name="download_url"> <param name="protocol">https</param> <param name="host">dl.bintray.com</param> <param name="path">otfried/generic/ipe/7.1/ipe-7.1.9-src.tar.gz</param> <param name="filename">ipe-7.1.9.tar.gz</param> </service> <service name="set_version"> </service> </services> The package's URL: https://build.opensuse.org/package/show/home:greenbasilisk:branches:graphic… Best regards, Heinz -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0