July 2021 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Add external source to a package?
by Carsten Ziepke 12 Sep '23

12 Sep '23

Hello, I want to update the package ja2-stracciatella in the games repository to version 0.17.0. https://build.opensuse.org/package/show/home:Kieltux:branches:games/ja2-str… The new version needs the library string_theory which is not available for openSUSE. The build process wants to download string_theory from github, because it is not found. [ 36s] Scanning dependencies of target string_theory [ 36s] [ 12%] Creating directories for 'string_theory' [ 37s] [ 25%] Performing download step (download, verify and extract) for 'string_theory' [ 37s] -- Downloading... [ 37s] dst='/home/abuild/rpmbuild/BUILD/ja2-stracciatella-0.17.0/build/dependencies/lib-string_theory/builder/string_theory-prefix/src/3.1.tar.gz' [ 37s] timeout='none' [ 37s] -- Using src='https://github.com/zrax/string_theory/archive/3.1.tar.gz' [ 37s] -- Retrying... Can I add string_theory (string_theory-3.1.tar.gz) manually to the package and patch the build process? Thank you, Carsten -- Well, since MS cant be sure of the username of someone downloading things, they are going to play it safe and have everything dowloaded and executed by Explorer as suid root. That way, it will run on ANY system anywhere. :) -- George Bonser <grep(a)cris.com>

3 4

Implementing a new APT publisher
by Arnaud Ferraris 30 Mar '22

30 Mar '22

Hi, We currently use OBS for building and publishing APT packages for the Apertis project[1] (a Debian derivative distribution). At the moment we use downstream patches for the publisher (src/backend/bs_publish) in order to use reprepro instead of dpkg-scanpackages/dpkg-scansources. As we're considering implementing a new APT publisher based on aptly[2], we'd like to do so in a way that can be upstreamed to OBS so it can benefit the whole community. This obviously raises several questions as to how we should proceed, so I'm sending this email as a call for advice/comments/suggestions. We're considering the following: - this new publisher would be implemented in addition to the existing dpkg-scan* based one and be selectable through global configuration options. - using aptly opens up possibilities, but it isn't always as straightforward as a few system() call; we would therefore need to either ship a helper tool or add a new BSPublisher submodule (the latter is the preferred option atm) - aptly can also be used through a REST API, which implies some asynchronous processing would be preferrable. Is there currently a way to handle async processing in OBS, or would that require another helper tool/module, if possible at all? We're only at the planning and design stage for now, so we would be very interested in your opinion and comments regarding the above. Thanks, Arnaud [1] https://apertis.org [2] https://aptly.info

3 3

broken packages under certain circumstances
by Hans-Peter Jansen 18 Aug '21

18 Aug '21

Hi, I noticed some packages being in state "Files could not be expanded: could not apply patch 'project.diff'" for no apparent reasons. Happened for graphics/blender, and now I noticed: https://build.opensuse.org/package/show/network:ha-clustering:Factory/drbd For blender, I fixed _link and superfluous files manually. Any idea, what this is about? Best, Pete

4 6

x86_64 disk space errors
by Avindra G 11 Aug '21

11 Aug '21

I've been having trouble getting deno to build since v1.9.0 (April 13th, 2021) on x86_64. Tried various _constraints values, but the job is failing with the same error: [ 3311s] LLVM ERROR: IO failure on output stream: No space left on device [ 3311s] /.build/build-vm: line 460: echo: write error: No space left on device [ 3312s] error: could not compile `deno` [ 3312s] https://build.opensuse.org/package/show/devel:languages:javascript/deno#com… Can anyone advise? Thanks, avindra goolcharan

3 6

Adding "Everything" for openEuler 20.03
by Julio Gonzalez 08 Aug '21

08 Aug '21

Right now: https://build.opensuse.org/projects/openEuler:20.03/meta Has OS, updates (which in fact is disabled by default at least on 20.03-SP1), EPOL and EPOL-updates (are they broken? I see a red warning sign at https:// build.opensuse.org/project/show/openEuler:20.03) Question is: can the repository "Everything" be added as well? https://repo.openeuler.org/openEuler-20.03-LTS-SP1/everything/${arch}/ Most likely the same should be done for https://build.opensuse.org/project/show/openEuler:21.03 Thanks. -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

2 3

ARMv7 build has been broken in private OBS instance
by Matwey V. Kornilov 06 Aug '21

06 Aug '21

Hi, I am running a private OBS instance with an ARM worker based on Cortex-A53 board. obs-api-2.10.10-lp152.63.1.noarch Worker version is obs-worker-2.11~alpha.20210609T113256.127f886c97-12468.1.noarch Everything worked fine until today I found that the worker is broken. It cannot boot the KVM machine. I see the silence after: [ 32s] /usr/bin/qemu-system-aarch64 -nodefaults -no-reboot -nographic -vga none -cpu host,aarch64=off -enable-kvm -M virt,gic-version=host -object rng-random,filename=/dev/random,id=rng0 -device virtio-rng-device,rng=rng0 -runas qemu -net none -kernel /var/cache/obs/worker/root_1/.mount/boot/kernel -initrd /var/cache/obs/worker/root_1/.mount/boot/initrd -append root=/dev/disk/by-id/virtio-0 rootfstype=ext4 rootflags=noatime ext4.allow_unsupported=1 mitigations=off panic=1 quiet no-kvmclock elevator=noop nmi_watchdog=0 rw rd.driver.pre=binfmt_misc console=ttyAMA0 init=/.build/build -m 3072 -drive file=/var/cache/obs/worker/root_1/root,format=raw,if=none,id=disk,cache=unsafe -device virtio-blk-device,drive=disk,serial=0 -drive file=/var/cache/obs/worker/root_1/swap,format=raw,if=none,id=swap,cache=unsafe -device virtio-blk-device,drive=swap,serial=1 -serial stdio -chardev socket,id=monitor,server,nowait,path=/var/cache/obs/worker/root_1/root.qemu/monitor -mon chardev=monitor,mode=readline -smp 4 Then I've found that kernel and initrd images are for aarch64 architecture in spite of -cpu host,aarch64=off argument. This is a case of my qemu failure. I suppose this is somehow connected to the new upstream OBS ARM workers, which are not able to run armv7 kernels inside VMs. Is it a known issue? How could I recover service operation? -- With best regards, Matwey V. Kornilov

