openSUSE Packaging April 2015

packaging@lists.opensuse.org

46 participants
34 discussions

[opensuse-packaging] release-notes-openSUSE requires google-opensans-fonts

by Felix Miata

TW $SUBJECT can't be right, but trying to zypper rm opensans wants to remove releasenotes. :-( -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 years, 10 months

[opensuse-packaging] Python 2 and 3 in single specfile

by Jan Matějek

Fellow packagers, after some discussions in our team, we figured that it would be neat if we could build python modules for Python 2 and 3 from a single spec file. Now that a great deal of python modules work with both pythons, this makes a lot of sense. A good deal of work can be done by RPM macros. Then we could even seamlessly start building modules for PyPy, Jython and other pythons. A sample specfile, and the corresponding set of RPM macros, is attached. As you can see, the appropriate subpackage is generated automatically by %python_subpackages, build and install steps are handled through %python_build and %python_install respectively. There is some more magic involved, as well as possibilities for customization. There is a minor problem with BuildRequires. As long as you only need python-devel, it's not too bad to just list $flavor-devel requirements by hand. It's worse when you require more subpackages, because then you need all of them in both python2 and python3 versions. It would be nice to be able to specify %{python_require Mako} and expand that to all the necessary BuildRequires, but OBS blocks us here, because the limited environment will not expand such macros. mls, ro, or anyone from the OBS team, would it be possible to solve this? Still, it basically doesn't matter if you list all the BuildRequires twice in one spec or in two specs, so there. Another thing I'm still unclear on are the filelists. It's certainly possible to make a generic filelist, something along the lines of: %package -n %flavor-%modname # python3-Mako %defattr(-, root, root) %{%flavor_sitelib}/* %{%flavor_sitearch}/* but this doesn't solve docs and possible other files. Again, obviously, we can write the filelists by hand. But if you have good suggestions for some smart macros here, I'd love to see them. What do you folks think? Comments, questions? m.

5 years, 7 months

[opensuse-packaging] git package and ca-certificates-mozilla dependency

by Stefan Schweter

Dear packaging maintainers and users, when playing around the openSUSE docker image and installing git I figured out some "missing" dependency: ca-certificates-mozilla. There's no direct or indirect depedency for installing ca-certificates-mozilla. That results to these kind of error messages: git clone https://github.com/gitlabhq/gitlab-ci-runner.git fatal: unable to access 'https://github.com/gitlabhq/gitlab-ci-runner.git/': SSL certificate problem: unable to get local issuer certificate What do the packagers think about adding a ca-certificates-mozilla package dependency? For example on Arch Linux, git has a curl dependency. And curl has a "ca-certificates" dependency (this is not equivalent to the openSUSE ca-certificates package, as it includs all Common CA certificates). So it can be called an indirect dependency. Thanks in advance for your feedback! Regards, Stefan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 years, 9 months

[opensuse-packaging] suse_macros bug on SLE_11?

by Darin Perusich

Hello, The %install_info on SLE_11_SP3 is calling sbin/install-info which is not fully qualified, is this on purpose or is it a bug? I''ve linkpac'd Publishing/texinfo -> devel:languages:R:released and the %post is failing which calls %install_info yet install-info is available in the build-root. [ 116s] Preparing packages for installation... [ 116s] info-5.2-89.1 [ 117s] install-info: No such file or directory for /usr/share/info/info-stnd.info.gz [ 117s] error: %post(info-5.2-89.1.x86_64) scriptlet failed, exit status 1 [ 117s] makeinfo-5.2-89.1 [ 117s] texinfo-5.2-89.1 [ 117s] install-info: No such file or directory for /usr/share/info/texinfo.info.gz [ 117s] install-info: No such file or directory for /usr/share/info/texinfo.info-1.gz [ 117s] install-info: No such file or directory for /usr/share/info/texinfo.info-2.gz [ 117s] install-info: No such file or directory for /usr/share/info/texinfo.info-3.gz [ 117s] error: %post(texinfo-5.2-89.1.x86_64) scriptlet failed, exit status 1 [ 117s] failed to install rpms, aborting build Thanks! -- Later, Darin -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 years, 9 months

[opensuse-packaging] Use of generics in "requires" statements?

by Greg Freemyer

