April 2024 - openSUSE Packaging - openSUSE Mailing Lists

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

python311-kombu blocked by missing python311-boto3 in devel:languages:python
by Keil 04 Apr '24

04 Apr '24

Hi, currently python311-kombu does not build in the devel project because it misses python311-boto3, which is only built for plain python3. This makes python311-celery in turn uninstallable in 15.5 or 15.6 as this directly translates to devel:languages:python or :backports respectively. All build fine in Factory. I'm happy to raise this anywhere else, it just wasn't obvious to me where this fits best. Best regards, Christian

5 13

Packaging entry-point only Python packages
by Matthias Bach 02 Apr '24

02 Apr '24

Hi, Upstream Typer [1] has recently split up their package into the following: * typer-slim providing the core functionality * typer-cli providing the entry point for the optional typer command, and * typer which pulls in the other two and all optional dependencies. Trying to adjust the openSUSE package, I have into the following error being reported from rpmlint: python310-typer-cli.noarch: E: no-dependency-on python-base 3.10 python311-typer-cli.noarch: E: no-dependency-on python-base 3.11 python312-typer-cli.noarch: E: no-dependency-on python-base 3.12 This package only consists of an entry point. Thus, there is no module installed, only "binaries". These are versioned and there is a dependency on the corresponding Python's version of typer-slim. However, it seems as there are not modules installed the dependency on "python(abi)" is not generated. I found in some older threads the suggestion to add "%py_requires". But that macro no longer seems to exist. Is there any recommended way to approach this? I can of course just override the error via rpmlintrc. But I suspect that's not the proper solution to the issue and probably won't work for pushing into Factory. Kind Regards, Matthias -- Dr. Matthias Bach www.marix.org „Der einzige Weg, die Grenzen des Möglichen zu finden, ist ein klein wenig über diese hinaus in das Unmögliche vorzustoßen.“ - Arthur C. Clarke

4 6