2 4

xUbuntu_21.04 builds unresolvable
by Martin Tůma 02 Aug '21

02 Aug '21

Hi, xUbuntu_21.04 builds using the qtbase5-private-dev package are unresolvable because of the following error: unresolvable: have choice for libfontconfig1-dev needed by qtbase5-private-dev: libfontconfig-dev libfontconfig1-dev For a sample project triggering this error see https://build.opensuse.org/package/show/home:tumic:GPXSee/gpxsee M.

2 1

Build an Arch Linux repository with Open Build Service
by 山田ハヤオ 31 Jul '21

31 Jul '21

I 'm trying to build my Arch Linux repository using Open Build Service. I created an account and posted my home project PKGBUILD. But the wiki and documentation only has documentation for Spec files, not for Arch Linux. Even if I upload PKGBUILD from the web client, the build fails. My repository and the package that has a problem is here https://build.opensuse.org/package/show/home:hayao/fascode-live-tools Please tell me how to Looking at other people's repositories, it looks like the repositories need files other than PKGBUILD, but I couldn't find any documentation about them.

3 5

SLE_15 build fails with invalid license for GPLv2
by Ralf Becker 30 Jul '21

30 Jul '21

https://build.opensuse.org/package/live_build_log/server:eGroupWare/egroupw… I could understand "GPLv2" being an invalid license-specifier, if not all other build targets would succeed, including eg. openSUSE_Leap_15.{0..3}, which are basically the same environment. Any ideas? Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

4 4

removing a package from OBS
by Roger Oberholtzer 30 Jul '21

30 Jul '21

If I have added a package on the build service via the web interface, how can I remove that package? I want to clean up my stuff on the build service. Am I blind? I really do not see where to remove a package that I have added. -- Roger Oberholtzer

2 2

Re: Build an Arch Linux repository with Open Build Service
by Axel Braun 29 Jul '21

29 Jul '21

Hi, please answer to the list, not to me personally: Am Donnerstag, 29. Juli 2021, 09:02:59 CEST schrieb 山田ハヤオ: > I have already read the guidelines. > But it's a simple Arch Linux link to the WIki, nothing about the Open Build > Service. Looks like the documentation needs some love.... > I want to migrate the packages I post to AUR to Open Build > Service. > > There are various files in the osc package. > Which of them do you need for Arch Linux? osc as I can see from PKGBUILD. There are additional dependencies (python-m2crypto) where OBS takes care about. HTH Axel

1 0

Error on CentOS Stream 8 with cmake not finding correct cmake-filesystem package
by Neal Gompa 28 Jul '21

28 Jul '21

Hey, I'm seeing an error in OBS where it can't resolve the "cmake" package dependencies when I try to build something that uses CMake on CentOS Stream 8. I'm getting the following error: unresolvable: nothing provides cmake-filesystem(x86-64) = 3.20.2-4.el8 needed by cmake, (got version 3.20.2-1.el8 provided by cmake-filesystem) However, I see that cmake-filesystem-3.20.2-4.el8.x86_64 exists in the repository: http://mirror.centos.org/centos/8-stream/AppStream/x86_64/os/Packages/cmake… You can see an example of the failure here: https://build.opensuse.org/package/show/home:Pharaoh_Atem:OSSLugaru/lugaru Can anyone help? Thanks in advance! -- 真実はいつも一つ！/ Always, there's only one truth!

2 2

ARM-32 builds not working on ARM-64 machine, again
by Kyle Edwards 28 Jul '21

28 Jul '21

Hello all, My ARM-64 server has been churning out ARM-32 builds happily for some time, until today (it worked fine as recently as last week.) The 32-bit builds are failing with "no compliant workers (constraints mismatch hint: hardware:cpu)", and osc checkconstraints shows that there are 0 armv7l workers (whereas our x86_64 machine is also providing the i586 workers.) However, osc workerinfo shows that the ARM-64 worker does not have the "nativeonly" tag which would exclude it from 32-bit builds. Our OBS server is pushing a hacked version of bs_worker which backports https://github.com/openSUSE/open-build-service/pull/10850. I've confirmed that this hacked bs_worker is still present in /usr/lib/obs/server, and that the worker has it in its /run/obs/worker/<num>/worker directory. Any ideas on why ARM-32 builds are suddenly not working? Kyle

4 8

repositories
by Peter Czanik 22 Jul '21

22 Jul '21

Hi, I ran into a strange problem while trying to enable the "SUSE SLE-15-SP3" repository in a project. As soon as I clicked on it, "openSUSE Leap 15.3" got disabled. It seems as if the two buttons were somehow linked. How can I enable both, like I have it in other projects? Peter

2 1

How to build products for CODE15?
by Srinidhi B 19 Jul '21

19 Jul '21

