April 2017 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] wkhtmltopdf-qt: Build breaks on Tumbleweed
by Sascha Manns 20 Apr '17

20 Apr '17

Hello List, i prepared a package of qt for wkhtmltopdf on [1]. It builds on Leap 42.2, but not on Tumbleweed. Maybe anyone has an idea, how to get this working? The Tumbleweed Buildlog is placed there [2]. [1] https://build.opensuse.org/package/show/Documentation:Publican/wkhtmltopdf-… [2] https://build.opensuse.org/build/Documentation:Publican/openSUSE_Tumbleweed… Greetings Sascha -- Sascha Manns openSUSE member -- 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] How define a signing key for a project
by Dieter Bloms 19 Apr '17

19 Apr '17

Hello, we are running an own private obs appliance. I've a gpg key and want to use this for all my project. I've added my gpg key in the keyring of /srv/obs/gnupg and defined it in /etc/sign.conf. The rpms were signed by my gpg key, but my gpg key is not used to sign the repos of my projects. The repos were signed with the key of "defaultkey@localobs". I read the online obs reference guide http://openbuildservice.org/help/manuals/obs-reference-guide/cha.obs.signin… but there is only an empty chapter "Configure sign key" Can anybody tell me how to define the project signing key ? Thank you very much. -- Regards Dieter -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the >From field. -- 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] devel:language:python Factory/Tumbleweed build target changes
by Todd Rme 17 Apr '17

17 Apr '17

I have just implemented some changes for the various factory targets of devel:languages:python. Most importantly, the openSUSE_Factory_ARM, openSUSE_Factory_PowerPC, and openSUSE_Factory_zSystems build targets have been rolled into the openSUSE_Tumbleweed build target. They are now architectures of openSUSE_Tumbleweed rather than stand-alone repositories. The existing repositories are still there. Assuming there are no problems they will be disabled on in 2 days (Sunday, April 2) and will be deleted in one week (Friday, April 7 2017). Second, the opensuse_factory_staging build target has already been deleted. It was purely a testing repository, so nobody should have been using it to begin with. Thank you, Todd -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 4

[opensuse-packaging] Some more python singlespec questions/suggestions
by Todd Rme 14 Apr '17

14 Apr '17

A few questions and ideas have popped up for me while doing the singlespec conversion: First, is there a way to use the macros without actually setting up the multiple packages? Particularly I need to use %{python_module foo}, but %python_expand and %python_exec would also be useful. The main use-case is for packages where the unit tests have been moved into a separate -doc spec file to avoid dependency cycles. These packages need to import both python2 and python3 dependencies to for the unit tests, and ideally would use %python_expand or %python_exec to run the tests. But the documentation itself would only be built once, so we don't need multiple rpms. I tried %_python_macro_init but it didn't work. Second, is there a single-spec version of %py(3)_compile? Ideally it would be nice to have %python2_compile and %python3_compile that could be used with %python_expand, as well as a macro that automatically run them both on %{buildroot}%{python(2/3)_sitelib} and %{buildroot}%{python(2/3)_sitearch} (whichever exists). Third, is there a macros to get just the current python major version number? So "2" for python2 and "3" for python3? So projects, such as the jupyter suite, use a "foo2-bar"/"foo3-bar" pattern that we need to support, so having a macro to get the major number is pretty critical especially since IPython is dropping python2 support soon so we need to be able to adjust the build targets easily. Third, the wiki recommends defining %oldpython when you need a specific python-foo dependency. Considering how often the backports are used these days in python2 packages, might this be a macro that would be good to include so people don't have to manually define it? Fourth, I notice the python2-foo versions of the packages (for Tumbleweed) provide python-foo, but the python-foo versions (for older releases) do not provide python2-foo. For maximum simplicity and compatibility, might it be good to have the python-foo versions also provide python2-foo? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 4

[opensuse-packaging] A new home for python3 packages
by Luigi Baldoni 14 Apr '17

14 Apr '17

