July 2021 - openSUSE Build Service - openSUSE Mailing Lists

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