Hello Team, We want to build our CODE12 based products ("_product" package) on CODE15. I have been following the way openSUSE Leap 15.x and SLE15 products are being built, but I am not sure which "00X..." packages should contain which files. The Product Definition wiki page still refers to "_product" details: https://en.opensuse.org/openSUSE:Build_Service_Concept_Product_Definition I couldn't find any documentation in either the OBS User or Administrator guide. I also searched the KIWI-ng documentation. I found 2 mentions of building products, but I can't find any useful content: https://openbuildservice.org/2017/09/22/two-new-guides-for-builders/ https://github.com/openSUSE/obs-docu/blob/master/xml/obs_product_building.x… I installed and ran the "obs-service-product_converter" service script locally on our existing "_product" package. After making a few changes to the My.product file, I was able to run the script. It generated following files: * A _multibuild file. * KIWI files for each media. * Keywords (KWD) files for each media. * Release package spec and changes files. My questions: * Where shall I place these files? In a package called 000product? * How do we use 000package-groups, 000release-packages, and 000update-repos * How were these packages created for the first time in openSUSE:Leap:15.1 project? Regards, Srinidhi.

2 1

Metrics
by Moritz Röhrich 16 Jul '21

16 Jul '21

Dear OBS Devs, I was wondering if there is a way to collect metrics from OBS. Of particular interest to me are build queue length, number of in-progress package builds and regular CPU/memory usage metrics. In my use case, I want to use the metrics to let Kubernetes determine automatically how many workers to deploy. This works almost alright with the limited metrics support that I already have from Kubernetes itself, but there are some pitfalls and edge cases where Kubernetes removes workers before they are fully done building a package. My current situation is this: I have a StatefulSet for the workers and a HorizontalPodAutoscaler which will scale up the StatefulSet once CPU usage (as determined by Kubernetes itself) exceeds the threshold (workers are no longer idle). Due to long periods of IO bound operations where CPU usage may fall below the threshold, the autoscaler needs to delay scale-down operations by at least 30 min. This is quite hacky and only really works as long as the build time of the packages does not significantly exceed 30 minutes. The downsides are that the scaling only happens once CPU usage increases, which is usually quite late in the package building process and that workers may be killed too early, if CPU usage at the end of the build process is too low for too long. If I had the build queue length and the number of in-progress package builds as scrapeable metric, I could utilize that to let Kubernetes determine the right amount of workers more reliably. Best regards, Moritz Röhrich -- Quobyte GmbH, Berlin, AG Charlottenburg HRB 149012 B, Felix Hupfeld, Bjoern Kolbeck -- Quobyte GmbH, Berlin, AG Charlottenburg HRB 149012 B, Dr. Felix Hupfeld, Dr. Bjoern Kolbeck

3 4

Problems with conditional rules for SLES 15 SP3 repos on private OBS instance
by Udo Hölzer 16 Jul '21

16 Jul '21

Hello, I'm running in strange problems with conditional rules on the new SLES 15 SP3 repos of our private OBS instance. We are currently using OBS 2.10.10-63.1. %if 0%{?suse_version} %define wwwconfigdir %{_sysconfdir}/apache2/conf.d %define wwwuser wwwrun %define php php %define php_runtime mod_php_any %define php_common %{php} %define php_cli %{php} # extra requirements on openSUSE BuildRequires: fdupes BuildRequires: gettext-tools BuildRequires: config(krb5) Requires: %{php}-ldap Requires: %{php}-mysql Requires: %{php}-pgsql # conflict with older PHP on SLES and openSUSE Conflicts: php < %{php_version} Conflicts: php5 < %{php_version} Conflicts: php53 %endif The nessesary RPM are not pulled from the parent repos if an "BuildRequires:" is encapsulated within an condition. The result looks like... [ 282s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature --define 'disturl obs://cvd/cvd_moni_2020/SLE_15_SP3/b70f064822eb864e7e70d257f9bbd802-icingaweb2' /home/abuild/rpmbuild/SOURCES/icingaweb2.spec [ 282s] error: Failed build dependencies: [ 282s] fdupes is needed by icingaweb2-2.8.2-1.1.noarch ... and the build process aborts. The same project build fine for SLES 15 SP2 and many other SLES versions. I can also build it local on the OBS server with... # osc co cvd_moni_2020 icingaweb2 # osc build --no-verify SLE_15_SP3 x86_64 icingaweb2.spec The SLES 15 SP3 Base Project has all nessaary RPM's in his :full tree and the project configuration defines "suse_version"... %define suse_version 1500 %define sle_version 150300 Macros: %suse_version 1500 %sle_version 150300 :Macros Projects without contitional "BuildRequires:" build fine for SLES 15 SP3. I watched the build process on the OBS server inside the worker file system /var/cache/obs/worker/root_??. For SLES 15 SP3... The definition for suse_version is included in /var/cache/obs/worker/root_1/.build.config but the required fdupes rpm is missing in /var/cache/obs/worker/root_1/.build.rpmlist and is missing as an result in the build process. root@obs::full # cat /var/cache/obs/worker/root_1/.build.command #!/bin/sh -x exec "rpmbuild" "-ba" "--define" "_srcdefattr (-,root,root)" "--nosignature" "--define" "disturl obs://cvd/cvd_moni_2020/SLE_15_SP3/b70f064822eb864e7e70d257f9bbd802-icingaweb2" "/home/abuild/rpmbuild/SOURCES/icingaweb2.spec" root@obs::full # grep suse_version /var/cache/obs/worker/root_1/.build.config %define suse_version 1500 %suse_version 1500 %define suse_version 1500 %suse_version 1500 root@obs::full # grep fdupes /var/cache/obs/worker/root_1/.build.rpmlist And For SLES 15 SP2 everything works as expected... root@obs::full # cat /var/cache/obs/worker/root_5/.build.command #!/bin/sh -x exec "rpmbuild" "-ba" "--define" "_srcdefattr (-,root,root)" "--nosignature" "--define" "disturl obs://cvd/cvd_moni_2020/SLE_15_SP2/b70f064822eb864e7e70d257f9bbd802-icingaweb2" "/home/abuild/rpmbuild/SOURCES/icingaweb2.spec" root@obs::full # grep suse_version /var/cache/obs/worker/root_5/.build.config %define suse_version 1500 %suse_version 1500 %define suse_version 1500 %suse_version 1500 root@obs::full # grep fdupes /var/cache/obs/worker/root_5/.build.rpmlist fdupes /var/cache/obs/worker/root_5/.pkgs/fdupes.rpm I'm using OBS since version 2.6 for many years and never met such problems. Is there anything to further debug the build process or has anyone an idea, how to fix this problem? With best regards, Jens Hofbauer

