August 2024 - openSUSE Packaging - openSUSE Mailing Lists

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

13 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 5

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

Re: Fwd: Build failure of devel:languages:python/python-Werkzeug in 15.6/x86_64
by Axel Braun 14 Aug '24

14 Aug '24

Hi Dirk, Am Mittwoch, 14. August 2024, 16:39:28 MESZ schrieben Sie: > > Am Di., 13. Aug. 2024 um 23:48 Uhr schrieb Matěj Cepl <mcepl(a)cepl.eu>: > > > > I'm getting suddenly Tons of build failures like the attached one. > > > Any changes in the build System? > > This is fallout of the python-pip update that we're trying to get > working for a while. if you need > working packages for 15.6 please use devel:languages:python:backports > not devel:languages:python. Well, I need it as prerequisite for some packages, but for whatver reason I get the build fail notifications... Cheers Axel

1 0

Fwd: Re: Fwd: Build failure of devel:languages:python/python-Werkzeug in 15.6/x86_64
by Axel Braun 14 Aug '24

14 Aug '24

Hi, Originally from the python list, Lots of build failures suddenly. Any changes in the setup for 15.6? Schöne Grüße Axel -- Written from cell phone - excuses for typos -------- Ursprüngliche Nachricht -------- Von: "Matěj Cepl" <mcepl(a)cepl.eu> Gesendet: 14. August 2024 00:47:55 OESZ An: Axel Braun <Axel.braun(a)gmx.de>, python(a)lists.opensuse.org Betreff: Re: Fwd: Build failure of devel:languages:python/python-Werkzeug in 15.6/x86_64 On Tue Aug 13, 2024 at 1:11 PM CEST, Axel Braun wrote: > I'm getting suddenly Tons of build failures like the attached one. > Any changes in the build System? It looks to me like something’s wrong with OBS. Matěj -- http://matej.ceplovi.cz/blog/, @mcepl@floss.social GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 When you’re happy that cut and paste actually works I think it’s a sign you’ve been using X-Windows for too long. -- from /. discussion on poor integration between KDE and GNOME

4 8

Questions about Intel Packages
by compellingbytes＠protonmail.com 03 Aug '24

03 Aug '24

Hi, I'm working on a youtube video about which Intel packages to install on Ubuntu, Debian, and potentially openSUSE to be able to use an Intel Arc/Xe Core APU for compute functions. I had some questions about the structure and choices of these packages, since I noticed some differences between how things are done for Debian/Ubuntu, and other things. If this isn't the best place to ask these questions, please direct me to the right mailing list or forum. First Question: On Ubuntu, Libmfx-gen1.2 is the only package needed for oneVPL-intel-gpu, while on openSUSE Tumbleweed, you need libmfx-gen and libmfx-gen_2 for seemingly the same functionality? Libmfx-gen is 6.6KiB while libmfx-gen1_2 is 8.4MiB, could someone explain why there's a size discrepancy, and what the function of the two packages are? Second Question: I noticed that libvp2 is being built based on oneVPL 2.10.1-2.2, while 2.10.1 was released in December 2023. 2.10.1 was released in December 2023, and that's the only 2.10.1 I see available on github. Are versions like 2.10.1-2.2 created by the openSUSE maintainers with adjustments for openSUSE or... where do they come from? Sub question The latest version is 2.11.0, and I'm wondering if there's an issue as far as it not being the version available for openSUSE Tumbleweed users? Are the intel packages not a priority, especially since there's uncertainty about Intel's gpu future? 3rd question I've tried running the OpenVINO implementation of Stable Diffusion WebUI, and all of the packages needed seem to be available on the openSUSE repo, but script doesn't complete. Would you know if this is because there are at least some packages that are behind the latest of what Intel has made available version wise, or is it an issue with the parameters being passed during compilation by the openSUSE maintainers. I'd really appreciate it if I could get some answers so that I can report a straight story to my audience because I'd really like for Tumbleweed (at least) to be a platform (I'm a Tumbleweed user) that people could utilize Intel Arc/Xe cores on for compute/productivity/AI tasks, instead of having to dual boot into Ubuntu. I hope it doesn't seem that I'm just trying to stick my nose into your business for my own gain; I'd genuinely like to help more people be able to use openSUSE (Tumbleweed) for as many things as possible. Thanks!

4 5

Project for Garage (S3-compatible storage)
by Johannes Kastl 01 Aug '24

01 Aug '24

Hi all, I found Garage recently and tried to package it. Looks good, needs some finetuning and testing. https://git.deuxfleurs.fr/Deuxfleurs/garage/ "S3-compatible object store for small self-hosted geo-distributed deployments" Garage is a S3-compatible storage like MinIO. What would be a good devel project for it? There is no server:storage or similar. Kind Regards Johannes

6 15