openSUSE Build Service March 2023

buildservice@lists.opensuse.org

29 participants
25 discussions

Could NOT find Wayland (missing: WAYLAND_CLIENT_INCLUDE_DIR) - Cmake error
by ahmed moselhi 31 Mar '23

31 Mar '23

Hi , I'm trying to build pcsx2 on obs but i encounter this error while building [ 49s] CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message): [ 49s] Could NOT find Wayland (missing: WAYLAND_CLIENT_INCLUDE_DIR [ 49s] WAYLAND_SERVER_INCLUDE_DIR WAYLAND_EGL_INCLUDE_DIR [ 49s] WAYLAND_CURSOR_INCLUDE_DIR) [ 49s] Call Stack (most recent call first): [ 49s] /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE) [ 49s] cmake/FindWayland.cmake:37 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) [ 49s] cmake/SearchForStuff.cmake:87 (find_package) [ 49s] CMakeLists.txt:42 (include) [ 49s] [ 49s] [ 49s] -- Configuring incomplete, errors occurred! I tried to build against tumbleweed , leap 15.4 and 15.5 same error each time my spec file is here : https://build.opensuse.org/package/view_file/home:ahmedmoselhi2:branches:Em…

2 1

%ifarch fails to properly detect armv7l builds on OBS?
by Johannes Kastl 31 Mar '23

31 Mar '23

Good morning/evening/afternoon/night, I am currently trying to package python-libtmux, that has different errors in the %checks on different architectures. I figured out which checks fail on which architecture and wrapped them in separate %ifarch sections: > # Failing tests on armv7l > # https://github.com/tmux-python/libtmux/issues/479 > %ifarch armv7l > %pytest -k 'not ( \ > test_capture_pane \ > or test_function_times_out \ > or test_function_times_out_no_rise \ > or test_new_window_with_environment[environment0] \ > or test_new_window_with_environment[environment1] \ > or test_select_window \ > )' > %endif However, the armv7l section is never used when building for "openSUSE Tumbleweed armv7l". The build log shows many different things regarding the architecture: > [ 0s] Using BUILD_ARCH=armv7l:armv6l:armv5tel > [ 0s] Building python-libtmux for project 'home:ojkastl_buildservice:libtmux_bugreports' repository 'openSUSE_Tumbleweed' arch 'armv7l' srcmd5 'def7c83c25c69087de1ed1cde6ee11e4' > [ 11s] 2nd stage started in virtual machine > [ 11s] machine type: aarch64 > [ 11s] 2nd stage started in virtual machine > [ 11s] machine type: armv8l > [ 18s] build target is armv7hl-suse-linux > [ 18s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature --target=armv7hl-suse-linux --undefine _enable_debug_packages --define 'disturl obs://build.opensuse.org/home:ojkastl_buildservice:libtmux_bugreports/openS…' /home/abuild/rpmbuild/SOURCES/python-libtmux.spec > [ 20s] Building target platforms: armv7hl-suse-linux > [ 20s] Building for target armv7hl-suse-linux But in the end it falls back to the default: > [ 30s] + echo 'DEBUGGING BUILDARCH is NOT aarch64 aarch64_ilp32 armv8l aarch64:aarch64_ilp32:armv8l ppc64:ppc ppc64 ppc ppc64le armv7l armv6l armv5tel armv7l:armv6l:armv5tel' > [ 30s] DEBUGGING BUILDARCH is NOT aarch64 aarch64_ilp32 armv8l aarch64:aarch64_ilp32:armv8l ppc64:ppc ppc64 ppc ppc64le armv7l armv6l armv5tel armv7l:armv6l:armv5tel > [ 30s] + uname -a > [ 30s] Linux obs-arm-10 6.1.7-1-default #1 SMP PREEMPT_DYNAMIC Wed Jan 18 11:12:34 UTC 2023 (872045c) armv7l armv7l armv7l GNU/Linux > [ 30s] + IGNORED_TESTS='not (test_capture_pane_start or test_function_times_out_no_rise or test_function_times_out_no_raise_assert)' I already tried to add things like armv6l armv5tel armv7l:armv6l:armv5tel to the %ifarch, but that did not help. What have I missed? Is this due to some cross-compilation used in OBS? How to properly detect armv7l? The package in question is (currently containing lots of debugging code not yet cleaned up): > https://build.opensuse.org/package/show/home:ojkastl_buildservice:libtmux_b… Kind Regards, Johannes Side note: I used several separate %ifarch conditions followed by a %ifnarch mentioning all of the architectures used before in the %ifarch conditions. I have not found any trace of %elsearch or %elifarch or anything like that, i.e. some kind of if-elseif-else-statement or case-like statement. If there is such a thing, please point me at it, I would like to make this more readable... :-) -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

2 1

A lib ist not a lib
by Detlef Steuer 29 Mar '23

29 Mar '23

Hi! A package devel:languages:R:autoCRAN/R-mimi building locally is not build on OBS because: [ 40s] R-mimi.x86_64: E: explicit-lib-dependency R-bslib [ 40s] R-mimi.x86_64: E: explicit-lib-dependency R-jquerylib [ 40s] You must let rpm find the library dependencies by itself. Do not put unneeded [ 40s] explicit Requires: tags. But: R-bslib and R-jquerylib aren't ordinary libs. Both are just other R packages also build in autoCRAN. Is it possible to override this error or can this even be seen as a bug in OBS, because there is just "*lib" in the names, but no libs in the usual sense are in there? Regards Detlef -- "Wozu leben wir, wenn nicht dazu, uns gegenseitig das Leben einfacher zu machen. (George Eliot)" Dr. Detlef Steuer Helmut-Schmidt-Universität Fakultät WiSo Holstenhofweg 85 22043 Hamburg Tel: 040/6541-2819 mail: steuer(a)hsu-hh.de