1 0

headsup: breaking change in tar_scm/obs_scm
by Frank Schreiner 15 Jul '21

15 Jul '21

Hi, with the new deployment of our current services comes a breaking change for those who use '%cd' in the versionformat combined with 'versionrewrite-pattern'/'versionrewrite-replacement'. The date format changes from 'YYYY-MM-DD' back to 'YYYYMMDD' Here is a list of packages that might be affected: base dino thruk czmq libzmq zyre naemon pyzmq malamute rpcs3 glar150 naemon-core thruk_libs naemon-livestatus cheers Frank

1 0

Authentication failed in Kerberos
by 562482135＠qq.com 13 Jul '21

13 Jul '21

Hello all, I configured Kerberos mode to sign on, but it failed,the environment is as follows: OS:openSUSE Leap 15.2 OBS version:2.10.10 hostname:obsserver Kerberos section of the options.yml file: kerberos_mode: true kerberos_keytab: "/etc/krb5.keytab" kerberos_service_principal: "HTTPS/obsserver.abc.com(a)ABC.COM" kerberos_realm: "ABC.COM" /etc/krb5.keytab: Kerberos Keytab file, realm=ABC.COM, principal=host/10.198.10.10, type=1, date=Fri Jan 3 18:51:26 2020, kvno=1 The following error is reported when signing on: Authentication failed: 'Received a GSSAPI exception; gss_acquire_cred did not return GSS_S_COMPLETE: Unspecified GSS failure. Minor code may provide more information No key table entry found matching HTTPS/obsserver.abc.com@ .' I configured it according to https://openbuildservice.org/help/manuals/obs-admin-guide/obs.cha.administr… 4.8.7.2 Kerberos.

1 0

How should I set up debian.series properly?
by hwsnemo 12 Jul '21

12 Jul '21

