December 2017 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Frustration with mongodb
by Martin Pluskal 04 Dec '17

04 Dec '17

Hello As some of you might know or actually use it, we currently have mongodb in Factory [1] and corresponding devel project [2], and active maintainer is/was wanted for some time [3]. Given that I personally have no use for mongodb (or never had), and given that it currently fails to build for Factory (due to scons python3 migration) I am bit frustrated with its state. Given that today I got feedback by community: <randy-sk_> [11:31:38] zbite niekto Martina Puskala. Mongo, co je v tom repozitari https://build.opensuse.org/package/show/server:database/mongodb, je od jeho super upravy rozbite. Plus sa tam snazil dolepit mongotoolsy a le samozrejme to jeho spec sa nebuildi, kedze je to v samostatnom subore :D Which would loosely translate to request that someone beats me up for breaking mongodb (I assume that is related to accepting request [4]), my frustration with mongodb has reached its limit. If you are interested in maintaining this package, let me know I will add you as maintainer and reviewer in devel project, if noone steps in I will create delete request for Factory next week. Cheers Martin 1. https://build.opensuse.org/package/show/openSUSE:Factory/mongodb 2. https://build.opensuse.org/package/show/server:database/mongodb 3. https://lists.opensuse.org/opensuse-factory/2015-09/msg00078.html 4. https://build.opensuse.org/request/show/542220 -- 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] Bug in singlespec?
by Axel Braun 03 Dec '17

03 Dec '17

Morning, I was building a new package, setup was made as for singlespec, but by definition %define skip_python2 1 it should only be py3. I noticed a build failure for Leap 42.3, while Tumbleweed builds fine. The error is: [ 3s] ----------------------------------------------------------------- [ 3s] I have the following modifications for gnuhealth-thalamus.spec: [ 3s] ----------------------------------------------------------------- [ 3s] ----- building gnuhealth-thalamus.spec (user abuild) [ 3s] ----------------------------------------------------------------- [ 3s] ----------------------------------------------------------------- [ 3s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' -- nosignature /home/abuild/rpmbuild/SOURCES/gnuhealth-thalamus.spec [ 3s] error: line 82: Package does not exist: %files -n python-gnuhealth- thalamus No idea why it asks for this file, it was defined nowhere.... I have rewritten the specfile for Python3 only , and then it builds for Leap 42.3 as well. See: https://build.opensuse.org/package/show/Application:ERP:Tryton:4.2/ gnuhealth-thalamus I guess this is an error in the singlespec macros? Best regards Axel

2 2

[opensuse-packaging] Build package for TW (>=20171129) with a need of postgresql-devel
by Bruno Friedmann 02 Dec '17

02 Dec '17

I'm stuck actually to resolve the case I need to build a package for actual TW In spec I have 112 Requires: postgresql >= 9.1 113 Requires: postgresql-devel >= 9.1 In build log I have [ 22s] postgresql-10-1.2 [ 23s] postgresql10-10.1-1.2 [ 23s] postgresql96-devel-9.6.5-1.1 Of course then pg_config isn't found later. I've tried to adapt the project conf by adding the new 1550 TW version, but still fail. %if 0%{?suse_version} >= 1550 && 0%{?is_opensuse} == 1 Prefer: postgresql10-devel %endif %if 0%{?suse_version} >= 1325 && 0%{?suse_version} < 1550 && 0%{?is_opensuse} == 1 Prefer: postgresql96-devel %endif Any review or help is welcome. Could it be a bug, that now on TW if I request to install postgresql-devel zypper only propose this package (with a 10.1 version) and have no dep to the real default one postgresql10-devel ? I didn't remember having this kind of trouble with previous upgrade. -- 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

1 0

[opensuse-packaging] Tumbleweed will change suse_version to 1550
by Dominique Leuenberger / DimStar 01 Dec '17

01 Dec '17

Dear Tumbleweed hackers and packagers, It is about time that openSUSE:Factory aka Tumbleweed moves its suse_version definition up again. There were quite some build hacks in place that were explicitly pinned on 1330, as the idea was to be able to get rid of them by the time we move the version. As this is dragging on for too long though, we changed the hacks to also apply on Tumbleweed with a newer suse_version and all those tweaks are now in place. Which means we can move forward. The new suse_version will be 1550 - starting with December 1st 2017 What's the rationale behind 1550: * SLE15 / Leap 15 are using 1500 (for their entire lifecycle). * Tumbleweed is supposed to be 'ahead of the game', so we plant it between SLe/Leap15 and SLE/Leap16 (don't ask about timeframes for those, nobody knows) While packaging, you should never reference version 1550 though. your thing are compatible to suse_version >= 1500 (meaning all Leap 15.x versions) OR, if something comes into play on newer .x levels, you'd do: %if %{suse_version} > 1500 || %{sle_version} >= 150100 # Feature is available since Leap 15.1 BuildRequires: new-dep %endif This will indicate that starting with 15.1 things are present, and for TW as well. If you don't know yet about the Leap version it might become available, simply skip the sle_version check (but keep the check for suse_version > 1500) The change of suse_version has no visible impact to the end user, this is merely of interest to developers/packagers. Cheers, Dominique

1 1