4 5

package signing
by Ivan Ekimov 29 Mar '23

29 Mar '23

Hello, I'm using a local obs server and got a problem with package signing. I tried this guideline https://en.opensuse.org/openSUSE:Build_Service_Signer, but it's outdated and after a few workarounds like coping files from ~/.gnupg/* to /srv/obs/gnupg/ got this message [11882] signer exiting... [12254] signer started waiting for an event... signing x86_64/*** 127.0.0.1: Connection refused sign failed: 256 - checking digest /srv/obs/jobs/x86_64/***.src.rpm: digests OK sign failed: sign /srv/obs/jobs/x86_64/***src.rpm failed sign -k returning key perfectly also, I tried to use obs_admin --update-project-signing-key project ./key.pgp.pub ./_signkey and got error no secret key BR, Ivan

3 3

Debian:11 project security repository
by Nicholas Brown 27 Mar '23

27 Mar '23

Look at the meta for the `Debian:11` project (https://build.opensuse.org/project/show/Debian:11) I notice that this uses the following 3 sources: <repository name="standard"> <download arch="x86_64" url="http://ftp.de.debian.org/debian/bullseye/main" repotype="deb"> <repository name="update"> <download arch="x86_64" url="http://ftp.de.debian.org/debian/bullseye-updates/main" repotype="deb"> <repository name="backports"> <download arch="x86_64" url="http://ftp.de.debian.org/debian/bullseye-backports/main" repotype="deb"> I wonder if should also include the upstream debian `security` source? This will contain security fixes that are neither in update or standard (until the next point release of standard) `deb http://deb.debian.org/debian-security/ bullseye-security main` See: https://wiki.debian.org/SourcesList for full details of debian standard/update/security sources.

1 0

Building RT-Kernel Module packages for Leap 15.4
by Florian Pose 27 Mar '23

27 Mar '23

Hello, I maintain the science:EtherLab project [1] and we are building packages containing kernel-modules for the EtherCAT master project [2] based on the distribution kernels (using %{kernel_module_package_buildreqs}, %{flavors_to_build} and friends). We have a problem with the openSUSE Leap 15.4 repository: The module ethercat-kmp-rt is built correctly, but for kernel 5.3.18 (the version from the main repo). On a freshly installed Leap 15.4 system there is a repository called "Update repository with updates from SUSE Linux Enterprise 15" [3], that comes with a newer kernel-rt (5.14.21), so if users update the system, they get a newer RT kernel, but no updated EtherCAT modules for the installed kernel. Which repository do I have to add to the OBS project? I tried - SUSE:SLE-15:Update/pool-leap-15.4 - SUSE:SLE-15:Update/standard without luck. Where do I find this information for future distributions? [1] https://build.opensuse.org/project/show/science:EtherLab [2] https://build.opensuse.org/package/show/science:EtherLab/ethercat [3] http://download.opensuse.org/update/leap/15.4/sle

3 6

Add Ubuntu 23.04 to openSUSE Build Service?
by Wong Hoi Sing Edison 24 Mar '23

24 Mar '23

Hi Everyone, Ubuntu 23.04 is now currently pre-Beta, Beta scheduled on 2023-03-30, and final release scheduled on 2023-04-20: * https://discourse.ubuntu.com/t/lunar-lobster-release-schedule/27284 * https://wiki.ubuntu.com/Releases#Future * https://cdimage.ubuntu.com/daily-live/current/ Could we start getting it added to OBS now? Regards, Edison Wong

2 2

Unable to edit user account.
by Larma Doive 24 Mar '23

24 Mar '23

1 0

How to divide the obs server into three servers
by liuxueping.snow＠bytedance.com 24 Mar '23

24 Mar '23

I want to divide obs server into api server, source server and repo server, what should I do? Or is there an instruction manual?

1 0

How to add a new project under specific namespace?
by Kentaro Hayashi 24 Mar '23

24 Mar '23

Hi, According to https://build.opensuse.org/project/new, When I want to create a new project outside of my home project, I need to contact via email, but, apparently, it will not work because it bounces email (noreply(a)opensuse.org). It seems that it is a known-issue since 2022. [1] https://github.com/openSUSE/open-build-service/issues/12356 Is there documented instruction on how to request a new project under existing specific namespace (such as server:mail) ? What I learned from the existing documentation, it should create a new project in my case, but I couldn't find official documentation to do it yet. I've tried to use obs under my home project [2] whether it satisfies our requirement in beforehand. Here are our requirements for milter-manager project: 1. maintain the package under the meaningful namespace * package itself may be maintained under the home project, but it is better to maintain under a more meaningful namespace because milter-manager is related to mail service. 2. publish multiple versions in the same repository * maintain the latest version only is not enough. * It may work by submitting multiple versioned package to server:mail namespace, but it causes namespace polutions with milter-manager-1.x.x, milter-manager-2.x.x and more. * To avoid such a situation, it should be server:mail:milter-manager project to group multiple versions under it's own project namespace. 3. want to publish not only openSUSE, but also other distributions * It requires configuring project meta information to do, so it can't be satisfied with submitting packages to server:mail. It need to own server:mail:milter-manager project namespace. To satisfy both of them, I want to create a new project. Correct me if I understand wrongly. Regards, [2] https://build.opensuse.org/project/show/home:kenhys

1 1

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service March 2023