openSUSE Packaging October 2017

packaging@lists.opensuse.org

37 participants
25 discussions

[opensuse-packaging] Selecting GCC version

by Matthias Fehring

Hello, is there a simple way to force the GCC version used to build a package? openSUSE Leap 42.2 for example uses GCC 4.8 as default compiler, but also provides packages for GCC 5.3. Simply using BuildRequires gcc5 pulls gcc5 in but still uses gcc48 to build the package (especially in Build Service). So is there maybe some Buid Service or spec file switch (bcond) to select the used GCC version? Best greetings Matthias Fehring P.S. Not sure if it is a problem with my browser settings, but when I try to search lists.opensuse.org, it is not possible for me to limit the results to a specific list. Even if I set one, I get results from all lists, what makes searching almost impossible, because most results are commit messages. -- Das Gesetz hat zum Schneckengang verdorben, was Adlerflug geworden wäre. (Friedrich Schiller - Die Räuber) www.buschmann23.de GPG-Key: 0x614C3258 GPG Fingerprint: D786 DDF8 4CA9 00BC CDE0 9A5F CCC5 125D 6E87 D4FC

3 years, 2 months

[opensuse-packaging] .changes madness with upstream updates

by Michael Ströder

HI! Sometimes a submission of me gets declined because of changelog being too short or too long referring to this policy: https://en.opensuse.org/openSUSE:Creating_a_changes_file_%28RPM%29#What_goe… While the guide-lines were surely outlined with good aims I have to question the current policy of package changelogs (*.changes) regarding upstream updates. The rules are too blurry and boil down to "Do the right thing". I don't like to provide an extract of an upstream changelog because I'm convinced that no packager is capable of extracting a really meaningful essence from an upstream changelog. Furthermore I assume that upstream developers are also lazy writing docs and the changelog would have been already shorter if still meaningful. So IMO the right way is to.. 1. just mention upstream release and packaging changes xor 2. add the complete changelog. Ciao, Michael.

3 years, 7 months

[opensuse-packaging] Java-build on TW fails suddenly: [javac] error: Source option 1.5 is no longer supported. Use 1.6 or later.

by Axel Braun

Hi, maybe we have a Java-Expert around that can support: projectlibre [1] suddenly fails to build on TW, with the error message: [ 31s] [ 31s] init: [ 31s] [mkdir] Created dir: /home/abuild/rpmbuild/BUILD/projectlibre-1.7.0/openproj_contrib/build [ 31s] [mkdir] Created dir: /home/abuild/rpmbuild/BUILD/projectlibre-1.7.0/openproj_contrib/tmp [ 31s] [ 31s] build: [ 31s] [javac] /home/abuild/rpmbuild/BUILD/projectlibre-1.7.0/openproj_contrib/build.xml:30: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [ 31s] [javac] Compiling 10 source files to /home/abuild/rpmbuild/BUILD/projectlibre-1.7.0/openproj_contrib/build [ 31s] [javac] error: Source option 1.5 is no longer supported. Use 1.6 or later. [ 31s] [javac] error: Target option 1.5 is no longer supported. Use 1.6 or later. [ 31s] [ 31s] BUILD FAILED As the version setting is not explicit mentioned in the spec file I guess it is some implicit definition. Anyone an idea where to look forß Thanks Axel [1] https://build.opensuse.org/package/show/Office/projectlibre -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 years, 7 months

[opensuse-packaging] RFC: changing RPM's default scriptlet locale

by jan matejek

Fellow mortals, more and more packages need their locale to be set to something more sensible than C. This hit me while switching packages over to Python 3. Python gets its encoding from locale, so by default, it won't decode UTF-8 unless the appropriate encoding is set. Right now, when gtk-doc is switched to use Python 3, it won't build UTF-8 documentation. This could be changed in gtk-doc itself (although that is impractical), but perhaps a better way is to change the default locale for spec scriptlets. Right now the macros set it to C. We could switch that to "C.UTF-8", "en_US.UTF-8", or export a special RPM variable that could be overriden in your spec file. Still, the default should be something with UTF-8 in it. I'm now trying to build a Ring 1 staging project with this change. So far I have seen one failure related to it: with en_US.UTF-8, bash ranges (like [a-z]) are case-insensitive and match more than intended. That could be solved by changing the expression, or by setting locale to C.UTF-8. Thoughts, comments? regards m.

3 years, 7 months

