- openSUSE Packaging

Proposal: amend the packaging guidelines for %fillup_only
by Dan Čermák 30 Aug '23

30 Aug '23

Hi list, our packaging guidelines for %fillup_only [1] currently do not suggest anything for the %files section for the files generated in `/etc/sysconfig/`. I would like to suggest that we start adding the newly generated file `/etc/sysconfig/$pkgname` as follows to the %files section: --8<---------------cut here---------------start------------->8--- %files %ghost %config(noreplace) %attr(0600,root,root) /etc/sysconfig/%{name} %dir /etc/sysconfig --8<---------------cut here---------------end--------------->8--- This ensures that rpm is aware of the files as configuration files. Thoughts, opinions? Cheers, Dan Footnotes: [1] https://en.opensuse.org/openSUSE:Packaging_Conventions_RPM_Macros#%fillup_o… -- Dan Čermák <dcermak(a)suse.com> Software Engineer Development tools SUSE Software Solutions Germany GmbH Frankenstr. 146 90461 Nürnberg Germany www.suse.com Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)

4 4

new package help
by Jason Craig 20 Aug '23

20 Aug '23

I'm packaging a module for xrdp that allows it to work with pipewire: https://build.opensuse.org/package/show/home:jacraig:xrdp/pipewire-module-x… Any suggestions would be helpful. A specific question I have is I don't understand the documentation for %suse_update_desktop_file; am I doing this right? Also there is a warning for an unstripped binary (the .so file), saying "this is normally done by RPM at build time". Why isn't it being done? And am I right that I don't worry about a SONAME because it is a plugin? thanks /Jason Craig

4 4

Opensuse15.5: unresolvable: nothing provides python311-cffi, nothing provides python311-cryptography
by Greg Freemyer 18 Aug '23

18 Aug '23

All, The python packaging guidelines call for getting opensuse 15.5 packages to build with python 3.11 I've got roughly 50 packages that use python in security:forensics. Most using the 15.5 repo now build a python311 RPM. But a couple are complaining because python311-cffi.and python311-cryptography packages aren't available in devel:languages:python or devel:languages:python:pytest Can someone take a look and fix those to packages to follow the packaging guidelines? Thanks, Greg

5 9

OBS build with docker command
by Axel Braun 23 Jun '23

23 Jun '23

H, I'm currently working on the packaging of orthanc-ohif [1], a plugin that brings the OHIF viewer to Orthanc. During the preparation a build script processes the OHIF viewer tarball, and, as far as I understand the script, the attempt is made to build a container. The log states: [ 9s] + mkdir -p /home/abuild/rpmbuild/BUILD/OrthancOHIF-1.0/Resources/../OHIF/dist/ [ 9s] + cd /home/abuild/rpmbuild/BUILD/OrthancOHIF-1.0/Resources/../Resources/CreateOHIFDist [ 9s] + docker build --no-cache -t orthanc-ohif-node . [ 9s] DEPRECATED: The legacy builder is deprecated and will be removed in a future release. [ 9s] Install the buildx component to build images with BuildKit: [ 9s] https://docs.docker.com/go/buildx/ [ 9s] [ 9s] Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? [ 9s] error: Bad exit status from /var/tmp/rpm-tmp.mbzWeX (%prep) As I have no experience with docker, is there some process that need to be started beforehand in order to run docker? Thanks Axel [1] https://build.opensuse.org/package/show/home:DocB:Orthanc/orthanc-ohif[1] -------- [1] https://build.opensuse.org/package/show/home:DocB:Orthanc/orthanc-ohif

2 1

Re: openSUSE:Factory - gcc7 - Build problem notification
by Richard Biener 23 Jun '23

23 Jun '23

On Thu, 22 Jun 2023, DimStar / Dominique Leuenberger wrote: > Dear Richard Biener, > > Following-up the reminder of one week ago, we have to inform you that > 'gcc7' is still showing a problem in openSUSE:Factory. See > https://build.opensuse.org/package/show/openSUSE:Factory/gcc7 > > Since Wed Jun 7 23:04:05 2023 we noticed the following problem: > Uninstallable: package bash-5.2.15.x86_64 requires libreadline.so.8()(64bit), but none of the providers can be installed > > Please find the time to make this package usable again. If needed, > also reach out to the broader community, trying to find somebody to > help you fix this package. I've filed boo#1212435 about this new behavior of install-check but nobody feels responsible. It seems install-check changed how it tries installing packages, forcing things even when there's a better provider already installed on the system. But it's hard to tell since there are no sophisticated logs on what it actually does nor do these reminders tell you where the sources of the scripts are. Any hints? Thanks, Richard.

