April 2023 - openSUSE Build Service - openSUSE Mailing Lists

Building RT-Kernel Module packages for Leap 15.4
by Florian Pose 13 Apr '23

13 Apr '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 8

Mingw buiilds now failing
by Roger Oberholtzer 11 Apr '23

11 Apr '23

I build a couple of Mingw packages on OBS. I now get build failures in most of them. The error is generally like this: [ 49s] Processing files: mingw64-tktable-debug-2.10-2.1.noarch [ 49s] error: Could not open %files file /home/abuild/rpmbuild/BUILD/mingw64-debugfiles.list: No such file or directory I looked at a couple Mingw packages that are not failing, and I see that they seem to no longer use: %{_mingw64_debug_package} So I thought I would remove those. But it seems to make no difference. Here is a sample project that no longer builds on OBS: https://build.opensuse.org/package/show/home:rogeroberholtzer:mingw64/mingw… Anyone have a clue what might be happening? -- Roger Oberholtzer

2 3

Re: Heads-up: Removal of python38-* packages
by Ben Greiner 07 Apr '23

07 Apr '23

Hi, Am 04.04.23 um 13:05 schrieb Dominique Leuenberger: > Dear Tumbleweed users and hackers, > > > openSUSE:Factory has just been reconfigured to no longer consider > python38 when using the python single_spec macros (as most python-* > packages do); those packages will be cleaned up as part of snapshot > 0404. This change has not propagated to the devel projects yet. Look at all the unresolvables in devel:languages:python* https://build.opensuse.org/projects/openSUSE:Factory/prjconf has ExpandFlags: macroserial:20230404 so there must be a regression in the build service - Ben

1 0

OBS Request Page Redesign - Two More Action Types and Better Comments on Changes
by Jacob Michalskie 04 Apr '23

04 Apr '23

Hi, In the latest round of changes, the request page in OBS gained ability to handle two new request action types and got its comments on changes feature improved in a few major ways. Find out what exactly changed in the latest blog post: https://openbuildservice.org/2023/04/04/request-workflow-redesign/

1 0

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

03 Apr '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

4 6