- openSUSE Packaging

watchdog and ufw
by Jonas Kvinge 14 May '24

14 May '24

Hi Is it possible to submit these packages to factory? https://build.opensuse.org/package/show/Base:System/watchdog https://build.opensuse.org/package/show/security/ufw Jonas

2 1

Unresolvable due to "nothing provides perl(:MODULE_COMPAT_5.28.1) needed by git-core": Where have I found the answer to this one?
by Johannes Kastl 13 May '24

13 May '24

Hi all, please help me refresh my memory: Where have I seen the solution to the following error: > nothing provides perl(:MODULE_COMPAT_5.28.1) needed by git-core Happens here: > https://build.opensuse.org/package/show/home:ojkastl_buildservice/git-lfs > https://build.opensuse.org/package/show/home:ojkastl_buildservice:distrobox… I encountered this some time (years?) ago and found a solution, I think using prjconf. But I cannot for the life of me remember or find it again. Any hints for easing my troubled mind are highly welcome... Kind Regards, Johannes

1 1

u-boot with TPM
by Jonas Kvinge 08 May '24

08 May '24

Hi, I need a u-boot package for Raspberry Pi 4 with TPM / Soft SPI configuration as shown here: https://github.com/joholl/rpi4-uboot-tpm/blob/ad31306ce2f2d52f0572385bfc8ba… Otherwise, tpm2_pcrread shows blank PCR values. Would it be possible to enable this for the current u-boot-rpi4 package, or can we package a separate package with a name such as "u- boot-rpi4-tpm" which has this specific configuration? I have a fork here which already does it: https://build.opensuse.org/package/show/home:jonaski:vendanor/u-boot And how do I solve this? "unresolvable: nothing provides %prjconf_multibuild_selection" without removing "BuildRequires: %prjconf_multibuild_selection". Jonas

2 2

Using update-alternatives in baselibs.conf post scriptlets
by Atri Bhattacharya 04 May '24

04 May '24

Hi, Could someone kindly explain how one gets update-alternatives to work correctly with baselibs.conf generated packages? The only documentation I have seen [1] is rather sparse and does not go into this specific issue involving running update-alternatives as post(in/un) in baselibs.conf itself. I am trying to take care of the apparently incorrect packaging of *-32bit biarch libraries for lapack, which currently have 0-byte files instead of the intended update-alternatives symlinks. More details in this bug report [2]. My ongoing efforts to resolve this may be seen in my branch project [3]. I have tried to run update-alternatives in the baselibs.conf file itself or even simply running `ln -sf` to create a symlink target to the actual location of the library. None of these work, always ending up with a 0-byte file in place of the intended symlink. This looks to be the case also for some other packages, say, ocl-icd [4] which also uses update-alternatives in its post-scripts and whose -32bit packages also end up with 0-byte files. Consider the difference: sh-5.2$ rpm -qvlp libOpenCL1-32bit-2.3.1-51.14.x86_64.rpm -rw-r--r-- 1 root root 0 Feb 20 03:54 /usr/lib/libOpenCL.so.1 drwxr-xr-x 2 root root 0 Feb 20 03:54 /usr/lib/ocl-icd lrwxrwxrwx 1 root root 18 Feb 20 03:54 /usr/lib/ocl-icd/libOpenCL.so.1 -> libOpenCL.so.1.0.0 -rwxr-xr-x 1 root root 215264 Feb 20 03:54 /usr/lib/ocl-icd/libOpenCL.so.1.0.0 sh-5.2$ rpm -qvlp libOpenCL1-2.3.1-51.14.x86_64.rpm lrwxrwxrwx 1 root root 38 Feb 20 03:57 /etc/alternatives/libOpenCL.so.1 -> ../../usr/lib64/ocl-icd/libOpenCL.so.1 lrwxrwxrwx 1 root root 32 Feb 20 03:57 /usr/lib64/libOpenCL.so.1 -> /etc/alternatives/libOpenCL.so.1 drwxr-xr-x 2 root root 0 Feb 20 03:57 /usr/lib64/ocl-icd lrwxrwxrwx 1 root root 18 Feb 20 03:57 /usr/lib64/ocl-icd/libOpenCL.so.1 -> libOpenCL.so.1.0.0 -rwxr-xr-x 1 root root 192144 Feb 20 03:57 /usr/lib64/ocl-icd/libOpenCL.so.1.0.0 drwxr-xr-x 2 root root 0 Feb 20 03:57 /usr/share/doc/packages/libOpenCL1 -rw-r--r-- 1 root root 1387 Aug 17 2021 /usr/share/doc/packages/libOpenCL1/README Any pointers on how to get the symlinks right for biarch packages would be greatly appreciated. [1] <https://en.opensuse.org/openSUSE:Build_Service_baselibs.conf> [2] <https://bugzilla.opensuse.org/show_bug.cgi?id=1207563> [3] <https://build.opensuse.org/package/show/home:badshah400:lapack2023/lapack> [4] <https://build.opensuse.org/package/show/openSUSE:Factory/ocl-icd> Thanks in advance, -- Atri

1 1

Ignoring an error during %{cargo_test} (or: how to get youki tests to not error out because of missing dbus)?
by Johannes Kastl 19 Apr '24

19 Apr '24

