openSUSE Packaging July 2017

packaging@lists.opensuse.org

42 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, 5 months

[opensuse-packaging] factory-auto says "Unknown tag: bad spec python-wheel.spec"

by Sebastian

Hi, This request: https://build.opensuse.org/request/show/512806 got declined by factory-auto with this comment: > Output of check script: > Source validator failed. Try "osc service localrun source_validator" > https://files.pythonhosted.org/packages/source/w/wheel/wheel-0.29.0.tar.gz https://files.pythonhosted.org/packages/source/w/wheel/wheel-0.29.0.tar.gz error: line 21: Unknown tag: bad spec python-wheel.spec What does this mean? When running the specified command locally, I don't get this error. I got this error sometime in the last months in another request too, but I don't remember which one it was now. Sebastian -- python programming - mail server - photo - video - https://sebix.at cryptographic key at https://sebix.at/DC9B463B.asc and on public keyservers

4 years, 1 month

[opensuse-packaging] Poll about Url vs URL in RPM preamble

by Tomas Chvatal

Hi all, As per complains here that we should use URL rather than Url in the preamble of the spec-files I've decided to create quick doodle poll. From parser perspective there is 0 difference but since there is vocal proposition for URL instead of Url that is now replaced by spec- cleaner. I decided to create a poll where the majority will become default set value. [1] I will keep the doodle running until 14.8. and announce the results afterwards and tweak spec-cleaner if other value wins. I still think Url is fine as it is not URL in the "Uniform Resource Locator" but just variable name. Thanks for voting Tom [1] https://beta.doodle.com/poll/9y6gfunm8bm8cz3b

4 years, 1 month

[opensuse-packaging] How to control repositories enabled for obs build?

by John Paul Adrian Glaubitz

Hi! I am currently working on updating the Microsoft Azure SDK for Python for SLE12SP2. All of these Python packages use setuptools upstream which causes some problems on SLE12SP2 because they use a feature not present in the old version of setuptools in SLE12P2, namely the "~=" operator which is used to denote compatible versions in Python. To resolve this problem, I simply patched the setup.py to replace "~=" with ">" and made sure the proper version dependencies are noted in the spec file. This worked all fine and without problems until I worked on a package (python-azure-sdk) that I branched from the devel:languages:python project. Although the package uses the aforementioned operator in setup.py, the package still builds fine in a SLE12SP2 environment without the necessary patch. After digging some time, I noticed that the chroot for the package branched from devel:languages:python was using a current version of setuptools, namely version 36.2.2 while my other packages were using the setuptools version present in SLE12SP2 which is 1.10.x. So, I have obviously the problem that OBS is enabling the devel:languages:python repository for the build which it shouldn't. Is there a way to tell OBS which repositories it's allowed to use during build and which not? Or do I have to branch the package into a specific project to avoid the inclusion of these particular repositories? Thanks, Adrian -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 years, 1 month

[opensuse-packaging] Re: perl-Text-Unicode overrides perl-libintl-perl

by Andreas Schwab

On Jul 28 2017, Martin Pluskal <mpluskal(a)suse.cz> wrote: > Removal of "BuildRequires: perl-libintl-perl" was intentional, as with > external perl-libintl-perl internal testsuite does not work. Did you file a bug? Andreas. -- Andreas Schwab, SUSE Labs, schwab(a)suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 years, 1 month

[opensuse-packaging] I need help to complete build kernel with [reiser4-for-4.11.0.patch] applied.

by doiggl＠velocitynet.com.au

