openSUSE Packaging June 2022

packaging@lists.opensuse.org

12 participants
7 discussions

Enable Leap 15.4 build for server:http
by Fusion Future 01 Aug '22

01 Aug '22

Hi dear maintainers: openSUSE Leap 15.4 has been released, but server:http still doesn't have builds for 15.4. Could you enable it? Thanks in advance.

2 1

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

Base:System: "x86_64 is not a valid arch for the repository openSUSE_Factory"?
by Bernhard Voelker 20 Jun '22

20 Jun '22

Trying to locally build a package of Base:System on my native x86_64 system doesn't work any longer: $ osc co Base:System/coreutils ... $ cd Base:System/coreutils $ osc build x86_64 is not a valid arch for the repository openSUSE_Factory, use one of: armv7l, ppc64le, riscv64, s390x I tried with the packages coreutils, findutils, tar and grep. I could swear this used to work a while ago. Do I do something wrong? Is there a misconfiguration? Thanks & have a nice day, Berny

3 4

.desktop file Icon= entry How to ensure the icon is found?
by David C. Rankin 16 Jun '22

16 Jun '22

All, I have worked to create a .desktop file for small editor package. The desktop file creates the entry in the menu in the proper category/subcategory, but the icon isn't shown. The minimal .desktop file is: [Desktop Entry] Name=GtKate GenericName=GtKate Text Editor Comment=Open Source-Code & Text Files Exec=gtkate Icon=gtkate Terminal=false Type=Application Categories=Qt;KDE;TextEditor;Utility; MimeType=text/plain; The icon is installed to /usr/share/gtkwrite/img I've noticed some apps use /usr/share/appname/icons Is there some part of the xdg icon search that looks in /usr/share/appname for an "icons" directory? The xdg spec says it will search /usr/share/icons/hicolor/48x48/apps, and makes reference to user defined paths, but doesn't provide a great deal of detail. So would changing (or soft-linking) my .../img directory to an .../icons directory do it? Or would I need to specify the full path to search somewhere? I've tried: Icon=/usr/share/gtkate/img/gtkate but that didn't cause the icon to appear (though I didn't reload anything, I simply changed the .desktop file). Or is hicolor/48x48/apps the way to go? I notice many apps do not put anything there, but their icon still appears in the menu. What's the best way to go here? -- David C. Rankin, J.D.,P.E.

4 4

My new python package not handling debug files correctly - python-pyhaif
by Greg Freemyer 15 Jun '22

15 Jun '22

All, It has been a while since I posted here, but I can't figure this one out RE: https://build.opensuse.org/package/show/home:gregfreemyer:Tools-for-forensi… The log ends with: [ 53s] python38-pyheif.x86_64: E: filelist-forbidden-debuginfo (Badness: 10000) /usr/lib/debug/.build-id [ 53s] python38-pyheif.x86_64: E: filelist-forbidden-debuginfo (Badness: 10000) /usr/lib/debug/.build-id/37 [ 53s] python38-pyheif.x86_64: E: filelist-forbidden-debuginfo (Badness: 10000) /usr/lib/debug/.build-id/37/2c88e7d76a369fcbc38f0bf2043299989cf87e [ 53s] python38-pyheif.x86_64: E: filelist-forbidden-debuginfo (Badness: 10000) /usr/lib/debug/.build-id/37/2c88e7d76a369fcbc38f0bf2043299989cf87e.debug [ 53s] python38-pyheif.x86_64: E: filelist-forbidden-debuginfo (Badness: 10000) /usr/lib/debug/.build-id/50 [ 53s] python38-pyheif.x86_64: E: filelist-forbidden-debuginfo (Badness: 10000) /usr/lib/debug/.build-id/50/6a22f5c17b6517902262691f5955df4a86c4b5 [ 53s] python38-pyheif.x86_64: E: filelist-forbidden-debuginfo (Badness: 10000) /usr/lib/debug/.build-id/50/6a22f5c17b6517902262691f5955df4a86c4b5.debug [ 53s] python38-pyheif.x86_64: E: filelist-forbidden-debuginfo (Badness: 10000) /usr/lib/debug/.build-id/89 [ 53s] python38-pyheif.x86_64: E: filelist-forbidden-debuginfo (Badness: 10000) /usr/lib/debug/.build-id/89/543ec164635e5a71c97c059af6120d89d54af2 [ 53s] python38-pyheif.x86_64: E: filelist-forbidden-debuginfo (Badness: 10000) /usr/lib/debug/.build-id/89/543ec164635e5a71c97c059af6120d89d54af2.debug [ 53s] File may only be packaged in the -debuginfo subpackage. I have: %exclude %{_prefix}/lib/debug But I continue to get those errors. Any advice? Thanks, Greg -- Greg Freemyer Advances are made by answering questions. Discoveries are made by questioning answers. — Bernard Haisch

2 2

subpackage - how to specify noarch?
by David C. Rankin 03 Jun '22

03 Jun '22

All, I have two editors that I have created rpms for. Both rely on the same additional language-specs for gtksourceview, so I just separated those files into a subpackage for packaging purposes. I want the subpackge to be noarch. I've tried adding BuildArch: noarch to the subpackage declaration block, but that doesn't work. Currently I have: %package -n gtksv2-lang-extra Version: 1.0 Summary: Additional syntax files for GtkSourceView2 License: GPL-2.0+ Group: GTK %description -n gtksv2-lang-extra Additional syntax files for GtkSourceView2 (asm-intel, xorg, qmake, gnuplot, apache) BuildArch: noarch <snip> %files -n gtksv2-lang-extra /usr/share/gtksourceview-2.0/language-specs/apache.lang /usr/share/gtksourceview-2.0/language-specs/asm-intel.lang /usr/share/gtksourceview-2.0/language-specs/gnuplot.lang /usr/share/gtksourceview-2.0/language-specs/qmake.lang /usr/share/gtksourceview-2.0/language-specs/xorg.conf.lang I looked at %lang_package, but if I attempt to use %lang_package instead of %package, the build fails saying the subpackage can't be found. What's the trick to create the subpackage as noarch? -- David C. Rankin, J.D.,P.E.

2 2

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

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging June 2022