September 2023 - openSUSE Build Service

Black-listed or otherwise illegal to distribute packages on OBS
by Atri Bhattacharya 12 Sep '23

12 Sep '23

Hi, It seems there is a proliferation of black-listed (for example, x264, etc. according to [1]), or simply illegal to re-distribute (for example, skype, according to 8.iv in [2]) packages made available on build.o.o by packagers who really should know better. A simple search may be used to check where these packages are, so I am eschewing a list here. What mechanism, if any, do OBS admins have to clean-up these packages (and on repeat offences, perhaps the offending packagers [3]) so that openSUSE does not end up on the wrong side of the law perchance? See also Stefan's mail on the devel mailing list [4] on Thu, 24 Nov 2022. [1] <https://en.opensuse.org/openSUSE:Build_Service_application_blacklist> [2] <https://www.microsoft.com/en-us/servicesagreement/> [3] Without taking names, I know of one OBS package that was deleted after my pointing out of its illegality, but then 'undeleted' after a while. [4] <https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/… > -- Atri

1 0

OBS-Service obs-service-cargo_audit failing locally for kubie
by Johannes Kastl 12 Sep '23

12 Sep '23

Hi all, (reported as issue https://github.com/openSUSE/obs-service-cargo_audit/issues/10, ) I was recently trying to upgrade kubie to 0.22.0, but the OBS service obs-service-cargo_audit failed on me. The error was extremely verbose...: > [...] > INFO:obs-service-cargo_vendor:Starting compression ... > INFO:obs-service-cargo_vendor:Success > INFO:obs-service-cargo_audit: Running OBS Source Service 🛒: obs-service-cargo_audit > Aborting: service call failed: /usr/lib/obs/service/cargo_audit --srcdir kubie --outdir /home/Buildservice/Branches/Branch_devel_kubic/kubie/tmpb5aunh4a.cargo_audit.service I asked Robert to run this on his machine, and it worked for him. I tested again today and it still bails out. We have/had the same version of the package installed, so it might be something other than the actual package. Where could we start looking? 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 1

New Blog Post about new Build Results Summary
by Eduardo Navarro 08 Sep '23

08 Sep '23

Hello everybody, The Build Solutions team has worked on the request workflow redesign again. This time we add the build results summary. You can find more details in our latest blog post: https://openbuildservice.org/2023/09/08/request-workflow-redesign/ Kind regards, The Build Solutions Team

1 0

How to handle packages required for installation, when building against another project?
by Johannes Kastl 08 Sep '23

08 Sep '23

Hi all, I would like to provide Ansible packages for SLES15/Leap15 using the "new" python3.11 stack. I can build against devel:languages:python:backports, which has the sle15_python_module_pythons enabled and builds all packages with the python3.11 stack. I get most of the dependencies for Ansible & Co from there, but only for build time dependencies. Once I want to install the packages, I would need to also add the devel:languages:python:backports repository on the machine, which might mean I get updates for other packages, too. Is there a nice way to make the packages available without rebuilding each and everyone of them? I know I can aggregate packages, but AFAIK this only works within the same project (due to the GPG signature on the packages, IIRC). Until now I went with the rebuild-approach, as there were lots of packages that needed to be adapted or fixed along the way (subunit, etc.) anyway. But for the "official" packages in systemsmanagement:ansible (or a subproject) I would like to reduce the load on the OBS. 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 4

HELP: d:l:R:autoCRAN in broken state as a whole
by Detlef Steuer 04 Sep '23

04 Sep '23

Dear build.opensuse.org admins, since some time the repo devel:languages:R:autoCRAN is in broken state. All of the 20000 + x packages. The repo brings all of CRAN, cran.r-project.org to the Suse ecosystem in a completely automatic way. It enables the installation of R packages as binaries instead of local compilation. When I started the project three years ago the repo got a quota of 20000 packages, which no longer is enough, which in case lead to the broken state. Raising this limit to say 25000 packages would probably be enough for the next 3-5 years and to get the project running again. I've asked for help three weeks ago, but got no response at all. If the buildservice is not willing anymore to host such a project, even that would be an important information for me. Feeling quite helpless right now. Any feedback highly appreciated. Detlef -- "Wozu leben wir, wenn nicht dazu, uns gegenseitig das Leben einfacher zu machen. (George Eliot)" Dr. Detlef Steuer Helmut-Schmidt-Universität Fakultät WiSo Holstenhofweg 85 22043 Hamburg Tel: 040/6541-2819 mail: steuer(a)hsu-hh.de

2 1

Debian Testing setup errors processing tex-common
by Rosanne DiMesio 03 Sep '23

03 Sep '23

Building wine-staging Debian Testing packages fails setting up the container: [ 143s] dpkg: error processing package tex-common (--configure): [ 143s] installed tex-common package post-installation script subprocess returned error exit status 1 [ 143s] Processing triggers for udev (254.1-2) ... [ 143s] Processing triggers for debianutils (5.8-1) ... [ 143s] Processing triggers for fontconfig (2.14.2-4) ... [ 143s] Errors were encountered while processing: [ 143s] tex-common [ 143s] first configure attempt failed, trying again... [ 143s] Setting up tex-common (6.18) ... [ 143s] Running mktexlsr. This may take some time... done. [ 144s] Running updmap-sys. This may take some time... done. [ 144s] Running mktexlsr /var/lib/texmf ... done. [ 144s] Building format(s) --all. [ 200s] This may take some time... [ 200s] fmtutil failed. Output has been stored in [ 200s] /tmp/fmtutil.29zkybXq Build was on the OBS, so there is no tmp file. Build logs are at https://build.opensuse.org/package/show/Emulators:Wine:Debian/wine-staging -- Rosanne DiMesio <dimesio(a)earthlink.net>

1 1

Making self-hosted OBS not rely on build.opensuse.org availability
by Oliver Smith 01 Sep '23

01 Sep '23

Hello, for the Osmocom project we are hosting our own OBS instance. The projects in our instance depend on build.opensuse.org's instance for the base distributions. For example, from one meta config: <repository name="Debian_12"> <path project="openSUSE.org:Debian:12" repository="standard"/> <arch>x86_64</arch> </repository> As I understand, this is the reason that during recent outages related to openSUSE's OBS instance moving to a different datacenter, our OBS didn't build packages. After trying to start a build, in scheduler_x86_64.log: sorting 68 packages checking packages - libasn1c (interconnect error: rpc timeout) - libgtpnl (interconnect error: rpc timeout) - libosmo-abis (interconnect error: rpc timeout) … So I'm wondering, is there a way to cache/sync the base distribution information so our builds keep working even if build.opensuse.org is currently not reachable / we have a network outage etc? Thanks! Best regards, -- - Oliver Smith <osmith(a)sysmocom.de> https://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

4 3