Hello, Can you assist with a kernel [with reiser4-for-4.11.0.patch] build problem? kernel with reiser4 patch applied ok - reiser4-for-4.11.0.patch I need help to complete build process kernel with [reiser4-for-4.11.0.patch] applied ok. what steps to complete the build Thanks -Glenn spec https://build.opensuse.org/package/view_file/home:doiggl/kernel-vanilla/ker… https://build.opensuse.org/package/show/home:doiggl/kernel-vanilla build log: https://build.opensuse.org/build/home:doiggl/openSUSE_13.1/x86_64/kernel-va… [build log [1]shows: [ 70s] + sort -u [ 70s] + cd linux-4.12 [ 70s] + /home/abuild/rpmbuild/SOURCES/apply-patches --vanilla /home/abuild/rpmbuild/SOURCES/series.conf .. [ 70s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.kernel.org/patch-4.12.1 [ 70s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.kernel.org/patch-4.12.1-2 [ 70s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.kernel.org/patch-4.12.2-3 [ 70s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.kernel.org/patch-4.12.3-4 [ 70s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.rpmify/reiser4-for-4.11.0.patch [ 71s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.rpmify/firmware-path [ 71s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.rpmify/cloneconfig.diff . . . [ 76s] Second extended fs support (EXT2_FS) [N/m/y/?] n [ 76s] The Extended 3 (ext3) filesystem (EXT3_FS) [N/m/y/?] n [ 76s] The Extended 4 (ext4) filesystem (EXT4_FS) [Y/n/m/?] y [ 76s] Use ext4 for ext2 file systems (EXT4_USE_FOR_EXT2) [Y/n/?] y [ 76s] Ext4 POSIX Access Control Lists (EXT4_FS_POSIX_ACL) [Y/n/?] y [ 76s] Ext4 Security Labels (EXT4_FS_SECURITY) [Y/n/?] y [ 76s] Ext4 Encryption (EXT4_ENCRYPTION) [Y/n/?] y [ 76s] EXT4 debugging support (EXT4_DEBUG) [N/y/?] n [ 76s] JBD2 (ext4) debugging support (JBD2_DEBUG) [N/y/?] n [ 76s] Reiser4 (EXPERIMENTAL) (REISER4_FS) [N/m/y/?] (NEW) aborted! [ 76s] [1] https://build.opensuse.org/package/live_build_log/home:doiggl/kernel-vanill… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 years, 1 month

[opensuse-packaging] RFC: removing python-django (not python-Django)

by Todd Rme

devel:languages:python currently has two version of Django, the up-to-date python-Django package and the obsolete python-django package. The latter (python-django) has not been updated in two years, and the up-to-date python-Django provides python-django. However, there are still a few projects that link to it. I would like to remove it, but I want to give other projects that link to it a chance to it break the link and/or link to python-Django instead. If there are no objections, I will remove python-django in one week, on Friday, August 4. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 years, 1 month

[opensuse-packaging] golang - internal compiler error

by Axel Braun

Hi, I'm trying to update mongo-tools [1] to version 3.4.6, and encounter an error on the Leap-builds: [ 210s] # github.com/mongodb/mongo-tools/common/archive [ 210s] .gopath/src/github.com/mongodb/mongo-tools/common/archive/ demultiplexer.go:47: internal compiler error: haspointers: unexpected type, NamespaceStatus map[string]int [ 210s] error: Bad exit status from /var/tmp/rpm-tmp.7Px93a (%build) This breaks on go 1.6.2 (Leap) but works for go 1.8.x (TW) Should I report this upstream, or any other idea? Cheers Axel [1] https://build.opensuse.org/package/show/home:DocB/mongo-tools -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 years, 1 month

[opensuse-packaging] obs-service-format_spec_file is moving comments around

by Michal Srb

Hi, I have problem with format_spec_file, it moves comments to different lines for no obvious reason. For example in SUSE:SLE-12-SP1:Update/tigervnc: Snipped from original spec file: Url: http://tigervnc.org/ BuildRoot: %{_tmppath}/%{name}-%{version}-build Summary: A high-performance, platform-neutral implementation of VNC License: GPL-2.0 and MIT Group: System/X11/Servers/XF86_4 # would need fixing to use fPIC in common/CMakeLists.txt ExcludeArch: s390 Source1: https://github.com/TigerVNC/tigervnc/archive/v%version}.tar.gz Source3: vnc.xinetd After format_spec_file: Url: http://tigervnc.org/ BuildRoot: %{_tmppath}/%{name}-%{version}-build Summary: A high-performance, platform-neutral implementation of VNC # would need fixing to use fPIC in common/CMakeLists.txt License: GPL-2.0 and MIT Group: System/X11/Servers/XF86_4 ExcludeArch: s390 Source1: https://github.com/TigerVNC/tigervnc/archive/v%{version}.tar.gz Source3: vnc.xinetd The comment moved to a different line where it doesn't make sense. Is it a bug in obs-service-format_spec_file? Michal Srb -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 years, 1 month

[opensuse-packaging] perl-Text-Unicode overrides perl-libintl-perl

by Olaf Hering

Does anyone happen to know why perl-Text-Unicode overrides perl-libintl-perl (or perl(Locale::Textdomain))? devel:languges:perl/perl-Event-ExecFlow fails because libintl-perl is not installed, even if specified as BuildRequires. So far I have not spotted a Substitute or Provides/Obsoletes in prjconf. Olaf

4 years, 1 month

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging July 2017