- openSUSE Packaging

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

Having fun with RPM's spec and shells and quoting
by Johannes Kastl 28 Sep '24

28 Sep '24

Dear packagers, does anyone have an idea, how I can get a variable, containing spaces, into the ldflags argument to "go build ..."? When the ldflags have to be quoted themselves? > https://build.opensuse.org/package/show/home:ojkastl_buildservice:Branch_de… > go build \ > -mod=vendor \ > -buildmode=pie \ > -ldflags=" \ > -X github.com/updatecli/updatecli/pkg/core/version.GoVersion=${GO_VERSION} \ > -X github.com/updatecli/updatecli/pkg/core/version.Version=v%{version} \ > -X github.com/updatecli/updatecli/pkg/core/version.BuildTime=${BUILD_DATE}" \ > -o bin/%{name} ./main.go GO_VERSION is supposed to hold something like "go version go1.23.1 linux/amd64". ldflags needs to be quoted: -ldflags="-X ... -X ..." Quoting the ${GO_VERSION} breaks the ldflag quoting. No matter what I tried, how I espaced the double quotes inside the double quotes, I get an error as soon as GO_VERSION contains spaces. I.e. setting GO_VERSION to "1.2.3" works, but it fails with "go version go1.23.1 linux/amd64". Searching for rpm spec and quoting did not bring up anything, so I am out of ideas. Maybe someone has an idea. Kind Regards, Johannes P.S.: Currently the package builds as GO_VERSION is set to something without spaces: > GO_VERSION="$(go version| awk '{print $3}')"

2 4

Building a package using busybox-coreutils or coreutils-single
by Johannes Kastl 16 Sep '24

16 Sep '24

Hi all, for packaging lix I apparently need the coreutils binary. So I tried adding coreutils-single to the BuildRequires, as this contains the binary. But then the builds are unresolvable, as lots of other packages depend on coreutils, and the both of them conflict. Not sure why the "single" package does not just contain the additional binary and does not conflict, but there may be a reason. How do I solve this without having to resort to crude prjconf hacks? The packages that depend on coreutils are: rpm-build systemd-rpm-macros debugedit linux-glibc-devel I also tried if busybox-coreutils might solve this, but the problem is the same, as this also conflicts with coreutils... Kind Regards, Johannes

4 6

Devel project for espanso (Cross-platform Text Expander written in Rust)
by Johannes Kastl 15 Sep '24

15 Sep '24

Hi all, any recommendations on where to submit espanso to (once I tested it properly)? ################################################## Cross-platform Text Expander written in Rust https://github.com/espanso/espanso What is a Text Expander? A text expander is a program that detects when you type a specific keyword and replaces it with something else. This is useful in many ways: Save a lot of typing, expanding common sentences. Create system-wide code snippets. Execute custom scripts Use emojis like a pro. ################################################## Kind Regards, Johannes

2 2

libcap for Hercules (available via zypper, but unresolvable for Tumbleweed)
by Sarah Julia Kriesch 10 Sep '24

10 Sep '24

