July 2024 - openSUSE Build Service - openSUSE Mailing Lists

Slow login to OBS and 504 errors
by Martin Hooper 22 Jul '24

22 Jul '24

Is the global IT problem effecting OBS?? Slow logins leading to 504 Gateway Timeout while waiting to login...

2 2

Re: Can I build containers based on hub.docker.com images?
by Dan Čermák 16 Jul '24

16 Jul '24

Martin Hooper <martin(a)mjhooper.co.uk> writes: > On 16/07/2024 13:53, Dan Čermák wrote: > >> If I had to guess, then I'd blame dockerhub rate limiting. But this >> won't work anyway, as the buildservice cannot build container images >> based on Alpine (it does not support the apk package manager). >> >> >> Cheers, >> >> Dan >> > > Ah thought that might be the case... No, OBS can only build containers based on distributions that it supports (this includes Ubuntu/Debian based ones, RPM based ones and Archlinux). Also, the build has to run in full network isolation, i.e. no `curl | sudo bash`. Cheers, Dan -- Dan Čermák <dcermak(a)suse.com> Software Engineer Development tools SUSE Software Solutions Germany GmbH Frankenstr. 146 90461 Nürnberg Germany www.suse.com Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)

2 2

New Blog Post! Notifications Filter by Request State
by Saray Cabrera Padron 16 Jul '24

16 Jul '24

Hello! We are back with another improvement on filters! This time, we introduced the possibility of filtering by request state on the notifications page. Please read more in https://openbuildservice.org/2024/07/15/filter_by_request_state. Kind regards, The Build Solutions Team -- Saray Cabrera Padrón scabrerapadron(a)suse.com | scabrerapadron(a)suse.de Build Solutions Team SUSE Software Solutions Germany GmbH

1 0

Re: Can I build containers based on hub.docker.com images?
by Dan Čermák 16 Jul '24

16 Jul '24

Martin Hooper <martin(a)mjhooper.co.uk> writes: > On 16/07/2024 09:18, Dan Čermák wrote: >> Martin Hooper <martin(a)mjhooper.co.uk> writes: >> >>> Can I build docker images that use images hosted on hub.docker.com? >> >> Maybe. The buildservice supports to build against registries that have >> been setup as projects. At the moment I am aware of: >> - registry.suse.com as SUSE:Registry >> - registry.opensuse.org as openSUSE:Registry (albeit this one is kinda >> pointless, as registry.opensuse.org is OBS itself) >> >> and the one you're looking for as Docker:Registry [1]. > > Thanks Dan - I put them both in as: > > <repository name="containers_arm" rebuild="local"> > <path project="Docker:Registry" repository="standard"/> > <path project="openSUSE:Templates:Images:Tumbleweed" > repository="containers_arm"/> > <arch>aarch64</arch> > </repository> > <repository name="containers" rebuild="local"> > <path project="Docker:Registry" repository="standard"/> > <path project="openSUSE:Templates:Images:Tumbleweed" > repository="containers"/> > <arch>x86_64</arch> > </repository> > > and the dockerfile from line is: > > FROM library/alpine:latest > > and it is blocked saying it is waiting for container to appear > but it looks like it never does... If I had to guess, then I'd blame dockerhub rate limiting. But this won't work anyway, as the buildservice cannot build container images based on Alpine (it does not support the apk package manager). Cheers, Dan -- Dan Čermák <dcermak(a)suse.com> Software Engineer Development tools SUSE Software Solutions Germany GmbH Frankenstr. 146 90461 Nürnberg Germany www.suse.com Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg)

1 0

Can I build containers based on hub.docker.com images?
by Martin Hooper 16 Jul '24

16 Jul '24

Can I build docker images that use images hosted on hub.docker.com? My google-fu is failing me or at least not giving me the right answers if there are any... My guess is no but no harm in asking... :) Cheers in advance....

3 2

Building containers
by Martin Hooper 15 Jul '24

15 Jul '24

