openSUSE Build Service May 2023

buildservice@lists.opensuse.org

24 participants
18 discussions

Start a nNew thread

How do I add the Tumbleweed repository to the ISO, so that it exists when starting the Live ISO?
by Ruach 08 May '23

08 May '23

ISO: https://build.opensuse.org/package/show/home:hopeandtruth6517:nova-flow-os/…

1 0

Key missing for openSUSE:Leap:15.5:Update?
by Johannes Kastl 08 May '23

08 May '23

Good morning, when building for 15.5 locally I get the following warning: > Verifying integrity of cached packages > using keys from SUSE:SLE-15-SP3:Update, SUSE:SLE-15:GA, SUSE:SLE-15-SP4:GA, SUSE:SLE-15:Update, SUSE:SLE-15-SP4:Update, SUSE:SLE-15-SP3:GA, SUSE:SLE-15-SP5:GA, SUSE:SLE-15-SP2:GA, SUSE:SLE-15-SP1:Update, SUSE:SLE-15-SP2:Update, SUSE:SLE-15-SP1:GA, SUSE:SLE-15-SP5:Update, devel:languages:python, home:ojkastl_buildservice, openSUSE:Leap:15.5 > warning: /home/Buildservice/22_packagecache/openSUSE:Leap:15.5:Update/standard/x86_64/rpmlint-mini-1.10-lp155.4.2.1.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 3dbdc284: NOKEY > /home/Buildservice/22_packagecache//openSUSE:Leap:15.5:Update/standard/x86_64/rpmlint-mini-1.10-lp155.4.2.1.x86_64.rpm : public key not available I looked into the old thread for missing keys with SLES12, back then this needed to be adapted on the build service side. Not sure if this is the same error, but if it is, could someone fix this, please? Kind Regards, Johannes -- 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 2

Problems with %{?sle15_python_module_pythons}
by Eric Schirra 06 May '23

06 May '23

Hello, I have been having problems building python packages in my homerepo for a few days now. And only for packages wich has %{?sle15_python_module_pythons} in his spec. All other will build. The reason is probably %{?sle15_python_module_pythons}. Which according to the threat in opensuse-packaging is not used if not configured. I don't have that either. At least not myself. However (now the text from opensuse-packaging): Using the GUI of the web browser I can't find an entry in ProjectConfig with %sle15_python_module_pythons(). But if I use offline "osc buildconfig home:ecsos 15.4" to display the ProjectConfig there appears: #request by slemke/dmueller 2023-05-04 for python311 builds. macros: # Macro to build Python stack proposal packages %sle15_python_module_pythons() %global pythons python311 :macros Why is that in there? According to your previous explanation, this is also observed in the specs and thus python311 is built. (But also only 311. Nothing else) Surely this should not be? Or is that now nevertheless firmly everywhere in it? Does he think that is a mistake? Why? How do I get the way? I do not see him online. Or can you take care of it and correct it? Regards Eric

1 0

Ubuntu 22.04 build order issue when building in OBS
by Dirk Stöcker 05 May '23

05 May '23

Hello, when I try to use Ubuntu 22.04 I always get [ 11s] [234/305] installing libssl-dev-3.0.2-0ubuntu1 [ 11s] [235/305] installing fontconfig-config-2.13.1-4.2ubuntu5 [ 11s] [236/305] installing libdebuginfod-common-0.186-1build1 [ 11s] /usr/bin/ucf: 352: getopt: not found [ 11s] dpkg: error processing package libdebuginfod-common (--install): [ 11s] installed libdebuginfod-common package post-installation script subprocess returned error exit status 127 [ 11s] Errors were encountered while processing: [ 11s] libdebuginfod-common It seems there is an installation conflict that getopt is required before util-linux is installed. Could this please be fixed? Also it seems Ubuntu 21.04 universe should be refreshed. I tries to download e.g. http://ftp.halifax.rwth-aachen.de/ubuntu/pool/universe/t/texlive-lang/texli… but this file doesn't exist on this server. P.S. I build with osc locally. Freedom in Peace -- https://www.dstoecker.eu/ (PGP key available)

4 6

Lots of broken packages due to year changed in boilerplate: How to avoid this?
by Johannes Kastl 05 May '23

05 May '23

Good morning, for building ansible for SLES15 I had to branch lots of packages from dlp. Today I noticed that there are many packages in a "broken" state. And most of them show the following conflict: > # > # spec file for package python-constantly > # > <<<<<<< .mine > # Copyright (c) 2022 SUSE LLC > ======= > # Copyright (c) 2023 SUSE LLC >>>>>>>> .new > # I guess that when modifying the spec file (to adapt something else, not this line) something[tm] changed the year automatically in the background, and hence this change is seen as "my change". Can I somehow prevent this kind of automatic changes somehow? Or can OBS be told to simply ignore changes in the boilerplate code? Having to fix dozens of packages is something I would like to avoid. :-) Kind Regards, Johannes -- 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

3 6

security updates for Debian:11
by Nicholas Brown 04 May '23

04 May '23

Look at the meta for the https://build.opensuse.org/project/show/Debian:11 project 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 also include the 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 sources. Thanks, Nick

2 2

ARM aarch64 items not published.
by Roger Oberholtzer 02 May '23

02 May '23

I have a couple projects that are building for OpenSUSE_Factory_ARM. They build for aarch64 and armv71. The builds succeed. But only the armv71 get published. In the OBS web gui Build Results, there is a lock symbol next to the aarch4 build results, while the armv71 has a green vehicle. I cannot see that I have configured anything different between these two architectures. So I have no idea why they are being treated differently. For example, this simple package: https://build.opensuse.org/package/show/home:rogeroberholtzer/libpixtend Any pointers are welcome. -- Roger Oberholtzer

2 3

Newly Documented API Endpoints for Comments, Status Messages and Staging
by Jacob Michalskie 02 May '23

02 May '23

Hi, The new OBS API documentation got expanded yet again to cover more endpoints. It's also easier to find as it's mentioned from the old documentation. Find out more details in the blog post https://openbuildservice.org/2023/05/02/api-docs-comments-status-staging/

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service May 2023