All, My SR to add a couple of generic "Requires:" to the wordpress spec file has been rejected because they are generic: https://build.opensuse.org/request/show/304469 My re-opened SR was also rejected. Can someone explain to my why the use of Requires: httpd Requires: mod_php_any is wrong. I know the below will also work, but I don't see why we should be restrictive Requires: apache2 Requires: apache2-mod_php5 That is unless wordpress is strictly a apache2 based tool, but I can't imagine that is true. fyi: In the SR Eric did say: "httpd only for other than opensuse." I don't understand that since apache2, lighttpd and nginx all provide httpd in their opebnsuse packages. He also said "zypper se php_mod_any" show "package not found" That is true, but "zypper se" doesn't search for generic provides so that logic would invalidate all use of generic requires. Thanks Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 years, 9 months

[opensuse-packaging] Re: [opensuse-project] [Announcement] SUSE Release SLE Sources to openSUSE Project

by Jan Engelhardt

>SUSE is preparing to pro-actively release a significant portion of >the SUSE Linux Enterprise source code,[...], to the openSUSE >project. These packages will give the community an enduring, stable, >and maintained base, upon which exciting[...] Mighty goodlord, this is too much salestalk/marketspeak. The significant portion of SLE code is from openSUSE and/or other open projects anyway, so that may not be all that exciting. >An openSUSE community distribution built upon this base can plan for >a sustainable stream of packages, as we intend to continue releasing >and updating this platform in line with the cadence of SUSE Linux >Enterprise and it's [sic] service packs. Reads to me like "The openSUSE distribution converges with SLE and the two become the new SUSE Linux (open, this time)". Would not even be bad. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 years, 10 months

[opensuse-packaging] gdb extensions

by Matwey V. Kornilov

Hi, What are the general guidelines to package gdb python extensions? I would like to include gdb python printers with eigen3-devel package, because it is near impossible to debug Eigen matrices without it. The problem is that I have not found any packages to use as a reference. In my opinion I just have to put /etc/gdbinit.d/eigen3 file, and scripts into /usr/share/gdb/python/eigen3 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 years, 10 months

[opensuse-packaging] How to configure osc subproject to use GCC v5 from devel:gcc by default, for all packages?

by PGNd

I want to use gcc-5 from http://download.opensuse.org/repositories/devel:/gcc/openSUSE_13.2 by default in all builds within an osc subproject. To use gcc-5 preferentially in local builds, I mod the local ENV with export CC="/usr/bin/gcc-5" export CXX="/usr/bin/g++-5" ln -sf /usr/bin/gcc-5 /usr/bin/gcc ln -sf /usr/bin/g++-5 /usr/bin/g++ ln -sf /usr/bin/gcc-5 /usr/bin/cc ln -sf /usr/bin/g++-5 /usr/bin/c++ ln -sf /usr/bin/cpp-5 /usr/bin/cpp For OBS builds, I've added the source repo to the subproject's 'meta prj' <repository name="openSUSE_13.2"> <path project="Kernel:stable" repository="standard"/> + <path project="devel:gcc" repository="openSUSE_13.2"/> <path project="openSUSE:13.2" repository="standard" /> <arch>x86_64</arch> </repository> For project-wide setting of gcc == v5.0 for OBS builds, is adding %define gcc_version 50 to my project's 'meta prjconf' sufficient? Do I also need to (1) modify the ENV (CC, CXX, ln ...) prior to %configure/%make &/or (2) specify BuildRequires: gcc-5 ... ? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 years, 10 months

[opensuse-packaging] 'osc build' fails @ RPM error: "file not found". spec file's BuildRoot:/%{buildroot} ignored, files instead installed under 'build-root' from ~/.oscrc.

by PGNd

