openSUSE Build Service December 2022

buildservice@lists.opensuse.org

14 participants
14 discussions

nothing provides cmake-filesystem(x86-64) = 3.20.2-4.el8 needed by cmake when trying to compile for CentOS Stream 8
by Luciano Santos 05 Dec '22

05 Dec '22

It took a bit of a discussion in #opensuse-buildservice and some digging up. So let's see what's going on. In security:zeek project we can see this message for CentOS 8 Stream repository: > unresolvable: nothing provides glibc(x86-64) = 2.28-203.el8 needed by glibc-gconv-extra, (got version 2.28-214.el8 provided by glibc), nothing provides glibc-common = 2.28-203.el8 needed by glibc-gconv-extra, (got version 2.28-214.el8) Please remember that our CentOS 8 Stream repository uses http://mirror.centos.org/centos/8-stream/ for package download, and that the AppStream repo takes precedence over BaseOS. First, let's check the version 2.28-203 for glibc, because that's the latest release that AppStream got: > $ curl -sLI http://mirror.centos.org/centos/8-stream/AppStream/x86_64/os/Packages/glibc… | head -1 > HTTP/1.1 404 Not Found > curl -sLI http://mirror.centos.org/centos/8-stream/AppStream/x86_64/os/Packages/glibc… | head -1 > HTTP/1.1 200 OK > > $ curl -sLI http://mirror.centos.org/centos/8-stream/BaseOS/x86_64/os/Packages/glibc-2.… | head -1 > HTTP/1.1 200 OK > $ curl -sLI http://mirror.centos.org/centos/8-stream/BaseOS/x86_64/os/Packages/glibc-gc… | head -1 > HTTP/1.1 404 Not Found Here we can see that glibc-gconv-extra, a sub-package ofglibc, found in BaseOS, got split and is found in Appstream instead. OBS/openSUSE/many-other-RPM-based-distros(I believe) doesn't support a Package A being required by its Sub-Package B when A comes from Vendor/repo X and B, from Vendor/repo Y. DNF doesn't seem to share such restrictions, though, as seen here [1] in this bug report. And those missing glib (and possibly others) RPMs from mirror.centos.org are a result of an official decision to move certain packages from one repository to another (as stated in that bug report), but it seems that the move wasn't completed/successful, at least from my perspective of having Package A living in repo X being required by its Sub-Package B living in repo Y. Now, if the BaseOS repo takes precedence over AppStream we can find both 2.28-214 glibc and glibc-gconv-extra packages there: > $ fc > curl -sLI http://mirror.centos.org/centos/8-stream/BaseOS/x86_64/os/Packages/glibc-2.… | head -1 > curl -sLI http://mirror.centos.org/centos/8-stream/BaseOS/x86_64/os/Packages/glibc-gc… | head -1 > HTTP/1.1 200 OK > HTTP/1.1 200 OK Nonetheless, with BaseOS being above AppStream we get the unresolvable reported in this thread: > 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) That's because in BaseOS we can find another Package/Sub-Package missing: > $ curl -sLI http://mirror.centos.org/centos/8-stream/BaseOS/x86_64/os/Packages/cmake-3.… | head -1 > HTTP/1.1 404 Not Found > curl -sLI http://mirror.centos.org/centos/8-stream/BaseOS/x86_64/os/Packages/cmake-fi… | head -1 > HTTP/1.1 200 OK A cmake-filesystem-3.20.2-1 that wants a not found cmake-3.20.2-1. And in AppStream: > $ curl -sLI http://mirror.centos.org/centos/8-stream/AppStream/x86_64/os/Packages/cmake… | head -1 > HTTP/1.1 200 OK > $ curl -sLI http://mirror.centos.org/centos/8-stream/AppStream/x86_64/os/Packages/cmake… | head -1 > HTTP/1.1 200 OK Both packages are there, but since we're prioritizing BaseOS and one of them was already found, we end up with an unresolvable. In BaseOS we don't have a 3.20.2-4 CMake release (which would take precedence over 3.20.2-1), only in Appstream: > $ curl -sLI http://mirror.centos.org/centos/8-stream/BaseOS/x86_64/os/Packages/cmake-3.… | head -1 > HTTP/1.1 404 Not Found > $ curl -sLI http://mirror.centos.org/centos/8-stream/BaseOS/x86_64/os/Packages/cmake-fi… | head -1 > HTTP/1.1 404 Not Found > > $ curl -sLI http://mirror.centos.org/centos/8-stream/AppStream/x86_64/os/Packages/cmake… | head -1 > HTTP/1.1 200 OK > $ curl -sLI http://mirror.centos.org/centos/8-stream/AppStream/x86_64/os/Packages/cmake… | head -1 > HTTP/1.1 200 OK But, again, since we're prioritizing BaseOS and one of them was already found, we end up with an unresolvable. The right way forward, I'd say, is to file bugs for those missing packages and/or add comments to existing bugs, like the one for glibc. Cheers, Luciano [1] https://bugzilla.redhat.com/show_bug.cgi?id=2102548

3 4

Regression: OBS does not install gzip when building Arch Linux packages, which breaks builds
by - - 02 Dec '22

02 Dec '22

Please refer to https://github.com/openSUSE/open-build-service/issues/13403 for details. The maintainer of Arch:Core has been pinged on GitHub, but there is no response from him. Hopefully OBS admins / mods can look into this issue and introduce a fix.

1 0

EL9 debuginfo generation broken on build.opensuse.org
by Jan Engelhardt 01 Dec '22

01 Dec '22

In build.opensuse.org / home:jengelh:EL / nginx-module-brotli-EL, the EL9.x86_64 (AlmaLinux9) build produces an error because rpm apparently can't figure out its own debuginfo mess. [ 111s] error: File not found: /home/abuild/rpmbuild/BUILDROOT/nginx-module-brotli-1.0.0rc+g1-1.1.x86_64/usr/src/debug/nginx-module-brotli-1.0.0rc+g1-1.1.x86_64 [ 111s] [ 111s] [ 111s] RPM build errors: [ 111s] File not found: /home/abuild/rpmbuild/BUILDROOT/nginx-module-brotli-1.0.0rc+g1-1.1.x8 6_64/usr/src/debug/nginx-module-brotli-1.0.0rc+g1-1.1.x86_64 What exists: /home/abuild/rpmbuild/BUILDROOT/nginx-module-brotli-1.0.0rc+g1-1.1.x8 6_64/usr/src/debug/.dwz/nginx-module-brotli-1.0.0rc+g1-1.1.x86_64 What can we do?

1 0

What is the mean of <param name="submodules">master</param>
by liuxueping.snow＠bytedance.com 01 Dec '22

01 Dec '22

here is a <param name="submodules">master</param> configuration in tar_scm.service, but I don't know what the specific meaning of this parameter is.And i kown the difference is git submodule update --init --recursive and git submodule update --init --recursive --remote in TarSCM/scm/git.py. But I don't know why this distinction is made.

3 4

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service December 2022