Hello, I am trying to package deb and rpm in the same obs package with patches. I was able to do RPM somehow but applying patches with debian.series seems to have some problems. Is it just a bug or did i do something wrong? Below lines are error logs: [ 238s] Found files matching debian.*, running debian transformer... [ 238s] release: (7.1), release (DEB) (7.1) [ 238s] ** Started: debtransform --release 7.1 //usr/src/packages/SOURCES //usr/src/packages/SOURCES/wine-osu_6.12-1.dsc //usr/src/packages/SOURCES.DEB [ 238s] Transforming into source package 1.0 (non-native) format [ 238s] converting //usr/src/packages/SOURCES/wine-staging-6.12-patched.tar.xz to wine-staging-6.12-patched.tar.gz [ 248s] Moving //usr/src/packages/SOURCES/wine-staging-6.12-patched.tar.gz to //usr/src/packages/SOURCES.DEB/wine-osu_6.12.orig.tar.gz [ 248s] files dc61399b56f26a7e98d18ab3c3abf93a 50443187 wine-osu_6.12.orig.tar.gz [ 248s] Scanning //usr/src/packages/SOURCES.DEB/wine-osu_6.12.orig.tar.gz... [ 250s] Generating //usr/src/packages/SOURCES.DEB/wine-osu_6.12-1.diff [ 250s] Scanning //usr/src/packages/SOURCES/wine-osu.debian.tar.xz... [ 250s] Processing file "//usr/src/packages/SOURCES/debian.changelog"... [ 250s] Processing series file "//usr/src/packages/SOURCES/debian.series"... [ 250s] Processing patch //usr/src/packages/SOURCES/0001-Revert-to-5.14-winepulse.drv.patch... [ 250s] Processing patch //usr/src/packages/SOURCES/0002-5.14-Latency-Fix.patch... [ 250s] Processing patch //usr/src/packages/SOURCES/0003-secur32-Fix-crash-from-invalid-context-in-Initialize.patch... [ 250s] Processing patch //usr/src/packages/SOURCES/0004-kernelbase-Cache-last-used-locale-sortguid-mapping.patch... [ 250s] Writing //usr/src/packages/SOURCES.DEB/wine-osu_6.12-1.dsc [ 250s] dpkg-source: warning: extracting unsigned source package (/usr/src/packages/SOURCES.DEB/wine-osu_6.12-1.dsc) [ 250s] dpkg-source: info: extracting wine-osu in /usr/src/packages/BUILD [ 250s] dpkg-source: info: unpacking wine-osu_6.12.orig.tar.gz [ 252s] dpkg-source: info: applying wine-osu_6.12-1.diff.gz [ 252s] dpkg-source: warning: diff '/usr/src/packages/SOURCES.DEB/wine-osu_6.12-1.diff.gz' patches file /usr/src/packages/BUILD/dlls/winepulse.drv/mmdevdrv.c more than once [ 252s] dpkg-source: info: upstream files that have been modified: [ 252s] /usr/src/packages/BUILD/dlls/kernelbase/locale.c [ 252s] /usr/src/packages/BUILD/dlls/mmdevapi/devenum.c [ 252s] /usr/src/packages/BUILD/dlls/mmdevapi/tests/render.c [ 252s] /usr/src/packages/BUILD/dlls/secur32/schannel.c [ 252s] /usr/src/packages/BUILD/dlls/winealsa.drv/mmdevdrv.c [ 252s] /usr/src/packages/BUILD/dlls/wineandroid.drv/mmdevdrv.c [ 252s] /usr/src/packages/BUILD/dlls/winecoreaudio.drv/mmdevdrv.c [ 252s] /usr/src/packages/BUILD/dlls/wineoss.drv/mmdevdrv.c [ 252s] /usr/src/packages/BUILD/dlls/winepulse.drv/Makefile.in [ 252s] /usr/src/packages/BUILD/dlls/winepulse.drv/mmdevdrv.c [ 252s] /usr/src/packages/BUILD/dlls/winepulse.drv/mult.c [ 252s] /usr/src/packages/BUILD/dlls/winepulse.drv/pulse.c [ 252s] /usr/src/packages/BUILD/dlls/winepulse.drv/unixlib.h [ 252s] /usr/src/packages/BUILD/include/audioclient.idl [ 252s] ----------------------------------------------------------------- [ 252s] ----- building wine-osu_6.12-1.dsc (user abuild) [ 252s] ----------------------------------------------------------------- [ 252s] ----------------------------------------------------------------- [ 252s] dpkg-buildpackage: info: source package wine-osu [ 252s] dpkg-buildpackage: info: source version 6.12-1 [ 252s] dpkg-buildpackage: info: source distribution UNRELEASED [ 252s] dpkg-buildpackage: info: source changed by Rosanne DiMesio <dimesio(a)earthlink.net> [ 252s] dpkg-source --before-build . [ 252s] dpkg-buildpackage: info: host architecture amd64 [ 253s] fakeroot debian/rules clean [ 253s] dh clean --parallel [ 253s] dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) [ 253s] dh_auto_clean -O--parallel [ 253s] dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use) [ 253s] dh_clean -O--parallel [ 253s] dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use) [ 253s] dpkg-source -b . [ 254s] dpkg-source: info: using source format '3.0 (quilt)' [ 254s] dpkg-source: info: building wine-osu using existing ./wine-osu_6.12.orig.tar.gz [ 256s] dpkg-source: warning: ignoring deletion of directory autom4te.cache [ 256s] dpkg-source: warning: ignoring deletion of file autom4te.cache/output.0, use --include-removal to override [ 256s] dpkg-source: warning: ignoring deletion of file autom4te.cache/traces.0, use --include-removal to override [ 256s] dpkg-source: warning: ignoring deletion of file autom4te.cache/requests, use --include-removal to override [ 256s] dpkg-source: warning: ignoring deletion of file dlls/winepulse.drv/unixlib.h, use --include-removal to override [ 256s] dpkg-source: warning: ignoring deletion of file dlls/winepulse.drv/pulse.c, use --include-removal to override [ 256s] dpkg-source: warning: ignoring deletion of file dlls/winepulse.drv/mult.c, use --include-removal to override [ 257s] dpkg-source: info: local changes detected, the modified files are: [ 257s] BUILD/dlls/kernelbase/locale.c [ 257s] BUILD/dlls/mmdevapi/devenum.c [ 257s] BUILD/dlls/mmdevapi/tests/render.c [ 257s] BUILD/dlls/secur32/schannel.c [ 257s] BUILD/dlls/winealsa.drv/mmdevdrv.c [ 257s] BUILD/dlls/wineandroid.drv/mmdevdrv.c [ 257s] BUILD/dlls/winecoreaudio.drv/mmdevdrv.c [ 257s] BUILD/dlls/wineoss.drv/mmdevdrv.c [ 257s] BUILD/dlls/winepulse.drv/Makefile.in [ 257s] BUILD/dlls/winepulse.drv/mmdevdrv.c [ 257s] BUILD/include/audioclient.idl [ 257s] dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/wine-osu_6.12-1.diff.hsxEmH [ 257s] dpkg-source: info: you can integrate the local changes with dpkg-source --commit [ 257s] dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2

3 2

How should I properly setup debian.series?
by hwsnemo 12 Jul '21

12 Jul '21