Hi all, I stumbled upon youki today and thought I'' sharpen my rust packaging skills. Voilá! > https://build.opensuse.org/package/show/home:ojkastl_buildservice:Branch_Vi… However, the package only builds fine because I disabled the %checks due to three errors (details see below). Is there a way to ignore some checks when running %{cargo_test}? Maybe like "%pytest -k (not some-test)" or similar? Or does anyone know how to fix the error below, that seems to be from a missing/failing/broken dbus connection inside the build vm? Have a nice weekend, everyone! Kind Regards, Johannes P.S.: Here are the errors: > [ 830s] > [ 830s] failures: > [ 830s] > [ 830s] ---- systemd::dbus_native::dbus::tests::test_dbus_function_calls stdout ---- > [ 830s] Error: DBus(ConnectionError("ENOENT: No such file or directory")) > [ 830s] > [ 830s] ---- systemd::dbus_native::dbus::tests::test_dbus_connection_auth stdout ---- > [ 830s] thread 'systemd::dbus_native::dbus::tests::test_dbus_connection_auth' panicked at crates/libcgroups/src/systemd/dbus_native/dbus.rs:475:9: > [ 830s] assertion failed: conn.is_ok() > [ 830s] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace > [ 830s] > [ 830s] ---- systemd::dbus_native::dbus::tests::test_dbus_function_calls_errors stdout ---- > [ 830s] thread 'systemd::dbus_native::dbus::tests::test_dbus_function_calls_errors' panicked at crates/libcgroups/src/systemd/dbus_native/dbus.rs:528:69: > [ 830s] called `Result::unwrap()` on an `Err` value: DBus(ConnectionError("ENOENT: No such file or directory")) > [ 830s] > [ 830s] > [ 830s] failures: > [ 830s] systemd::dbus_native::dbus::tests::test_dbus_connection_auth > [ 830s] systemd::dbus_native::dbus::tests::test_dbus_function_calls > [ 830s] systemd::dbus_native::dbus::tests::test_dbus_function_calls_errors > [ 830s] > [ 830s] test result: FAILED. 134 passed; 3 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.55s

1 0

Right location for archful shared libraried
by Mzz 18 Apr '24

18 Apr '24

Hi, I'm currently trying to package https://gitlab.freedesktop.org/monado/utilities/vulkan-layers for OpenSUSE Tumbleweed(x86_64), the package provides two files VkLayer_MND_enable_timeline_semaphore.json and libVkLayer_MND_enable_timeline_semaphore.so, the shared Library is 64-bit, having the library in /usr/lib64 causes issues in some games(can give more details in necessary) and i was able to fix said issues by moving the library to /usr/lib, I was wandering if this should be avoided or not. Kind regards -Etch

2 1

Use other nodejs verson as defined via npm-default
by Johannes Weberhofer 17 Apr '24

17 Apr '24

Dear all! I'm trying to build a nodejs app https://build.opensuse.org/package/show/devel:kubic/traefik that's UI is build on the OBS using the "local-npm-registry". This pulls "npm-default" which is version 21 on Tumbleweed. Unfortunately the package can be built only with sable versions 16, 18, 20 but not with the (current) default 21 version. Is there a way to configure the spec file to install and use npm20 instead of npm21? Best regards, Johannes

1 0

Re: Your confirmation is needed to leave the packaging@lists.opensuse.org mailing list.
by Jan Ritzerfeld 14 Apr '24

14 Apr '24

Am Samstag, 13. April 2024, 23:49:09 CEST schrieb packaging- confirm+b278fed55e115ce794ecbbef480d3a673acea6e0(a)lists.opensuse.org: > Email Address Unsubscription Confirmation > > Hello, this is the GNU Mailman server at lists.opensuse.org. > > We have received an unsubscription request for the email address > > suse(a)mailinglists.jan.ritzerfeld.org > > Before GNU Mailman can unsubscribe you, you must first confirm your request. > You can do this by simply replying to this message. > > Or you should include the following line -- and only the following > line -- in a message to packaging-request(a)lists.opensuse.org: > > confirm b278fed55e115ce794ecbbef480d3a673acea6e0 > > Note that simply sending a `reply' to this message should work from > most mail readers. > > If you do not wish to unsubscribe this email address, simply disregard this > message. If you think you are being maliciously unsubscribed from the list, > or have any other questions, you may contact > > packaging-owner(a)lists.opensuse.org

1 1

Packages owning configuration files and configuration file samples: Current best practices?
by Johannes Kastl 13 Apr '24

13 Apr '24

Hi all, while working on Hashicorp Vault and OpenBao packages (stay tuned, mail to Factory will come soon) I stumbled upon something I did not have to do for quite a while. Hence my question what the current practice is on that. 1. How should I handle files in /etc/openbao that should "belong" to the package, but should not be packaged at all (the admin needs to create that herself)? Not having the file in the package means that querying RPM will not yield which package this file belongs to. Of course, the directory name might give a hint, but I would like to have rpm answer that question properly. My most educated guess whould be to %ghost those files. Not sure if that is the right way]tm]. :-) 2. How to treat example configuration files? Files that are not used and thus can be safely overwritten by package upgrades. My first idea was to put them into /etc/openbao, with e.g. a sample suffix. But packages should[tm] no longer write to /etc/, AFAIK. So it would be better to put them into /usr/share/doc/packages/openbao? Which also allows to safeley overwrite them on package upgrades. Would be great to get some recommendations! Thanks in advance! Kind Regards, Johannes

6 14

Build problem with multi spec
by Eric Schirra 12 Apr '24

12 Apr '24

Hello everyone, I have a problem and acceptance with a request for factory. I want to build a package which builds an application with different versions for Leap and Tumbleweed. First attempt was to query in spec what is built and then set the version number dynamically. Worked in the home and devel repo. But was then rejected by factory. Second try was with 3 spec and change files for Leap 15.5, 15.6 and for Tumblweed. Also worked in home and devel repo. But again factory rejects it. Factory says it has no change file. But it actually has three! What should or can I do now to have a package that builds once for Leap in version A and for Tumbleweed in version X? Regards Eric

2 2