[opensuse-packaging] RFC: best practices for referencing bugs/features in commit messages and %changelog

by Adam Spiers

Hi all, openSUSE has a documented policy for how to reference external bugs / features from within package %changelogs: https://en.opensuse.org/openSUSE:Creating_a_changes_file_(RPM)#Bug_fix.2C_f… This works fairly well, but is not perfect, especially in the case where entries in a foo.changes file are automatically generated from upstream SCM repositories, e.g. via the tar_scm source service. Some recent discussion amongst my team got me thinking about whether we could improve this slightly. So I just wrote up my thoughts, which include two possible ways forward: https://github.com/openSUSE/obs-service-tar_scm/issues/207 Feedback on this would be very welcome. Thanks! Adam -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 years, 7 months

[opensuse-packaging] /mounts/work_src_done/SLE15-STAGING/jeos-firstboot not checked in

by ro

Script 'mail_helper' called by ro Hi gmoro(a)suse.com, /mounts/work_src_done/SLE15-STAGING/jeos-firstboot was not checked in by ro for the following reasons: (submitrequest 144700 on https://build.suse.de) request on hold, please create a matching submitrequest to the devel project on OBS (devel:openSUSE:Factory) your dist/autobuild team. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 years, 7 months

[opensuse-packaging] Kiwi - different behaviour on OBS and locally

by Axel Braun

Hi, I'm working on a Kiwi-build (export from Studio) and always run into the error: [ 2461s] Installation of glibc-locale-2.22-8.4.x86_64 failed: [ 2461s] Error: Subprocess failed. Error: RPM failed: warning: /var/cache/kiwi/packages/usr_src_packages_SOURCES_repos_openSUSE:Leap:42.3_standard/glibc-locale.rpm: Header V3 RSA/SHA256 Signature, key ID 3dbdc284: NOKEY [ 2461s] installing package glibc-locale-2.22-8.4.x86_64 needs 340MB on the / filesystem I have added a constraint for a larger disk space during build, I'm now at 10G but the error does not change. So I tried to build locally: Kiwi adds sources: Oct-19 15:19:50 <1> : Setting up source channel: Oct-19 15:19:50 <1> : --> http://download.opensuse.org/update/leap/42.3/oss/ Oct-19 15:19:50 <1> : Setting up source channel: Oct-19 15:19:50 <1> : --> http://download.opensuse.org/distribution/leap/42.3/repo/oss/ Oct-19 15:19:50 <1> : Removing old root directory '/home/docb/isobuild/result/root' Oct-19 15:19:50 <1> : Set root log: /home/docb/isobuild/result/root.3082.screenrc.log... done Oct-19 15:19:50 <1> : Setting target architecture to: x86_64 and later it fails: + SPID=3259 + wait 3259 + /usr/bin/zypper --non-interactive --pkg-cache-dir /var/cache/kiwi/packages --reposd-dir /home/docb/isobuild/result/root//var/cache/kiwi/zypper/repos --solv-cache-dir /home/docb/isobuild/result/root//var/cache/kiwi/zypper/solv --cache-dir /home/docb/isobuild/result/root//var/cache/kiwi/zypper --config /var/cache/kiwi/zypper/zypper.conf.3082 --no-gpg-checks --root /home/docb/isobuild/result/root install --auto-agree-with-licenses --no-recommends filesystem glibc-locale module-init-tools gfxboot-devel shim zypper File '/repodata/repomd.xml' not found on medium 'http://download.opensuse.org/distribution/leap/42.3/repo/oss/' File './noarch/kbd-legacy-2.0.3-3.14.noarch.rpm' not found on medium 'http://download.opensuse.org/distribution/leap/42.3/repo/oss/' Problem occurred during or after installation or removal of packages: Installation aborted by user Please see the above error message for a hint. Repository types are rpm-md. Is this an issue on download.opensuse.org? Thanks for hints! Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 years, 8 months

[opensuse-packaging] Why does the build for succeed[i586] and fail[x86_64] on platforms ?

by doiggl＠velocitynet.com.au

Hello, Questions: Why does the build for succeed[i586] and fail[x86_64] on platforms ? Why does x86_64 fail ,how is spec fixed so build completes. ? Thanks --Glenn [urls] https://build.opensuse.org/package/show/home:doiggl/kernel-vanilla1 https://build.opensuse.org/public/build/home:doiggl/openSUSE_Factory/i586/k… https://build.opensuse.org/public/build/home:doiggl/openSUSE_Factory/x86_64… from logs: https://build.opensuse.org/package/live_build_log/home:doiggl/kernel-vanill… [ 58s] CC arch/x86/purgatory/sha256.o [ 59s] AS arch/x86/purgatory/entry64.o [ 59s] CC arch/x86/purgatory/string.o [ 59s] LD arch/x86/purgatory/purgatory.ro [ 59s] BIN2C arch/x86/purgatory/kexec-purgatory.c [ 59s] CC kernel/bounds.s [ 59s] cc1: error: code model kernel does not support PIC mode [ 59s] make[2]: *** [kernel/bounds.s] Error 1 [ 59s] make[1]: *** [prepare0] Error 2 [ 59s] make[1]: Leaving directory `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.2.1/linux-4.2/linux-obj' [ 59s] make: *** [sub-make] Error 2 [ 59s] make: Leaving directory `/home/abuild/rpmbuild/BUILD/kernel-vanilla-4.2.1/linux-4.2' [ 59s] error: Bad exit status from /var/tmp/rpm-tmp.bXHOnk (%prep) [ 59s] [ 59s] [ 59s] RPM build errors: [ 59s] Bad exit status from /var/tmp/rpm-tmp.bXHOnk (%prep) [ 59s] [ 59s] lamb27 failed "build kernel-vanilla.spec" at Sun Oct 8 13:36:55 UTC 2017. [ 59s] or ## https://build.opensuse.org/public/build/home:doiggl/openSUSE_Factory/i586/k… [ 1967s] ... saving statistics [ 1967s] ... saving built packages [ 1967s] RPMS/i686/kernel-vanilla-devel-4.2.1-2.1.gd2bbe7f.i686.rpm [ 1967s] RPMS/i686/kernel-vanilla-4.2.1-2.1.gd2bbe7f.i686.rpm [ 1967s] SRPMS/kernel-vanilla-4.2.1-2.1.gd2bbe7f.nosrc.rpm [ 1967s] OTHER/_statistics [ 1967s] OTHER/rpmlint.log [ 1967s] [ 1967s] lamb70 finished "build kernel-vanilla.spec" at Sun Oct 8 14:08:44 UTC 2017. [ 1967s] [ 1967s] ### VM INTERACTION START ### [ 1970s] [ 1962.791243] sysrq: SysRq : Power Off [ 1970s] [ 1962.798089] reboot: Power down [ 1970s] ### VM INTERACTION END ### [ 1970s] build: extracting built packages... [ 1970s] RPMS/i686/kernel-vanilla-devel-4.2.1-2.1.gd2bbe7f.i686.rpm [ 1970s] RPMS/i686/kernel-vanilla-4.2.1-2.1.gd2bbe7f.i686.rpm [ 1970s] SRPMS/kernel-vanilla-4.2.1-2.1.gd2bbe7f.nosrc.rpm [ 1970s] OTHER/_statistics [ 1970s] OTHER/rpmlint.log

3 years, 8 months

[opensuse-packaging] Python scripts and rpmlint

by Todd Rme

The current version of rpmlint in devel:languages:python [1] contains a patch relative to the one in openSUSE:Factory. This patch adds additional warnings and errors regarding shebangs in scripts. Specifically, executable scripts with "/usr/bin/env" cause an error and "/usr/bin/python" cause a warning. However, the submission to openSUSE:Factory [2] was rejected 4 months ago over doubts regarding whether there should be an error and whether the checks are really necessary. Since then, devel:languages:python has had this different rpmlint behavior than openSUSE:Factory. I hope we can get this issue resolved so we can bring the two versions back into agreement. 1: https://build.opensuse.org/package/show/devel:languages:python/rpmlint 2: https://build.opensuse.org/request/show/508168 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 years, 8 months

[opensuse-packaging] Building python-urllib for SLES12 GA and SP1 hangs and hangs and hangs...

by Johannes Kastl

Dear python experts, I tried to build python-urllib for SLES12 GA and SP1, but it is hanging in the tests. Previously it failed, because it timed out after 28000s. > https://build.opensuse.org/package/show/home:ojkastl_buildservice:Redfish_S… For SP2 and SP3 it builds in a reasonable time and does not fail or time out. Anything I need to change? Any package or setting that is missing on SP1 and GA? Thanks in advance. Johannes

3 years, 8 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging October 2017