I'm packaging cryptodev-linux in a local osc instance. Upstream source is from git. It can be trivially built/installed with cd cryptodev-linux make make install which installs two files /usr/include/crypto/cryptodev.h /lib/modules/4.0.0-2.g53b125b-desktop/extra/cryptodev.ko For obs, I use osc source_services, configured with edit _service <services> <service name="tar_scm" mode="disabled"> <param name="url">https://github.com/cryptodev-linux/cryptodev-linux.git</param> <param name="scm">git</param> <param name="exclude">.git</param> </service> <service name="recompress" mode="disabled"> <param name="file">*.tar</param> <param name="compression">gz</param> </service> <service name="set_version" mode="disabled"> <param name="basename">cryptodev-linux</param> </service> </services> On exec of disabled run osc service dr the git source is pulled and tar'd in the local pkg dir, ls -1 . cryptodev-linux-1428749261.da73010.tar.gz cryptodev-linux.spec _service and 'version' is propagated to the spec file edit cryptodev-linux.spec # spec file for package cryptodev-linux # # Copyright (c) 2015 PGNd <dev+opensuse(a)pgnd.us> # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed # upon. The license for this file, and modifications and additions to the # file, is the same license as for the pristine package itself (unless the # license for the pristine package is not an Open Source License, in which # case the license is the MIT License). An "Open Source License" is a # license that conforms to the Open Source Definition (Version 1.9) # published by the Open Source Initiative. # Please submit bugfixes or comments via http://bugs.opensuse.org/ # # cryptodev-linux.spec Name: cryptodev-linux Version: 1428749261.da73010 Release: 0 Summary: Package cryptodev-linux License: GPL-2.0 Group: Productivity/Networking/Security Url: http://cryptodev-linux.org/ Source: %{name}-%{version}.tar.gz BuildArch: x86_64 BuildRequires: kernel-desktop-devel BuildRoot: %{_tmppath}/%{name}-%{version}-build %description Cryptodev-linux is a device that allows access to Linux kernel cryptographic drivers; thus allowing of userspace applications to take advantage of hardware accelerators. %prep %setup -q -n %{name}-%{version} make clean %build make %{?_smp_mflags} %install make DESTDIR=%{buildroot} install %clean rm -rf %{buildroot} %files %defattr(-, root, root) %{buildroot}/usr/include/crypto/cryptodev.h %changelog * Sat Apr 25 2015 PGNd <dev+opensuse(a)pgnd.us> - init The exec of the build fails osc build --noinit --local-package cryptodev-linux.spec WARNING: source service from package or project will not be executed. This may not be the same build as on server! Building cryptodev-linux.spec for openSUSE_13.2/x86_64 Use local '/usr/local/src/obs_workspace/home:pgnd:pgnd-stack/cryptodev-linux/.osc/_buildinfo-openSUSE_13.2-x86_64.xml' file as buildinfo Use local '/usr/local/src/obs_workspace/home:pgnd:pgnd-stack/cryptodev-linux/.osc/_buildconfig-openSUSE_13.2-x86_64' file as buildconfig Updating cache of required packages 0.0% cache miss. 108/108 dependencies cached. Verifying integrity of cached packages using keys from openSUSE:13.2, devel:tools, Kernel Writing build configuration Running build logging output to /var/tmp/build-root/openSUSE_13.2-x86_64/.build.log... [ 0s] Memory limit set to 33093592KB [ 0s] Using BUILD_ROOT=/var/tmp/build-root/openSUSE_13.2-x86_64 [ 0s] Using BUILD_ARCH=x86_64:i686:i586:i486:i386 [ 0s] [ 0s] [ 0s] desk.lan started "build cryptodev-linux.spec" at Sun Apr 26 00:54:48 UTC 2015. [ 0s] [ 0s] [ 0s] processing recipe /usr/local/src/obs_workspace/home:pgnd:pgnd-stack/cryptodev-linux/cryptodev-linux.spec ... [ 0s] running changelog2spec --target rpm --file /usr/local/src/obs_workspace/home:pgnd:pgnd-stack/cryptodev-linux/cryptodev-linux.spec [ 1s] ----------------------------------------------------------------- [ 1s] ----- building cryptodev-linux.spec (user abuild) [ 1s] ----------------------------------------------------------------- [ 1s] ----------------------------------------------------------------- [ 1s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature /usr/src/packages/SOURCES/cryptodev-linux.spec [ 1s] Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.9NhwX4 [ 1s] + umask 022 [ 1s] + cd /usr/src/packages/BUILD [ 1s] + cd /usr/src/packages/BUILD [ 1s] + rm -rf cryptodev-linux-1428749261.da73010 [ 1s] + /usr/bin/gzip -dc /usr/src/packages/SOURCES/cryptodev-linux-1428749261.da73010.tar.gz [ 1s] + /bin/tar -xf - [ 1s] + STATUS=0 [ 1s] + '[' 0 -ne 0 ']' [ 1s] + cd cryptodev-linux-1428749261.da73010 [ 1s] + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . [ 1s] + make clean [ 1s] make -C /lib/modules/4.0.0-4.g27299c0-desktop/build SUBDIRS=`pwd` clean [ 1s] make[1]: Entering directory '/usr/src/linux-4.0.0-4.g27299c0-obj/x86_64/desktop' [ 2s] make[1]: Leaving directory '/usr/src/linux-4.0.0-4.g27299c0-obj/x86_64/desktop' [ 2s] rm -f *~ [ 2s] CFLAGS= KERNEL_DIR=/lib/modules/4.0.0-4.g27299c0-desktop/build make -C tests clean [ 2s] make[1]: Entering directory '/usr/src/packages/BUILD/cryptodev-linux-1428749261.da73010/tests' [ 2s] rm -f *.o *~ cipher cipher-aead hmac speed async_cipher async_hmac async_speed sha_speed hashcrypt_speed fullspeed cipher-gcm cipher-aead-srtp cipher_comp hash_comp hmac_comp [ 2s] make[1]: Leaving directory '/usr/src/packages/BUILD/cryptodev-linux-1428749261.da73010/tests' [ 2s] + exit 0 [ 2s] Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.Lr1Uxf [ 2s] + umask 022 [ 2s] + cd /usr/src/packages/BUILD [ 2s] + /usr/bin/rm -rf /usr/src/packages/BUILDROOT/cryptodev-linux-1428749261.da73010-0.x86_64 [ 2s] ++ dirname /usr/src/packages/BUILDROOT/cryptodev-linux-1428749261.da73010-0.x86_64 [ 2s] + /usr/bin/mkdir -p /usr/src/packages/BUILDROOT [ 2s] + /usr/bin/mkdir /usr/src/packages/BUILDROOT/cryptodev-linux-1428749261.da73010-0.x86_64 [ 2s] + cd cryptodev-linux-1428749261.da73010 [ 2s] + make -j4 [ 2s] make -C /lib/modules/4.0.0-4.g27299c0-desktop/build SUBDIRS=`pwd` modules [ 2s] make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. [ 2s] make[1]: Entering directory '/usr/src/linux-4.0.0-4.g27299c0-obj/x86_64/desktop' [ 2s] CC [M] /usr/src/packages/BUILD/cryptodev-linux-1428749261.da73010/ioctl.o [ 3s] CC [M] /usr/src/packages/BUILD/cryptodev-linux-1428749261.da73010/main.o [ 3s] CC [M] /usr/src/packages/BUILD/cryptodev-linux-1428749261.da73010/cryptlib.o [ 4s] CC [M] /usr/src/packages/BUILD/cryptodev-linux-1428749261.da73010/authenc.o [ 4s] CC [M] /usr/src/packages/BUILD/cryptodev-linux-1428749261.da73010/zc.o [ 5s] CC [M] /usr/src/packages/BUILD/cryptodev-linux-1428749261.da73010/util.o [ 5s] LD [M] /usr/src/packages/BUILD/cryptodev-linux-1428749261.da73010/cryptodev.o [ 5s] Building modules, stage 2. [ 5s] MODPOST 1 modules [ 5s] CC /usr/src/packages/BUILD/cryptodev-linux-1428749261.da73010/cryptodev.mod.o [ 5s] LD [M] /usr/src/packages/BUILD/cryptodev-linux-1428749261.da73010/cryptodev.ko [ 5s] make[1]: Leaving directory '/usr/src/linux-4.0.0-4.g27299c0-obj/x86_64/desktop' [ 5s] + exit 0 [ 5s] Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.qbPpuC [ 5s] + umask 022 [ 5s] + cd /usr/src/packages/BUILD [ 5s] + cd cryptodev-linux-1428749261.da73010 [ 5s] + make DESTDIR=/usr/src/packages/BUILDROOT/cryptodev-linux-1428749261.da73010-0.x86_64 install [ 5s] make -C /lib/modules/4.0.0-4.g27299c0-desktop/build SUBDIRS=`pwd` modules_install [ 5s] make[1]: Entering directory '/usr/src/linux-4.0.0-4.g27299c0-obj/x86_64/desktop' [ 7s] INSTALL /usr/src/packages/BUILD/cryptodev-linux-1428749261.da73010/cryptodev.ko [ 7s] DEPMOD 4.0.0-4.g27299c0-desktop [ 7s] make[1]: Leaving directory '/usr/src/linux-4.0.0-4.g27299c0-obj/x86_64/desktop' [ 7s] Installing cryptodev.h in /usr/include/crypto ... [ 7s] + /usr/lib/rpm/brp-compress [ 7s] + /usr/lib/rpm/brp-suse [ 7s] calling /usr/lib/rpm/brp-suse.d/brp-05-permissions [ 7s] calling /usr/lib/rpm/brp-suse.d/brp-15-strip-debug [ 7s] calling /usr/lib/rpm/brp-suse.d/brp-25-symlink [ 7s] calling /usr/lib/rpm/brp-suse.d/brp-30-desktop [ 7s] WARNING: '/usr/lib/rpm/brp-desktop.data/suse-screensavers.menu' does not exist [ 7s] WARNING: '/usr/lib/rpm/brp-desktop.data/preferences-gnome.menu' does not exist [ 7s] WARNING: '/usr/lib/rpm/brp-desktop.data/applications-kmenuedit.menu' does not exist [ 7s] calling /usr/lib/rpm/brp-suse.d/brp-35-rpath [ 7s] calling /usr/lib/rpm/brp-suse.d/brp-40-rootfs [ 7s] calling /usr/lib/rpm/brp-suse.d/brp-45-tcl [ 7s] calling /usr/lib/rpm/brp-suse.d/brp-50-check-python [ 7s] calling /usr/lib/rpm/brp-suse.d/brp-55-boot-scripts [ 7s] calling /usr/lib/rpm/brp-suse.d/brp-60-hook [ 7s] calling /usr/lib/rpm/brp-suse.d/brp-65-lib64-linux [ 7s] calling /usr/lib/rpm/brp-suse.d/brp-72-extract-appdata [ 7s] Processing files: cryptodev-linux-1428749261.da73010-0.x86_64 [ 7s] error: File not found: /usr/src/packages/BUILDROOT/cryptodev-linux-1428749261.da73010-0.x86_64/usr/include/crypto/cryptodev.h [ 7s] [ 7s] [ 7s] RPM build errors: [ 7s] File not found: /usr/src/packages/BUILDROOT/cryptodev-linux-1428749261.da73010-0.x86_64/usr/include/crypto/cryptodev.h The buildroot was: /var/tmp/build-root/openSUSE_13.2-x86_64 In the .spec, I specified BuildRoot: %{_tmppath}/%{name}-%{version}-build The build exec seems to ignored that, instead using [ 0s] Using BUILD_ROOT=/var/tmp/build-root/openSUSE_13.2-x86_64 apparently sourced from grep "build-root =" ~/.oscrc #build-root = /var/tmp/build-root/%(repo)s-%(arch)s The files spec instructs looking for the installed file, cryptodev.h, in its install dir under %{buildroot}. %files %defattr(-, root, root) %{buildroot}/usr/include/crypto/cryptodev.h <-- The file is, apparently, not found under the spec-file-specified %{buildroot} [ 7s] RPM build errors: [ 7s] File not found: /usr/src/packages/BUILDROOT/cryptodev-linux-1428749261.da73010-0.x86_64/usr/include/crypto/cryptodev.h but is actually located under the used BUILD_ROOT [ 0s] Using BUILD_ROOT=/var/tmp/build-root/openSUSE_13.2-x86_64 find /var/tmp/build-root/openSUSE_13.2-x86_64 -name 'cryptodev.h' /var/tmp/build-root/openSUSE_13.2-x86_64/usr/include/crypto/cryptodev.h /var/tmp/build-root/openSUSE_13.2-x86_64/usr/src/packages/BUILD/cryptodev-linux-1428749261.da73010/crypto/cryptodev.h What in the spec file needs to change so that the build process finds the built file in the correct buildroot? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 years, 10 months

[opensuse-packaging] disable /run RPMLINT check

by Michael Ströder

HI! Can I disable this RPMLINT check? [ 168s] RPMLINT report: [ 168s] =============== [ 176s] (none): E: badness 10000 exceeds threshold 1000, aborting. [ 176s] openldap2.x86_64: E: non-ghost-in-run (Badness: 10000) /run/slapd [ 176s] A file or directory in the package is located in /run. Files installed in this [ 176s] directory should be marked as %ghost and created at runtime to work properly [ 176s] in tmpfs /run setups. While I understand the motivation this leads to more troubles with packages trying to support older distribution versions where /run is not yet available. Or is that no concern anymore? Ciao, Michael.

5 years, 10 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging April 2015