2 2

Python update problem from 15.4 to 15.5
by Eric Schirra 19 Jun '23

19 Jun '23

Now Leap 15.5 is out. But how do I update Python packages which I also have in my Home repo? If I leave projectconfig as intended by Suse, only python311 modules are built. At the moment I have in my projectconfig: # TEST TEST to remove %sle15_python_module_pythons() again!!!!!!!!!! # only visible with: osc buildconfig home:ecsos 15.4; not online in GUI !!!! %if "%_repository" == "15.3" || "%_repository" == "15.4" || "%_repository" == "openSUSE_Leap_15.3" macros: %sle15_python_module_pythons() %global pythons python3 :macros %endif The reason is that the packages can no longer be built for 15.4 with Suse projectconfig. In addition, only 311 Python is built with Suse projectconfig. This means that no upgrade from 15.4 to 15.5 would work. What do I have to enter in my projectconfig so that 15.4 is built and that 3.6 and 3.11 are built for 15.5? Can anyone help me? Regards Eric

3 16

Python packaging problem for Tumblweed in devel repos
by Eric Schirra 15 Jun '23

15 Jun '23

Is it nknown that in the python-devel-repos for almost all packages the following appears:? unresolvable: have choice for python3-packaging needed by python-rpm-packaging: python310-packaging python311-packaging Is this intended? Regards Eric

2 2

python package with manpage
by Fabrice 12 Jun '23

12 Jun '23

Hello I'm sorry, but I'm lost, I need help. I trying to add man pages to my python package. The following seems to work. But I'm not sure if it's the good way. Can you help me? %install ... %python_clone -a %{buildroot}%{_bindir}/radexreader %python_clone -a %{buildroot}%{_mandir}/man1/radexreader.1 %python_clone -a %{buildroot}%{_mandir}/fr/man1/radexreader.1 ... %files %{python_files} ... %python_alternative %{_bindir}/radexreader %python_alternative %{_mandir}/man1/radexreader.1.gz %python_alternative %{_mandir}/fr/man1/radexreader.1.gz ... (full spec file is https://build.opensuse.org/package/view_file/home:luigifab:branches:devel:l…) Thanks!

3 4

triggerin and multiple versions
by Fabrice 10 Jun '23

10 Jun '23

Hello I asked a similar thing to Fedora mailing list. Anyway, I have the same question for my package into openSUSE. I must update the theme depending of Pango version. So I added %trigger sections (in addition of %prep section). Package submitted: https://build.opensuse.org/package/show/X11:common:Factory/human-theme-gtk With 15.4 and 15.5, the following error occurs: error: line 97: Trigger fired by the same package is already defined in spec file: %triggerin -- pango < 1.44 To fix the problem, I have an idea! (copy pasted from my debian/ubuntu package in PPA). But not sure if this is acceptable for my spec file. Updated spec: https://build.opensuse.org/package/show/home:luigifab:branches:X11:common:F… Only one %trigger section (and sed commands removed from %prep section) But usage of rpm command. Can I do that? If I'm not wrong, the trigger is executed: - when my package is installed or updated - when pango is updated Thanks!

2 2

python package with manpage
by Fabrice 09 Jun '23

09 Jun '23

Hello I'm sorry, but I'm lost, I need help. I trying to add man pages to my python package. The following seems to work. But I'm not sure if it's the good way. Can you help me? %install ... %python_clone -a %{buildroot}%{_bindir}/radexreader %python_clone -a %{buildroot}%{_mandir}/man1/radexreader.1 %python_clone -a %{buildroot}%{_mandir}/fr/man1/radexreader.1 ... %files %{python_files} ... %python_alternative %{_bindir}/radexreader %python_alternative %{_mandir}/man1/radexreader.1.gz %python_alternative %{_mandir}/fr/man1/radexreader.1.gz ... (full spec file is https://build.opensuse.org/package/view_file/home:luigifab:branches:devel:l…) Thanks!

1 0