I have a dockerfile in a git repo which I have cloned to my Tumbleweed vm... 1. How do I get the dockerfile and associated files to build with obs 2. the dockerfile is based on the alpine docker image - Will I be able to build that straight off from docker hub or will I have to figure out how to do it on Opensuse? Also when I create an image from the left menu nd choose one of the container options how do I get into my project rather than a subproject?

1 0

Building a container image fails: "container normailzation failed: no manifest.json file found"
by Johannes Kastl 13 Jul '24

13 Jul '24

Hi all, maybe someone can spot what I am missing. > https://build.opensuse.org/package/show/home:ojkastl_buildservice:distrobox… No matter what I do, how often I compare my prjconf with Richard's where he builds some distrobox images, I always end up with the same error: "container normailzation failed: no manifest.json file found" Does anyone have an idea where this comes from? The typo ("normailzation") should make searching easier, but it does not... Kind Regards, Johannes

3 5

Multiple pubkeys for an imported project, how?
by Stefan Seyfried 09 Jul '24

09 Jul '24

Hi all, I am right now importing SLES15-SP6 into my local OBS instance. The repos are dod'd from my local SMT server, the setup is like this (with quite some more, basically all available SLES modules ;-): <project name="SLES15-SP6:GA"> <title>SUSE Linux Enterprise Server 15 SP6</title> <description>SLES15-SP6 without updates</description> <link project="SLES15-SP5:Update"/> <person userid="seife" role="maintainer"/> <build> <disable/> </build> <publish> <disable/> </publish> <debuginfo> <disable/> </debuginfo> <repository name="standard"> <path project="SLES15-SP6:GA" repository="SLE-Module-Basesystem"/> ... <path project="SLES15-SP6:GA" repository="SLE-Manager-Tools"/> <arch>x86_64</arch> </repository> <repository name="SLE-Module-Basesystem"> <download arch="x86_64" url="http://repo:50000/repo/SUSE/Products/SLE-Module-Basesystem/15-SP6/x86_64/pr…" repotype="rpmmd"/> <arch>x86_64</arch> </repository> ... <repository name="SLE-Manager-Tools"> <download arch="x86_64" url="http://repo:50000/repo/SUSE/Products/SLE-Manager-Tools/15/x86_64/product/" repotype="rpmmd"/> <arch>x86_64</arch> </repository> </project> After configuring OBS for a new SLES SP, I usually copy the newest SUSE package signing key to /srv/obs/projects/SLES15-SP6:GA.pkg/_pubkey and then accept it on the first local "osc build SLES15-SP6" invocation. Not this time. Apparently SLES15-SP6 has packages with different keys signed (new 150600 packages with key id f74f09bc3fa1d6ce, old packages up to 150500 with key ID 70af9e8139db7c82), and all my attempts to put multiple keys into _pubkey failed. What I have tried: * cat all pubkey files together into _pubkey => only the first one is used. * start with an empty keyring, gpg --import all gpg-pubkeys from the openSUSE-buildkey, then gpg --export --armor > _pubkey => no key is found The local osc-downloaded copy always contains the full set of keys I added on OBS, in fact the e <repository name="SLE-Product-WE"> <download arch="x86_64" url="http://repo/SUSE/Products/SLE-Product-WE/15-SP6/x86_64/product/" repotype="rpmmd"/> <arch>x86_64</arch> </repository> <repository name="SLE-Product-SLES"> <download arch="x86_64" url="http://repo/SUSE/Products/SLE-Product-SLES/15-SP6/x86_64/product/" repotype="rpmmd"/> <arch>x86_64</arch> </repository> <repository name="SLE-Module-Web-Scripting"> <download arch="x86_64" url="http://repo/SUSE/Products/SLE-Module-Web-Scripting/15-SP6/x86_64/product/" repotype="rpmmd"/> <arch>x86_64</arch> </repository> <repository name="SLE-Module-Server-Applications"> <download arch="x86_64" url="http://repo/SUSE/Products/SLE-Module-Server-Applications/15-SP6/x86_64/prod…" repotype="rpmmd"/> <arch>x86_64</arch> </repository> <repository name="SLE-Module-SAP-Applications"> <download arch="x86_64" url="http://repo/SUSE/Products/SLE-Module-SAP-Applications/15-SP6/x86_64/product/" repotype="rpmmd"/> <arch>x86_64</arch> </repository> <repository name="SLE-Module-Python3"> <download arch="x86_64" url="http://repo/SUSE/Products/SLE-Module-Python3/15-SP6/x86_64/product/" repotype="rpmmd"/> <arch>x86_64</arch> </repository> <repository name="SLE-Module-Python2"> <arch>x86_64</arch> </repository> <repository name="SLE-Module-Public-Cloud"> <download arch="x86_64" url="http://repo/SUSE/Products/SLE-Module-Public-Cloud/15-SP6/x86_64/product/" repotype="rpmmd"/> <arch>x86_64</arch> </repository> <repository name="SLE-Module-Legacy"> <download arch="x86_64" url="http://repo/SUSE/Products/SLE-Module-Legacy/15-SP6/x86_64/product/" repotype="rpmmd"/> <arch>x86_64</arch> </repository> <repository name="SLE-Module-HPC"> <download arch="x86_64" url="http://repo/SUSE/Products/SLE-Module-HPC/15-SP6/x86_64/product/" repotype="rpmmd"/> <arch>x86_64</arch> </repository> <repository name="SLE-Module-Development-Tools-OBS"> <arch>x86_64</arch> </repository> <repository name="SLE-Module-Development-Tools"> <download arch="x86_64" url="http://repo/SUSE/Products/SLE-Module-Development-Tools/15-SP6/x86_64/produc…" repotype="rpmmd"/> <arch>x86_64</arch> </repository> <repository name="SLE-Module-Desktop-Applications"> <download arch="x86_64" url="http://repo:50000/repo/SUSE/Products/SLE-Module-Desktop-Applications/15-SP6…" repotype="rpmmd"/> <arch>x86_64</arch> </repository> <repository name="SLE-Module-Containers"> <download arch="x86_64" url="http://repo:50000/repo/SUSE/Products/SLE-Module-Containers/15-SP6/x86_64/pr…" repotype="rpmmd"/> <arch>x86_64</arch> </repository> xact same _pubkey file (same checksum). So how do I add multiple pubkeys to a project? Is this an OBS or an osc problem? Best regards and thanks in advance, seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman

1 0

Project Linking Help
by Justin Hammond 08 Jul '24

08 Jul '24

Hi, I want to rebuild one of the RiscV JeOS images, but I need to downgrade some packages (mesa etc) to vendor supplied version so I've been looking at the best way to achieve this, but I'm hitting a bit of a wall. Looking over the Wiki etc, I understand that a Project Link is probably the best approach, but due to the number of packages involved, linking to openSUSE:Factory:RISCV on build.opensuse.org puts me "over quota" which is understandable. I've proceeded to setup my own install of OBS, setup an interconnect to api.opensuse.org, and I can successfully build images locally with my own kernel sources etc. All good so far. Now I've created a new package for my vendor mesa, (basically copied a spec file from a OpenSUSE:Factory version of mesa that matched the version the vendor supplied) and it also builds successfully, but the dependencies of Mesa are not getting rebuilt, and thus, fail in the final image. When I attempt to add a project link and specify the repositories as linkedbuild=localdep, it wants to rebuild all 15,000 packages in openSUSE:Factory:RISCV Is there a bit of a step-by-step instruction on how to get this working correctly? I would have thought that it would rebuild mesa, and any dependants on mesa only, and not things like glibc/gcc etc etc etc

3 3

Building debs from a spec file
by Martin Hooper 07 Jul '24

07 Jul '24

Does anyone have any documentation for absolute beginners on building debs from spec files using debbuild? I have some font rpms that build just fine and I want to make debs out of them as well. or am I barking up the wrong tree and will have to look up the deb packaging docs instead?

3 7