Hello, I am trying to package deb and rpm in the same obs package with patches. I was able to do RPM somehow but applying patches with debian.series seems to have some problems. Is it just a bug or did i do something wrong? Below lines are error logs: [ 238s] Found files matching debian.*, running debian transformer... [ 238s] release: (7.1), release (DEB) (7.1) [ 238s] ** Started: debtransform --release 7.1 //usr/src/packages/SOURCES //usr/src/packages/SOURCES/wine-osu_6.12-1.dsc //usr/src/packages/SOURCES.DEB [ 238s] Transforming into source package 1.0 (non-native) format [ 238s] converting //usr/src/packages/SOURCES/wine-staging-6.12-patched.tar.xz to wine-staging-6.12-patched.tar.gz [ 248s] Moving //usr/src/packages/SOURCES/wine-staging-6.12-patched.tar.gz to //usr/src/packages/SOURCES.DEB/wine-osu_6.12.orig.tar.gz [ 248s] files dc61399b56f26a7e98d18ab3c3abf93a 50443187 wine-osu_6.12.orig.tar.gz [ 248s] Scanning //usr/src/packages/SOURCES.DEB/wine-osu_6.12.orig.tar.gz... [ 250s] Generating //usr/src/packages/SOURCES.DEB/wine-osu_6.12-1.diff [ 250s] Scanning //usr/src/packages/SOURCES/wine-osu.debian.tar.xz... [ 250s] Processing file "//usr/src/packages/SOURCES/debian.changelog"... [ 250s] Processing series file "//usr/src/packages/SOURCES/debian.series"... [ 250s] Processing patch //usr/src/packages/SOURCES/0001-Revert-to-5.14-winepulse.drv.patch... [ 250s] Processing patch //usr/src/packages/SOURCES/0002-5.14-Latency-Fix.patch... [ 250s] Processing patch //usr/src/packages/SOURCES/0003-secur32-Fix-crash-from-invalid-context-in-Initialize.patch... [ 250s] Processing patch //usr/src/packages/SOURCES/0004-kernelbase-Cache-last-used-locale-sortguid-mapping.patch... [ 250s] Writing //usr/src/packages/SOURCES.DEB/wine-osu_6.12-1.dsc [ 250s] dpkg-source: warning: extracting unsigned source package (/usr/src/packages/SOURCES.DEB/wine-osu_6.12-1.dsc) [ 250s] dpkg-source: info: extracting wine-osu in /usr/src/packages/BUILD [ 250s] dpkg-source: info: unpacking wine-osu_6.12.orig.tar.gz [ 252s] dpkg-source: info: applying wine-osu_6.12-1.diff.gz [ 252s] dpkg-source: warning: diff '/usr/src/packages/SOURCES.DEB/wine-osu_6.12-1.diff.gz' patches file /usr/src/packages/BUILD/dlls/winepulse.drv/mmdevdrv.c more than once [ 252s] dpkg-source: info: upstream files that have been modified: [ 252s] /usr/src/packages/BUILD/dlls/kernelbase/locale.c [ 252s] /usr/src/packages/BUILD/dlls/mmdevapi/devenum.c [ 252s] /usr/src/packages/BUILD/dlls/mmdevapi/tests/render.c [ 252s] /usr/src/packages/BUILD/dlls/secur32/schannel.c [ 252s] /usr/src/packages/BUILD/dlls/winealsa.drv/mmdevdrv.c [ 252s] /usr/src/packages/BUILD/dlls/wineandroid.drv/mmdevdrv.c [ 252s] /usr/src/packages/BUILD/dlls/winecoreaudio.drv/mmdevdrv.c [ 252s] /usr/src/packages/BUILD/dlls/wineoss.drv/mmdevdrv.c [ 252s] /usr/src/packages/BUILD/dlls/winepulse.drv/Makefile.in [ 252s] /usr/src/packages/BUILD/dlls/winepulse.drv/mmdevdrv.c [ 252s] /usr/src/packages/BUILD/dlls/winepulse.drv/mult.c [ 252s] /usr/src/packages/BUILD/dlls/winepulse.drv/pulse.c [ 252s] /usr/src/packages/BUILD/dlls/winepulse.drv/unixlib.h [ 252s] /usr/src/packages/BUILD/include/audioclient.idl [ 252s] ----------------------------------------------------------------- [ 252s] ----- building wine-osu_6.12-1.dsc (user abuild) [ 252s] ----------------------------------------------------------------- [ 252s] ----------------------------------------------------------------- [ 252s] dpkg-buildpackage: info: source package wine-osu [ 252s] dpkg-buildpackage: info: source version 6.12-1 [ 252s] dpkg-buildpackage: info: source distribution UNRELEASED [ 252s] dpkg-buildpackage: info: source changed by Rosanne DiMesio <dimesio(a)earthlink.net> [ 252s] dpkg-source --before-build . [ 252s] dpkg-buildpackage: info: host architecture amd64 [ 253s] fakeroot debian/rules clean [ 253s] dh clean --parallel [ 253s] dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) [ 253s] dh_auto_clean -O--parallel [ 253s] dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use) [ 253s] dh_clean -O--parallel [ 253s] dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use) [ 253s] dpkg-source -b . [ 254s] dpkg-source: info: using source format '3.0 (quilt)' [ 254s] dpkg-source: info: building wine-osu using existing ./wine-osu_6.12.orig.tar.gz [ 256s] dpkg-source: warning: ignoring deletion of directory autom4te.cache [ 256s] dpkg-source: warning: ignoring deletion of file autom4te.cache/output.0, use --include-removal to override [ 256s] dpkg-source: warning: ignoring deletion of file autom4te.cache/traces.0, use --include-removal to override [ 256s] dpkg-source: warning: ignoring deletion of file autom4te.cache/requests, use --include-removal to override [ 256s] dpkg-source: warning: ignoring deletion of file dlls/winepulse.drv/unixlib.h, use --include-removal to override [ 256s] dpkg-source: warning: ignoring deletion of file dlls/winepulse.drv/pulse.c, use --include-removal to override [ 256s] dpkg-source: warning: ignoring deletion of file dlls/winepulse.drv/mult.c, use --include-removal to override [ 257s] dpkg-source: info: local changes detected, the modified files are: [ 257s] BUILD/dlls/kernelbase/locale.c [ 257s] BUILD/dlls/mmdevapi/devenum.c [ 257s] BUILD/dlls/mmdevapi/tests/render.c [ 257s] BUILD/dlls/secur32/schannel.c [ 257s] BUILD/dlls/winealsa.drv/mmdevdrv.c [ 257s] BUILD/dlls/wineandroid.drv/mmdevdrv.c [ 257s] BUILD/dlls/winecoreaudio.drv/mmdevdrv.c [ 257s] BUILD/dlls/wineoss.drv/mmdevdrv.c [ 257s] BUILD/dlls/winepulse.drv/Makefile.in [ 257s] BUILD/dlls/winepulse.drv/mmdevdrv.c [ 257s] BUILD/include/audioclient.idl [ 257s] dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/wine-osu_6.12-1.diff.hsxEmH [ 257s] dpkg-source: info: you can integrate the local changes with dpkg-source --commit [ 257s] dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2