Hi, I've noticed that some python3 packages I need are, in fact, python3-only and that some other cannot be unified at the moment, if ever. Also with the expectation of a mass-conversion d:l:p3 has been a tad neglected lately, so I was wondering if the packages above could be rehomed to d:l:p. Or perhaps it's too early? Regards -- View this message in context: http://opensuse.14.x6.nabble.com/A-new-home-for-python3-packages-tp5084623.… Sent from the opensuse-packaging mailing list archive at Nabble.com. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 11

[opensuse-packaging] %license is no longer working?
by Sebastian 12 Apr '17

12 Apr '17

Dear list, I wanted to port a python3 package to the singlespec approach and I was stuck with a strange behavior of %license, which is only available on >= 42.2. I therefore use this condition: %if 0%{?leap_version} >= 420200 || 0%{?suse_version} > 1320 %license LICENSE %else %doc LICENSE %endif Which works fine, e.g. here: https://build.opensuse.org/package/show/network:utilities/macchanger But not for this package: https://build.opensuse.org/package/show/home:sebix:branches:devel:languages… Error message is, for 42.2 and TW: [ 40s] RPM build errors: [ 40s] File must begin with "/": MIT [ 40s] File must begin with "/": LICENSE Apparently %license is replaced by the value of the "License:" field. Does anyone have a clue why this is not working now? Sebastian -- python programming - mail server - photo - video - https://sebix.at cryptographic key at https://sebix.at/DC9B463B.asc and on public keyservers

1 0

[opensuse-packaging] python singlespec and quilt
by Hans-Peter Jansen 12 Apr '17

12 Apr '17

Hi, there's another unsolved issue lurking around the corner: quilt stumbles across the singlespec format for the time being. Is somebody working on a solution already? Cheers, Pete -- 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] package is built from outdated sources
by Rüdiger Meier 10 Apr '17

10 Apr '17

Hi, my packages home:rudi_m/dateutils and utilities/dateutils are currently identical. But in utilities/ it is somewhow build from other sources, see the logs. For example it does not apply the patch 0001-fix-when-printing-zones-transitioning-at-INT_MAX-in-.patch What's going on here? cu, Rudi -- 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] fixes for rpmlint ? python singlespec pyc, opt-1.pyc
by Bruno Friedmann 07 Apr '17

07 Apr '17

For any packages build with the new singlespec way there those warnings [ 21s] RPMLINT report: [ 21s] =============== [ 21s] python3-mappyfile.noarch: W: files-duplicate /usr/lib/python3.6/site- packages/mappyfile/__pycache__/tokens.cpython-36.pyc /usr/lib/python3.6/site- packages/mappyfile/__pycache__/tokens.cpython-36.opt-1.pyc [ 21s] python3-mappyfile.noarch: W: files-duplicate /usr/lib/python3.6/site- packages/mappyfile/__pycache__/__init__.cpython-36.opt-1.pyc /usr/lib/ python3.6/site-packages/mappyfile/__pycache__/__init__.cpython-36.pyc [ 21s] python3-mappyfile.noarch: W: files-duplicate /usr/lib/python3.6/site- packages/mappyfile-0.2.0-py3.6.egg-info/not-zip-safe /usr/lib/python3.6/site- packages/mappyfile-0.2.0-py3.6.egg-info/dependency_links.txt [ 21s] python3-mappyfile.noarch: W: files-duplicate /usr/lib/python3.6/site- packages/mappyfile/__pycache__/ordereddict.cpython-36.opt-1.pyc /usr/lib/ python3.6/site-packages/mappyfile/__pycache__/ordereddict.cpython-36.pyc [ 21s] 3 packages and 0 specfiles checked; 0 errors, 4 warnings. Should RPMLINT be fixed to become smarter, and just ignore those, or something still need to be fixed in the python part ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, 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

4 6

[opensuse-packaging] Do we use %{!?_docdir_fmt:-%{version}
by Sascha Manns 04 Apr '17

04 Apr '17

Hello list, currently i'm packaging a app, where upstream (Fedora) uses: %{_docdir}/%{name}-doc%{!?_docdir_fmt:-%{version}} Do we use that? Or must i use it in another way? Greetings Sascha -- Sascha Manns openSUSE member -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0