December 2021 - openSUSE Build Service

AW: expired certificate
by Mathias Radtke 07 Dec '21

07 Dec '21

Hi, Is your SLES 12 up to date? The SLES12SP4 - Pool and Updates repositories are being used and zypper refresh && zypper update tells me it is up to date. This is a freshly installed machine. The DST Root CA X3 was removed from our CA Bundle to avoid triggering this problem. Ciao, Marcus On Tue, Dec 07, 2021 at 01:07:09PM +0000, Mathias Radtke wrote: > Hi we are currently struggling with testing our sles12 packages on download.opensuse.org > > The certificate gets rejected because it is expired > > > openssl s_client -showcerts -connect download.opensuse.org:443 > > CONNECTED(00000003) > > depth=3 O = Digital Signature Trust Co., CN = DST Root CA X3 > > verify error:num=10:certificate has expired > > notAfter=Sep 30 14:01:15 2021 GMT > > --- > > Certificate chain > > 0 s:/CN=opensuse.org > > i:/C=US/O=Let's Encrypt/CN=R3 >

2 1

expired certificate
by Mathias Radtke 07 Dec '21

07 Dec '21

Hi we are currently struggling with testing our sles12 packages on download.opensuse.org The certificate gets rejected because it is expired openssl s_client -showcerts -connect download.opensuse.org:443 CONNECTED(00000003) depth=3 O = Digital Signature Trust Co., CN = DST Root CA X3 verify error:num=10:certificate has expired notAfter=Sep 30 14:01:15 2021 GMT --- Certificate chain 0 s:/CN=opensuse.org i:/C=US/O=Let's Encrypt/CN=R3 Regards Mathias -- opsi - Open PC-Server-Integration das Open Source Client-Management-System von uib gmbh Mathias Radtke Entwicklung eMail: m.radtke(a)uib.de Tel. +49 6131 / 27561-0 Fax +49 6131 / 27561-22 uib gmbh Bonifaziusplatz 1B 55118 Mainz Internet: https://uib.de https://opsi.org Geschftsfhrer: Dr. Detlef Oertel, Erol Ülükmen Handelsregister: Amtsgericht Mainz HRB 6942

2 1

Buildservice proxy
by Joop Boonen 07 Dec '21

07 Dec '21

Dear all, I'm testing the buildserver 2.10 to only connect, via a squid, proxy. I've nearly got it working completely. I've add to /etc/apache2/vhosts.d/obs.conf obs:~ # head /etc/apache2/vhosts.d/obs.conf setenv http_proxy "http://172.16.0.2:3128/" setenv https_proxy "http://172.16.0.2:3128/" setenv ftp_proxy "http://172.16.0.2:3128/" setenv no_proxy "localhost, 127.0.0.1" Listen 82 # May needed on old distributions or after an update from them. #Listen 443 # Passenger defaults obs:~ # and to: /srv/obs/run/worker/boot/BSConfig.pm obs:~ # tail /srv/obs/run/worker/boot/BSConfig.pm # our $geminabox_container = ''; # # public cloud uploader configuration # our $cloudupload_pubkey = "/etc/obs/cloudupload/_pubkey"; # default setting our $proxy = "http://172.16.0.2:3128/"; our $noproxy = "localhost, 127.0.0.1"; 1; obs:~ # One issue is still left. If I add a repo to a Project. https://obs/project/add_repository_from_default_list/test i.e. https://obs/project/add_repository_from_default_list/<project> Select a Repositry, OBS (I don't know which module) directly connects to: api.opensuse.org Can you please point me to te direction where I have to look. I'm willing to fix the issue. Regards, Joop.

2 2

The stucked s390X build in Factory.
by orville＠anislet.dev 07 Dec '21

07 Dec '21

Hello everyone. I found three packages in openSUSE:Factory:zSystems were stucked in building state for quite a while. They are ibus has been building for three full days and four hours, libksysguard5 for two days and one hour, and gcc11 for one day and two hours. Although it shows that they are building, they are actually both throwing up the same error over and over, for example gcc11 is BUG: workqueue lockup - pool cpus=4 node=0 flags=0x0 nice=0 stuck for 87381s And in particular, gcc11 basically blocks all other packages from being built, and has nearly 14,000 packages blocked in the factory because of it. That's not a normal situation, is it? Also where and how could I report it to the obs guys? Regrads, Orville Q. Song

2 1

incomplete submit request processing
by Olaf Hering 06 Dec '21

06 Dec '21

Processing of rq921282 is incomplete, the _link in the origin prj was not updated. Where does this need to be reported: - in openSUSE/open-build-service? - in the tooling around open-build-service? - somewhere else? Olaf

1 0

Creating unofficial packages for the Darling compatibility layer
by Hamish McIntyre-Bhatty 04 Dec '21

04 Dec '21

Hi there, I'm thinking of using OpenSUSE build service for building and hosting unofficial packages for darlinghq.org. However, these builds take a few hours, and can temporarily use up to 15GB disk space. I couldn't find anything on the wiki about service use limitations, so I wanted to check if this is okay before I do it, and not going to get me banned or something. Thanks, Hamish

3 6

Re: EXT:Re: Multiple Factory image breakages
by Olsson, Dennis 02 Dec '21

02 Dec '21

Hi Dominique, Where do I find this: > ...(as announced in the weekly reviews)... A link to this would be neat. ;-) Cheers/Dennis DFS Deutsche Flugsicherung GmbH * Am DFS-Campus * 63225 Langen * Tel.: +49 6103 707-0 * Sitz der Gesellschaft: Langen/Hessen * Zuständiges Registergericht: AG Offenbach am Main, HRB 34977 * Vorsitzende des Aufsichtsrats: Antje Geese * Geschäftsführer: Arndt Schoenemann (Vors.), Dr. Kerstin Böcker, Dirk Mahns, Friedrich-Wilhelm Menge * www.dfs.de<http://www.dfs.de> Sollten Sie nicht der richtige Empfänger dieser E-Mail sein, löschen Sie diese bitte.

2 1

Multiple Factory image breakages
by Nicolas FORMICHELLA 02 Dec '21

02 Dec '21

Hello, Some Factory ARM and PPC64/RISCV64 images in my projects ([1],[2] images are broken and all build fails on a error: failed to exec scriptlet interpreter /bin/sh: No such file or directory [1]: https://build.opensuse.org/package/live_build_log/utilities/nnn/openSUSE_Fa… (armv7, aarch64 and ppc64 fails there) [2]: https://build.opensuse.org/package/live_build_log/home:stig124:branches:dev… Can someone have a look? Regards, Nicolas FORMICHELLA

2 1