1 0

Cannot automatically resolve and install dependency packages when compiling Debian10
by 562482135＠qq.com 08 Jul '21

08 Jul '21

When compiling the package of Debian10, the dependent package is not installed, such as: [ 27s] [57/259] installing libpython3.7-minimal-3.7.3-2+deb10u3 [ 28s] dpkg: libpython3.7-minimal:amd64: dependency problems, but configuring anyway as you requested: [ 28s] libpython3.7-minimal:amd64 depends on libssl1.1 (>= 1.1.1); however: [ 28s] Package libssl1.1 is not installed. I think that all dependent packages should be installed, whether it is a direct dependency or an indirect dependency.

1 0

Cannot automatically resolve and install dependency packages when compiling Debian10
by 562482135＠qq.com 08 Jul '21

08 Jul '21

When compiling the package of Debian10, the dependent package is not installed, such as: [ 27s] [57/259] installing libpython3.7-minimal-3.7.3-2+deb10u3 [ 28s] dpkg: libpython3.7-minimal:amd64: dependency problems, but configuring anyway as you requested: [ 28s] libpython3.7-minimal:amd64 depends on libssl1.1 (>= 1.1.1); however: [ 28s] Package libssl1.1 is not installed. I think that all dependent packages should be installed, whether it is a direct dependency or an indirect dependency.

1 0

Fedora 34 categorized as "Unknown" at software.opensuse.org
by Andreas Vögele 07 Jul '21

07 Jul '21

Only packages for Fedora 33 show up under "Fedora" at software.opensuse.org. Other Fedora versions are "Unknown" with broken download links. Here's an example, but this seems to be a general problem: https://software.opensuse.org//download.html?project=home%3Aphoenix.os%3Afe… Kind regards, Andreas

2 1

Re: exclude paths in _service file broken
by Olaf Hering 05 Jul '21

05 Jul '21

Am Tue, 8 Jun 2021 14:04:49 +0200 schrieb Olaf Hering <olaf(a)aepfle.de>: > Does anyone happen to know how certain paths are supposed to be excluded in a _service file? This is apparently fixed for x86 builds since a couple of days. But the change is missing for aarch64 builds. I see failures due to lack of commit 0f18bfa. Olaf

1 0

A python packaging single spec issue when upgrading a package
by Lee Duncan 02 Jul '21

02 Jul '21

Hi All: I have a question about python single-spec packaging. [tl;dr: systemd targetcli service goes from enabled to disabled during upgrade.] [BACKGROUND] ------------ Quite a while ago I had to upgrade the "targetcli-fb" package in SLES and openSUSE. At that time, "single spec" was being heavily pushed, even though I would just as soon written a single package and SPEC file for python3. I spent quite a bit of time on the change. It turns out you have to have duplicate ("alternative") copies of everything in your python3-vs-python2 packages, so that they can co-exist, using single-spec. When I complained that I didn't need two version of things like man pages and systemd service files, I was told I should break my package into a "common" part (not python version dependent) and a python-version-dependent part. So with a bit of work I did that. So now targetcli-fb became two new packages: python3-targetcli-fb (assuming python3) and targetcli-fb-common. The "python3-targetcli-fb" package has a "requires" on "targetcli-fb-common", as well as "provides" of "targetcli" and "targetcli-fb". So when a user upgrades from openSUSE 12 to openSUSE 15, the software knows to replace "targetcli" or "targetcli-fb" with the newer "python3-targetcli-fb" and it's subpackage "targetcli-fb-common". [THE PROBLEM] ------------- The problem occurs when the user had the "targetcli.service" systemd service enabled in openSUSE 12 and they upgrade to 15. Ownership of the service file changes from "targetcli-fb" to "python-common-fb", and the install software (using zypper, I assume) fails to understand that the service that was under "targetcli-fb" didn't go away, it just changed ownership to "targetcli-fb-common", and should continue to be enabled. Is there any way to fix this? If not in this case, what should I do in the future to avoid this trap? Thank you for any wisdom you can share! -- lee Duncan

2 1

nothing provides kernel-obs-build
by Marcus Schäfer 01 Jul '21

01 Jul '21

Hi, I'm having a weird issue with the kiwi integration test from here: https://build.opensuse.org/project/show/Virtualization:Appliances:Images:Te… The unresolvables from that page says: osc buildinfo -M Disk images x86_64 <buildinfo project="Virtualization:Appliances:Images:Testing_x86:fedora" repository="images" package="test-image-live-disk:Disk" downloadurl="https://download.opensuse.org/repositories"> <arch>x86_64</arch> <error>unresolvable: vminstalls: nothing provides kernel-obs-build</error> <srcmd5>5d67112c7fde1f103ab09520e067ff31</srcmd5> <verifymd5>e1670184a25866b4021fe1a7a6eb306f</verifymd5> <rev>21</rev> <specfile>_service:obs_scm:appliance.kiwi</specfile> <file>_service:obs_scm:appliance.kiwi</file> <versrel>2.0.0-21</versrel> <bcnt>5</bcnt> <release>21.5</release> <debuginfo>0</debuginfo> <imagetype>oem</imagetype> </buildinfo> I could not come across a way to fix this. Any idea ? Any kernel for the worker is fine to build these images and I actually normally use kernel-default, but setting this in the prjconf has no effect. Thanks much Regards, Marcus -- Public Key available via: https://keybase.io/marcus_schaefer/key.asc keybase search marcus_schaefer ------------------------------------------------------- Marcus Schäfer (Res. & Dev.) SUSE Software Solutions Germany GmbH Tel: 0911-740 53 0 Maxfeldstrasse 5 FAX: 0911-740 53 479 D-90409 Nürnberg HRB: 21284 (AG Nürnberg) Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton http://www.suse.de -------------------------------------------------------

