October 2024 - openSUSE Packaging - openSUSE Mailing Lists

How to properly add a Requires for "I want a desktop" (or maybe "I want a KDE Plasma desktop")?
by Johannes Kastl 03 Nov '24

03 Nov '24

Hi all, I found tail-tray, a KDE Plasma tray application for tailscale. I have a first rough package (that I need to test), but was asking myself how to properly add a dependency on "a desktop environment. If I understood this properly, this tray app should be running fine on a KDE plasma desktop. Maybe also on other desktops, if everything follows the same "tray specification". No idea. But how to add that Requires? What should I depend on? > https://build.opensuse.org/package/show/home:ojkastl_buildservice:Branch_ne… Kind Regards Johannes

3 5

Properly require one of podman or docker **with** specifying a preference for podman?
by Johannes Kastl 31 Oct '24

31 Oct '24

Hi all, while packaging apx (https://github.com/Vanilla-OS/apx) I noticed something funny with distrobox. distrobox has the following line in the spec: Requires: (%{_bindir}/podman or %{_bindir}/docker) However, on a new Tumbleweed VM or container, installing distrobox does not pull in podman, it pulls in docker. I would have assumed that the first in the list, i.e. podman, is being installed if neither is already installed. Is there a way to tell RPM to "favor" podman over docker, if neither is already installed? Kind Regards, Johannes

3 3

How to fix the "#include <filesystem>" error on 15.x / SLES15 SPX?
by Johannes Kastl 30 Oct '24

30 Oct '24

Hi all, next thing regarding tail-tray: It fails to build on 15.x (Leap and SLES15). > [ 53s] [ 18%] Building CXX object CMakeFiles/tail-tray.dir/tail-tray_autogen/mocs_compilation.cpp.o > [ 56s] [ 25%] Building CXX object CMakeFiles/tail-tray.dir/src/main.cpp.o > [ 58s] [ 31%] Building CXX object CMakeFiles/tail-tray.dir/src/MainWindow.cpp.o > [ 58s] In file included from /usr/include/qt6/QtCore/qdir.h:8:0, > [ 58s] from /usr/include/qt6/QtCore/QDir:1, > [ 58s] from /home/abuild/rpmbuild/BUILD/tail-tray-0.2.2/src/MainWindow.cpp:1: > [ 58s] /usr/include/qt6/QtCore/qfile.h:13:10: fatal error: filesystem: No such file or directory > [ 58s] #include <filesystem> > [ 58s] ^~~~~~~~~~~~ > [ 58s] compilation terminated. The few things I found on the net hinted at the gcc compiler. Richard and Alexandre also mentioned it in the SR (https://build.opensuse.org/request/show/1219105) But adding a BuildRequire for gcc14 and gcc14-c++ makes it unresolvable for Leap and still fails to build for SLES15 SPX. As this (also?) uses clang, do I need to specify a newer version of clang to get this going? > https://build.opensuse.org/package/show/home:ojkastl_buildservice:Branch_ne… Kind Regards, Johannes

1 1

New global macro default_firewall_backend
by Marcus Rückert 22 Oct '24

22 Oct '24

hi, since a while ago firewalld, the default firewall tool on TW, switched to nftables. Sadly not all tools followed that switch so now you can run into the situation that you have a perfectly configured firewalld firewall but you traffic still doesnt work, because there is a parallel iptables firewall. ARGH! to make it easier to switch over all tools without having to have a new chain of `%if 0%{?suse_version}` cascades for this, we set up the macro default_firewall_backend in TW, ALP/SLFO and SLE 15.x that should make it easy to have one spec file that can adapt to prefer one of the other depending on the distro. to take an example from the libvirt package: ``` %if 0%{?suse_version} > 1500 %define prefer_nftables 1 %define firewall_backend_priority nftables,iptables %else %define prefer_nftables 0 %define firewall_backend_priority iptables,nftables %endif ``` we can now rewrite this to: ``` %if "%{?default_firewall_backend}" == "nftables" %define prefer_nftables 1 %define firewall_backend_priority nftables,iptables %else %define prefer_nftables 0 %define firewall_backend_priority iptables,nftables %endif ``` if you only care about BuildRequires or some configure option you can of course directly use: ``` BuildRequires: %{default_firewall_backend} [snip] %build %configure --with-firewall-backend=%{default_firewall_backend} ``` hth darix -- Always remember: Never accept the world as it appears to be. Dare to see it for what it could be. The world can always use more heroes.

1 1

unresolvable systemd
by Eric Schirra 13 Oct '24

13 Oct '24

Hello, since a few days the following error appears in OBS for all packages of Leap that use systemd: unresolvable: have choice for pkgconfig(libsystemd): systemd-devel systemd- devel-32bit Is this a bug or do we have to change something? Regards Eric

2 2

source validator
by Peter Czanik 09 Oct '24

09 Oct '24

Hi, I wanted to update syslog-ng from 4.8.0 to 4.8.1 in Tumbleweed, however the source validator fails on me. I cannot even compile the current state of syslog-ng form Base:System, which obviously worked a couple of months ago. Any ideas what could go wrong? leap155b:~ # osc bco Base:System syslog-ng Using existing branch project: home:czanik:branches:Base:System A home:czanik:branches:Base:System A home:czanik:branches:Base:System/syslog-ng A home:czanik:branches:Base:System/syslog-ng/syslog-ng-4.8.0.tar.gz A home:czanik:branches:Base:System/syslog-ng/syslog-ng-service-prepare A home:czanik:branches:Base:System/syslog-ng/syslog-ng.changes A home:czanik:branches:Base:System/syslog-ng/syslog-ng.conf.default A home:czanik:branches:Base:System/syslog-ng/syslog-ng.service A home:czanik:branches:Base:System/syslog-ng/syslog-ng.spec A home:czanik:branches:Base:System/syslog-ng/syslog-ng.sysconfig At revision a9b8369aa8ad041d5915af957fd43181. leap155b:~ # cd home\:czanik\:branches\:Base\:System/syslog-ng/ leap155b:~/home:czanik:branches:Base:System/syslog-ng # osc build Building syslog-ng.spec for openSUSE_Factory/x86_64 Running source_service 'format_spec_file' ... Running source_service 'source_validator' ... ERROR: syslog-ng-4.8.0.tar.gz mentioned in spec file is not tracked. ERROR: syslog-ng.sysconfig mentioned in spec file is not tracked. ERROR: syslog-ng.conf.default mentioned in spec file is not tracked. ERROR: syslog-ng.service mentioned in spec file is not tracked. ERROR: syslog-ng-service-prepare mentioned in spec file is not tracked. Aborting: service call failed: /usr/lib/obs/service/source_validator --outdir /root/home:czanik:branches:Base:System/syslog-ng/tmpn_ouvaub.source_validator.service Source service run failed! Peter

2 2

Open submit requests for Cloud:Tools
by Johannes Kastl 04 Oct '24

04 Oct '24

Hi all, could someone please review my open SRs to Cloud:Tools? > https://build.opensuse.org/request/show/1203629 > https://build.opensuse.org/request/show/1203630 > https://build.opensuse.org/request/show/1204358 I can also send another SR to request maintainer rights for this project to help out in answering to SRs... Kind Regards, Johannes

1 0