openSUSE Packaging March 2023

packaging@lists.opensuse.org

11 participants
5 discussions

Announce: Conditional Build Dependencies per Project
by Thorsten Kukuk 25 Mar '23

25 Mar '23

Hi, Our base packages include support for all sorts of features, making our base OS very large due to dependencies. While this is not a problem for e.g. openSUSE Tumbleweed, where the extra packages do not really matter in the overall size, it is a big problem when building a small single-purpose OS where you want something really small without any unnecessary packages. Like ALP. The "useless" packages create yet another problem: Libraries are installed for features that are not supported or do not work. E.g. AppArmor and SELinux are exclusive, so why should e.g. ALP ship AppArmor that can't work and isn't supported, but creates a high maintenance overhead on all sides without any benefit? We use already %bcond in our spec files set in the project config for various reasons, one is to bootstrap the distro. Another reason is, that it looks like as some maintainers build already smaller versions of some packages for their need in their projects. To avoid that e.g. ALP is shipped with AppArmor and SELinux, while only SELinux will be used, we decided to "formalize" and document this: https://en.opensuse.org/openSUSE:Package_Conditional_Build_Dependencies 85% of the keywords are already used today in projects. What does this mean for you? 1. if somebody added this %bcond to your packages, please accept them and forward them to Factory. 2. if you are working on a package and have dependencies mentioned in the list, please consider to make your package configurable in this regard. 3. If we create bug reports for ALP since you are a maintainer of a core package which has dependencies we don't want to see, please work on them with a higher priority. 4. Yes, it is known that you cannot build every package without this dependencies. Thanks, Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nuernberg, Germany Managing Director: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman (HRB 36809, AG Nürnberg)

9 15

Building python-libtmux: OBS errors out with "couldn't create directory /run/tmux/399 (No such file or directory)"
by Johannes Kastl 17 Mar '23

17 Mar '23

Hi all, I am trying to package the new ansible-sign utility. One of the dependencies is python-libtmux, which builds successfully. But only locally or if I disable the %check section. > https://build.opensuse.org/package/show/home:ojkastl_buildservice:Branch_de… Inside OBS the checks fail with this error message: > [ 54s] if proc.stderr: > [ 54s] > raise exc.LibTmuxException(proc.stderr) > [ 54s] E libtmux.exc.LibTmuxException: ["couldn't create directory /run/tmux/399 (No such file or directory)"] > [ 54s] > [ 54s] ../../BUILDROOT/python-libtmux-0.21.0-5.1.x86_64/usr/lib/python3.8/site-packages/libtmux/server.py:483: LibTmuxException My guess is that somehow /run and /run/tmux are not setup properly. I tried to create it manually, I tried "systemd-tmpfiles --create", but nothing worked. /run is existing, but only contains utmp and some other directory I forgot. What would be the OBS way to get that working? Or is this not possible inside OBS? Thanks in advance! Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

2 2

license of not built library
by Cor Blom 11 Mar '23

11 Mar '23

Hi, If the source package include a library that is not built and not part of the binary, should it then be mentioned in the license line in the spec? This is specifically about musescore, which contain google crash client, but we disable it during build. It is the only part with an apache license. Thanks, Cor

3 2

Buildservice _constraints
by Arjen de Korte 07 Mar '23

07 Mar '23

What does the specifying jobs [1] in the _constraints file actually do? I expected it to work similarly as specifying 'osc build --jobs N' on the command line, but looking in the logs of a remote build server, it see that it actually runs with a higher number '+ /usr/bin/make -O VERBOSE=1 -j8'. Is there a way to limit the requested number of parallel build jobs in the _constraints file, or is the only way to put this in the spec file like '%cmake_build --jobs 4'? [1] https://openbuildservice.org/help/manuals/obs-user-guide/cha.obs.build_job_…

4 4

Proper dependencies for bash/fish/zsh completion sub-packages
by Johannes Kastl 04 Mar '23

04 Mar '23

Hi all, what are the proper dependencies for packages that contain some completion for bash, zsh or fish? Should they Require bash-completion/fish/zsh? I came across this today, as I was wondering why the bash-completion subpackage of kubie did not require the bash-completion package. Of course it makes no sense to install a zsh completion package if I am not using zsh, but should this not be reflected in the subpackage's requirements? For bash it might be even more prominent, because the completion files for kubie are not being used without the bash-completion package itself (if I am understanding the scripts correctly). Thanks in advance and have a nice weekend, everyone! Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

3 4

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging March 2023