4 8

SSL Fingerprint Mismatch when using DoD Repositories
by Rose, Robert 01 Jul '21

01 Jul '21

Hi all, Can anybody explain to me in how the SSL fingerprint check for DoD repositories works and why it is strongly recommended for security reasons in https://openbuildservice.org/help/manuals/obs-user-guide/cha.obs.concepts.h… We use DoD repositories to pin a tumbleweed snapshot we are working on in our private OBS instance. Each repository has the the respective Tumbleweed snapshot at https://download.opensuse.org/history/ together with the SSL fingerprint of download.opensuse.org<https://download.opensuse.org/history/> specified in its master subelement. However, since last week OBS refuses to download new DoD RPMs due to a fingerprint mismatch. dodup.log says: https://download.opensuse.org/history/20210622/tumbleweed/repo/oss/repodata…: peer fingerprint does not match: 82bac52cf77a1ec92d2184ebb574a97ba28ba98b7b63c3c67656a16ff708fca5 != 286869be29119fd068f94c0b1cd318068568c0b7f3036b303f5d102e512be80f Please notice that 82ba...fca5 is the (current!) fingerprint of download.opensuse.org<https://download.opensuse.org/history/> and 2868...e80f is from ftp.gwdg.de/<https://ftp.gwdg.de/>, which makes kind of perfect sense as a curl on https://download.opensuse.org/history/20210622/tumbleweed/repo/oss/repodata… on our download server gives the following response: ~> curl https://download.opensuse.org/history/20210622/tumbleweed/repo/oss/repodata… <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1> <p>The document has moved <a href="https://ftp.gwdg.de/pub/opensuse/history/20210622/tumbleweed/repo/oss/repod…">here</a>.</p> <hr> <address>Apache/2.4.43 (Linux/SUSE) Server at download.opensuse.org Port 443</address> </body></html> Now to my questions: Is OBS expected to check the fingerprint of documents that can be redirected? I would have expected it to check only the fingerprint of the repomd.xml file in the regarding repository. On other servers I get other redirects (e.g. http://ftp.halifax.rwth-aachen.de) Anyway, I fail to see the sense of an SSL fingerprint check when resources can redirect to other domains. Do I miss an important point here? Wouldn't it be sufficient to rely on the GPG signature of the RPMs? I am considering removing the master subelement completely. This issue does not have its origin in a rotated letsencrypt certificate, we already take that into account. However, a new certificate could be issued the upcoming days so please do not look to closely on the specific fingerprints mentioned in this post but the general questions about fingerprint checks in DoD repositories. Any help is greatly appreciated. Regards, Robert Appendix: Examplary DoD configuration in our OBS <repository name="next"> <download arch="x86_64" url="https://download.opensuse.org/history/20210623/tumbleweed/repo/oss/" repotype="rpmmd"> <master url="https://download.opensuse.org/history/20210623/tumbleweed/repo/oss/" sslfingerprint="sha256:82bac52cf77a1ec92d2184ebb574a97ba28ba98b7b63c3c67656a16ff708fca5"/> <archfilter>x86_64</archfilter> <pubkey> -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v2.0.15 (GNU/Linux) mQENBEkUTD8BCADWLy5d5IpJedHQQSXkC1VK/oAZlJEeBVpSZjMCn8LiHaI9Wq3G 3Vp6wvsP1b3kssJGzVFNctdXt5tjvOLxvrEfRJuGfqHTKILByqLzkeyWawbFNfSQ 93/8OunfSTXC1Sx3hgsNXQuOrNVKrDAQUqT620/jj94xNIg09bLSxsjN6EeTvyiO mtE9H1J03o9tY6meNL/gcQhxBvwuo205np0JojYBP0pOfN8l9hnIOLkA0yu4ZXig oKOVmf4iTjX4NImIWldT+UaWTO18NWcCrujtgHueytwYLBNV5N0oJIP2VYuLZfSD VYuPllv7c6O2UEOXJsdbQaVuzU1HLocDyipnABEBAAG0NG9wZW5TVVNFIFByb2pl Y3QgU2lnbmluZyBLZXkgPG9wZW5zdXNlQG9wZW5zdXNlLm9yZz6JATwEEwECACYC GwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAUCU2dN1AUJHR8ElQAKCRC4iy/UPb3C hGQrB/9teCZ3Nt8vHE0SC5NmYMAE1Spcjkzx6M4r4C70AVTMEQh/8BvgmwkKP/qI CWo2vC1hMXRgLg/TnTtFDq7kW+mHsCXmf5OLh2qOWCKi55Vitlf6bmH7n+h34Sha Ei8gAObSpZSF8BzPGl6v0QmEaGKM3O1oUbbB3Z8i6w21CTg7dbU5vGR8Yhi9rNtr hqrPS+q2yftjNbsODagaOUb85ESfQGx/LqoMePD+7MqGpAXjKMZqsEDP0TbxTwSk 4UKnF4zFCYHPLK3y/hSH5SEJwwPY11l6JGdC1Ue8Zzaj7f//axUs/hTC0UZaEE+a 5v4gbqOcigKaFs9Lc3Bj8b/lE10Y =i2TA -----END PGP PUBLIC KEY BLOCK----- </pubkey> </download> <arch>x86_64</arch> </repository> -- Robert Rose Embedded System Engineer Edge Device Competence Center

3 2