Hello together, I want to update the Hercules emulator. If I do not include libcap as a package, I will receive this error message: [ 174s] (cd /home/abuild/rpmbuild/BUILDROOT/hercules-4.7-39.1.x86_64/usr/bin; ln -s ./dasdcopy64 cckd642ckd) [ 174s] (cd /home/abuild/rpmbuild/BUILDROOT/hercules-4.7-39.1.x86_64/usr/bin; setcap 'cap_sys_nice=eip' ./hercules) [ 174s] /usr/bin/bash: line 1: setcap: command not found (https://build.opensuse.org/package/show/home:AdaLovelace:branches:Emulators…) I used zypper on my x86 Tumbleweed system and it can find libcap and libcap2. Our package search can find also an official release for Tumbleweed: https://software.opensuse.org/package/libcap Anyways OBS is showing "unresolvable" for Tumbleweed, that it can not find libcap. What do I do wrong with the BuildRequires based on both libcap or libcap2? Thank you! Best regards, Sarah

2 1

Language packages are being built differently for Leap and Tumbleweed
by Heitor Moreira 27 Aug '24

27 Aug '24

While investigating why some language packages are not being automatically installed, I noticed that the language packages are being built differently for Leap and Tumbleweed. Taking as an example the qemu package, besides the version, the *spec file* is the same for Leap and Tumbleweed. However, the package built for Leap 15.6 doesn't contain the locale information in the *provides* section. Why the difference? Tumbleweed: > rpm -qp --provides qemu-lang-9.0.2-1.2.x86_64.rpm locale(qemu:bg) locale(qemu:de_DE) locale(qemu:fr_FR) locale(qemu:hu) locale(qemu:it) locale(qemu:sv) locale(qemu:tr) locale(qemu:uk) locale(qemu:zh_CN) qemu-lang = 9.0.2-1.2 qemu-lang(x86-64) = 9.0.2-1.2 Leap 15.6: > rpm -qp --provides qemu-lang-8.2.2-150600.1.8.x86_64.rpm qemu-lang = 8.2.2-150600.1.8 qemu-lang(x86-64) = 8.2.2-150600.1.8 Best regards, Heitor Moreira

2 2

Packaging espanso: How to supply compile flags (like "-I/usr/include/libxkbcommon") to the cargo build command?
by Johannes Kastl 18 Aug '24

18 Aug '24

Hi all, I came across espanso, a "cross-platform Text Expander written in Rust", and wanted to package it. I saw that there were some packages built for an older version, started by rickyk. I reworked the package, updated it to the current version and the current cargo packaging guidelines. And then ran into the same issue others also had on openSUSE: Specifying a different include location for xkbcommon. https://github.com/espanso/espanso/issues/995 I tried various ways to supply the compiler flag "-I/usr/include/libxkbcommon", but somehow none worked. I tried: %define __rustflags -Clink-arg=-I/usr/include/libxkbcommon export CXXFLAGS+="-I/usr/include/libxkbcommon" export OPTFLAGS+="-I/usr/include/libxkbcommon" export OPTFLAGS="%{optsflags} -I/usr/include/libxkbcommon" But this does not seem to be respected. How would I do this properly? Kind Regards, Johannes

2 2

lix not finding the pegtl dependency
by Johannes Kastl 17 Aug '24

17 Aug '24

Hi all, I am trying to package lix (https://lix.systems/) I managed to find almost all dependencies, I had to build some myself. Now I am stuck where I install the pegtl-devel package, but this dependency is not found during the "meson setup build". > [ 15s] + meson setup build --prefix=/home/abuild/rpmbuild/BUILD/lix-2.91.0/outputs/out > [ 16s] The Meson build system > [ 16s] Version: 1.5.1 > [ 16s] Source dir: /home/abuild/rpmbuild/BUILD/lix-2.91.0 > [ 16s] Build dir: /home/abuild/rpmbuild/BUILD/lix-2.91.0/build > [ 16s] Build type: native build > [ 16s] Project name: lix > [ 16s] Project version: > [ 16s] C++ compiler for the host machine: c++ (gcc 13.3.1 "c++ (SUSE Linux) 13.3.1 20240807 [revision 9d368828bd4d04ce507e02a581be850fca849fae]") > [ 16s] C++ linker for the host machine: c++ ld.bfd 2.42.0.20240130-4 > [ 16s] Host machine cpu family: x86_64 > [ 16s] Host machine cpu: x86_64 > [ 16s] Program doxygen found: YES (/usr/bin/doxygen) > [ 16s] Program bash found: YES (/usr/bin/bash) > [ 16s] Found pkg-config: YES (/usr/bin/pkg-config) 2.2.0 > [ 16s] Run-time dependency rapidcheck found: YES > [ 16s] Message: canonical Nix system name: x86_64-linux > [ 16s] Found CMake: /usr/bin/cmake (3.30.2) > [ 16s] Run-time dependency bdw-gc found: NO (tried pkgconfig and cmake) > [ 16s] Run-time dependency Boost (found: container) found: YES 1.85.0 (/usr) > [ 16s] Run-time dependency libcpuid found: YES 0.6.5 > [ 16s] Run-time dependency libseccomp found: YES 2.5.5 > [ 16s] Run-time dependency libarchive found: YES 3.7.4 > [ 16s] Run-time dependency libbrotlicommon found: YES 1.1.0 > [ 16s] Run-time dependency libbrotlidec found: YES 1.1.0 > [ 16s] Run-time dependency libbrotlienc found: YES 1.1.0 > [ 16s] Run-time dependency libcrypto found: YES 3.1.4 > [ 16s] Run-time dependency aws-cpp-sdk-core found: YES 1.11.382 > [ 16s] Run-time dependency aws-cpp-sdk-transfer found: YES 1.11.382 > [ 16s] Run-time dependency aws-cpp-sdk-s3 found: YES 1.11.382 > [ 16s] Run-time dependency sqlite3 found: YES 3.46.0 > [ 16s] Run-time dependency libsodium found: YES 1.0.20 > [ 16s] Run-time dependency libcurl found: YES 8.9.0 > [ 16s] Run-time dependency libeditline found: YES 1.17.1 > [ 16s] Run-time dependency lowdown found: YES 1.1.0 > [ 16s] Dependency rapidcheck found: YES unknown (cached) > [ 16s] Run-time dependency GTest found: YES 1.14.0 > [ 16s] Run-time dependency gtest_main found: YES 1.14.0 > [ 16s] Run-time dependency GMock found: YES 1.14.0 > [ 16s] Run-time dependency gmock_main found: YES 1.14.0 > [ 16s] Run-time dependency toml11 found: YES 3.7.1 > [ 16s] Run-time dependency pegtl found: NO (tried cmake) > [ 16s] > [ 16s] meson.build:314:8: ERROR: Dependency "pegtl" not found, tried cmake > [ 16s] As the package originates in the Nix ecosystem, my guess it that it looks in the wrong place due to different packaging. Is there any way I can tell meson (or the underlying cmake) where it can find this dependency? The dependency is defined in line 314 and contains "taocpp::pegtl". > https://git.lix.systems/lix-project/lix/src/branch/main/meson.build The package puts the files into "tao/pegtl" (without the "cpp"), not sure if that is the reason it is not found? Here is the link to my package: > https://build.opensuse.org/package/show/home:ojkastl_buildservice:Branch_de… (Currently unresolvable due to me trying to package aws-sdk-cpp as I missed that it is already available in Cloud:Tools...). Thanks in advance! Kind Regards, Johannes

1 1