openSUSE Packaging May 2022

packaging@lists.opensuse.org

8 participants
4 discussions

Packaging ansible-core aka ansible > 2.9: How to package, where to submit to, ...
by Johannes Kastl 27 Jun '22

27 Jun '22

TL;DR: - Package ansible-core in addition to ansible 2.9? - Where to submit to? systemsmanagement or a subproject for "all things ansible"? - Who can help getting the %checks working? Long version: Dear Lars, dear all, I have a lot of ansible related things at work at the moment, so I took a look at the openSUSE ansible package and was wondering why it was still at 2.9. While upstream is at 2.12. Or rather, the newly designed and re-structure ansible-core is at 2.12. Which I did not find for openSUSE. Which is needed for newer versions of ansible-lint (hence it fails to build at the moment). So, I tried to package it and got it building: > https://build.opensuse.org/project/show/home:ojkastl_buildservice:Branch_sy… (ansible-lint-5.4 built fine yesterday, apparently some pytest update broke the checks...) Caveats: - I only targeted Tumbleweed and ignored everything else, to just get it building - I had to disable most of the %check sections as the tests were failing out of the box and I had no time and no desire to dig into that - I kept the ansible-core spec file as short as possible, i.e. I ignored all the RHEL/Fedora/... related things that are present in the I tested the packages on a Tumbleweed VM and could successfully install ansible-base (the 2.10 version) or ansible-core. I added Conflicts to the spec so you can only install one of ansible, ansible-core or ansible-base, while all three of them "Provide" ansible. I could also install the 6.0.x version of ansible-lint and linted a small role (with the desired effect, finding things that the 5.4 version did not find/complain about). So, how should I proceed? 1. I am not sure if packaging only ansible-core (aka updating the ansible package to contain ansible-core) would create problems for users that are not aware of the changes (many modules were removed and are now available as collections via the Ansible Galaxy). Should we package ansible-core separately in addition to ansible 2.9? 2. Where to submit the packages to? Would it make sense to move all things related to ansible to a subproject of systemsmanagement? I guess the python-* dependencies could go to dlp* somewhere (not sure what the current layout is for python things, lost track ...) and could be maintained there. 3. Who could take a look at the packages and help in getting them nice and shiny? Especially the %check sections need a lot of love from someone more knowledgeable than me :-) 4. Not sure if it is worth the effort to try to package this for older distributions, e,g, Leap 15.3 / 15.4 or other distros like CentOS. The systemsmanagement project has a lot of build targets. :-) I can try to drive this and help as much as I can, but I would be glad for help and feedback (packaging guidelines that I missed, etc.). 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 9

devel:gcc: where did gcc42 go?
by Matwey Kornilov 01 Jun '22

01 Jun '22

Hi, I see that there are gcc41 and gcc43 in devel:gcc project, but no gcc42. I've found an avr32 board and would like to play with it, so I would like to have gcc42 in order to make cross-avr32-gcc42 in my home repo. Unfortunately, gcc 4.2 was the last version with avr32 architecture support.

5 5

Packaging npm packages?
by Johannes Kastl 18 May '22

18 May '22

Hi all, I needed npm-groovy-lint on an airgapped system today, and while I was able to manually copy all of the 86 dependencies to that system, I wondered if it was possible to package it in OBS. I got it building and it seems to be working, i.e. I could lint a Jenkinsfile with it. But it is a mess. > https://build.opensuse.org/project/show/home:ojkastl_buildservice:npm_packa… I mostly got it building by copying things from some of the recently updated packages in devel:languages:nodejs, but as most of the packages in that project are > 2 years old I was wondering: There seem to be some packages that are still being maintained, but to me it looks like packaging npm packages is abandoned? Especially as each package seems to bring along all of its dependencies, but (AFAICS) with a subtle difference to golang and the vendoring there: With go packages the vendoring is only used during build, while the dependencies for npm packages seem to be used at runtime, not only for building the package. Hence each and every funny file in each of the dependencies spits out a warning when building the RPM package. Is it worth it to submit my package? Is there a better approach to packaging things like npm-groovy-lint? An automated approach for packaging all of the dependencies? (Just joking...) In other words: If someone wants to have a look and has hints and tips for improving the packaging, fire away... :-) Have a nice day, 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

2 1

LIBSELINUX missing in obs
by Eric Schirra 09 May '22

09 May '22

Hello, i have many unresolvable errors in obs for Leap 15.4. unresolvable: nothing provides libselinux.so.1(LIBSELINUX_1.0)(64bit) needed by tar I see this in other repos also. Think this is an error. Can someone fix this, please? Regards Eric

3 2

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging May 2022