August 2021 - openSUSE Build Service - openSUSE Mailing Lists

Building against modules on CentOS Stream 8 isn't working?
by Neal Gompa 13 Aug '21

13 Aug '21

Hello, I'm trying to build some PHP extension backports from Fedora on CentOS Stream 8, but OBS is marking all of them as excluded and won't start building anything... You can see my OBS project here: https://build.opensuse.org/project/show/isv:Datto:Backports:PHP_Extensions What's going on? -- *Neal Gompa* Senior DevOps Engineer Datto, Inc. www.datto.com

2 2

Howto build XXX-32 - packages
by Dr.-Ing. Dieter Jurzitza 12 Aug '21

12 Aug '21

Dear listmembers, I tried recently to branch wine in oder to create a test build. However, unlucky me, similar to my local "rpmbuild" environment the 32 - bit compatibility layer is not generated - but crucial to have. Is there any specific configuration required to have the build generate the compatibility layer as well? Can some gentle person provide a pointer on how to get it generated? Thank you for looking into this, take care Dieter Jurzitza -- ----------------------------------------------------------- Dr.-Ing. Dieter Jurzitza 76131 Karlsruhe

3 4

x86_64 disk space errors
by Avindra G 11 Aug '21

11 Aug '21

I've been having trouble getting deno to build since v1.9.0 (April 13th, 2021) on x86_64. Tried various _constraints values, but the job is failing with the same error: [ 3311s] LLVM ERROR: IO failure on output stream: No space left on device [ 3311s] /.build/build-vm: line 460: echo: write error: No space left on device [ 3312s] error: could not compile `deno` [ 3312s] https://build.opensuse.org/package/show/devel:languages:javascript/deno#com… Can anyone advise? Thanks, avindra goolcharan

3 6

Please re-add maintainer permission for user "alvistack"
by Wong Hoi Sing Edison 10 Aug '21

10 Aug '21

Dear support, Sorry that I carelessly remove myself (alvistack) from maintainer of following projects, when updating project repositories with "Meta" tab: - https://build.opensuse.org/project/show/home:alvistack - https://build.opensuse.org/project/show/home:alvistack:rust-lang I couldn't self-manage it because now I had no permission for my own project. May someone give a hand to re-add maintainer permission for me? Regards, Edison Wong

3 5

Re: Error "Version is invalid" for JeOS 15 and 15SP1
by Vincent Moutoussamy 10 Aug '21

10 Aug '21

Hi, Anybody? Pretty please let me know how to proceed here with this request. Have a nice day, Regards, -- Vincent Moutoussamy SUSE Beta Program Manager JeOS Technical Project Manager Paris, France From: kiwi-internal <kiwi-internal-bounces+vmoutoussamy=suse.com(a)suse.de> on behalf of Vincent Moutoussamy <vmoutoussamy(a)suse.com> Date: Monday, 21 June 2021 at 16:16 To: kiwi-internal(a)suse.de <kiwi-internal(a)suse.de>, opensuse-buildservice(a)opensuse.org <opensuse-buildservice(a)opensuse.org> Cc: jeos-internal(a)suse.de <jeos-internal(a)suse.de> Subject: Re: Error "Version is invalid" for JeOS 15 and 15SP1 Hi, Please be aware that I wanted to showcase SUSE Studio Express to a JeOS SLES Customer and not a small one… But I don’t feel comfortable explaining why there is this error, which is not an error but a warning. So a reply from you would be appreciated, Thanks, Regards, -- Vincent Moutoussamy SUSE Beta Program Manager JeOS Technical Project Manager Paris, France From: kiwi-internal <kiwi-internal-bounces+vmoutoussamy=suse.com(a)suse.de> on behalf of Vincent Moutoussamy <vmoutoussamy(a)suse.com> Date: Tuesday, 15 June 2021 at 16:24 To: kiwi-internal(a)suse.de <kiwi-internal(a)suse.de>, opensuse-buildservice(a)opensuse.org <opensuse-buildservice(a)opensuse.org> Cc: jeos-internal(a)suse.de <jeos-internal(a)suse.de> Subject: Re: Error "Version is invalid" for JeOS 15 and 15SP1 Hi, I’m still seeing the “Version is invalid” when trying to customize JeOS images on https://build.opensuse.org/image_templates As we are still using in our JeOS templates: <version>15.2</version> And not <version>15.2.0</version> But in the kiwi documentation I see “<version>15.0</version> » https://osinside.github.io/kiwi/concept_and_workflow/profiles.html?highligh… but <version>1.2.3</version> in https://osinside.github.io/kiwi/image_description/elements.html#preferences thus it’s not clear if X.Y.Z is “mandatory” or not. Last but not least this error message is not blocking the customization or building the image however it’s potentially highly confusing for the users. Therefore if X.Y.Z is not enforced and Kiwi/IBS/OBS works fine with X.Y, could we please expect to have a solution that would just hide or remove this “Version is invalid” warning from the webui? Have a nice day, Regards, -- Vincent Moutoussamy SUSE Beta Program Manager JeOS Technical Project Manager Paris, France From: Vincent Moutoussamy <vmoutoussamy(a)suse.com> Date: Wednesday, 11 September 2019 at 14:15 To: kiwi-internal(a)suse.de <kiwi-internal(a)suse.de> Subject: Fwd: Error "Version is invalid" for JeOS 15 and 15SP1 Hi there, I thought the following issue was something for the OBS team but they told me that it should be something for you. Could you please confirm and give your inputs? Thanks Regards, -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager Begin forwarded message: From: Vincent Moutoussamy <vmoutoussamy(a)suse.com<mailto:vmoutoussamy@suse.com>> Subject: Error "Version is invalid" for JeOS 15 and 15SP1 Date: 11 September 2019 at 13:08:29 CEST To: opensuse-buildservice(a)opensuse.org<mailto:opensuse-buildservice@opensuse.org> Hi there, When selecting "SLE 15 JeOS and SLE 15 SP1 JeOS” from https://build.opensuse.org/image_templates and trying to “create appliance”, I get the following error message: Kiwi File 'JeOS.kiwi' has errors: • Preferences: • Version is invalid on page like: https://build.opensuse.org/package/view_file/home:gameboy974:branches:SUSE:… my-kiwi-templates-SLES15-JeOS/JeOS.kiwi?expand=1 I think this is because the kiwi file contains the following, instead of 15.0.0: <preferences profiles="kvm-and-xen"> <version>15.0</version> At least it works for openSUSE and their kiwi files contains: <preferences profiles="kvm-and-xen"> <version>15.1.0</version> So my question is it really a hard requirement to have version as X.Y.Z instead of X.Y or is this a bug? Regards, -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager

1 0

SLE_15 SP3 on private OBS-instance ?
by Christof Hanke 10 Aug '21

10 Aug '21

Hello, I see SLE-15-SP3 as a valid repository on the official OBS. On our private instance, the newest SLE-repo is SLE-15-SP2. LEAP 15.3 is availbale, but no SLE-15-SP3. I there anything to do to enable SLES 15 SP3 ? Many thanks, Christof -- Christof Hanke, Max-Planck Computing & Data Facility MPCDF, Gießenbachstr. 2, D-85748 Garching, Germany Tel: +49-89-3299-1041 E-Mail: christof.hanke(a)mpcdf.mpg.de Fax: +49-89-3299-1301 Web: http://www.mpcdf.mpg.de

2 2

SLE_15 SP3 on private OBS-instance ?
by Christof Hanke 09 Aug '21

09 Aug '21

Hello, I see SLE-15-SP3 as a valid repository on the official OBS. On our private instance, the newest SLE-repo is SLE-15-SP2. LEAP 15.3 is availbale, but no SLE-15-SP3. Is there anything to do on my side to enable SLES 15 SP3 ? Many thanks, Christof -- Christof Hanke, Max-Planck Computing & Data Facility MPCDF, Gießenbachstr. 2, D-85748 Garching, Germany Tel: +49-89-3299-1041 E-Mail: christof.hanke(a)mpcdf.mpg.de Fax: +49-89-3299-1301 Web: http://www.mpcdf.mpg.de

1 0

Adding "Everything" for openEuler 20.03
by Julio Gonzalez 08 Aug '21

08 Aug '21

Right now: https://build.opensuse.org/projects/openEuler:20.03/meta Has OS, updates (which in fact is disabled by default at least on 20.03-SP1), EPOL and EPOL-updates (are they broken? I see a red warning sign at https:// build.opensuse.org/project/show/openEuler:20.03) Question is: can the repository "Everything" be added as well? https://repo.openeuler.org/openEuler-20.03-LTS-SP1/everything/${arch}/ Most likely the same should be done for https://build.opensuse.org/project/show/openEuler:21.03 Thanks. -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

2 3

OBS Server 2.10.11 released
by Frank Schreiner 06 Aug '21

06 Aug '21

Hi, we proudly announce OBS Server 2.10.11 release Features ======== * OBS Appliance Images: - Upgrade base distribution from openSUSE 15.1 to 15.3 * obs-server - multiple cpu flags now supported by dispatcher - support cpu flag exclude constraint - Add another ampere variant for aarch32 support Bugfixes ======== * Frontend: - Update rails to fix a license issue in one of its dependencies - Fix potential XSS vulnerability in jQuery

2 1

ARMv7 build has been broken in private OBS instance
by Matwey V. Kornilov 06 Aug '21

06 Aug '21

Hi, I am running a private OBS instance with an ARM worker based on Cortex-A53 board. obs-api-2.10.10-lp152.63.1.noarch Worker version is obs-worker-2.11~alpha.20210609T113256.127f886c97-12468.1.noarch Everything worked fine until today I found that the worker is broken. It cannot boot the KVM machine. I see the silence after: [ 32s] /usr/bin/qemu-system-aarch64 -nodefaults -no-reboot -nographic -vga none -cpu host,aarch64=off -enable-kvm -M virt,gic-version=host -object rng-random,filename=/dev/random,id=rng0 -device virtio-rng-device,rng=rng0 -runas qemu -net none -kernel /var/cache/obs/worker/root_1/.mount/boot/kernel -initrd /var/cache/obs/worker/root_1/.mount/boot/initrd -append root=/dev/disk/by-id/virtio-0 rootfstype=ext4 rootflags=noatime ext4.allow_unsupported=1 mitigations=off panic=1 quiet no-kvmclock elevator=noop nmi_watchdog=0 rw rd.driver.pre=binfmt_misc console=ttyAMA0 init=/.build/build -m 3072 -drive file=/var/cache/obs/worker/root_1/root,format=raw,if=none,id=disk,cache=unsafe -device virtio-blk-device,drive=disk,serial=0 -drive file=/var/cache/obs/worker/root_1/swap,format=raw,if=none,id=swap,cache=unsafe -device virtio-blk-device,drive=swap,serial=1 -serial stdio -chardev socket,id=monitor,server,nowait,path=/var/cache/obs/worker/root_1/root.qemu/monitor -mon chardev=monitor,mode=readline -smp 4 Then I've found that kernel and initrd images are for aarch64 architecture in spite of -cpu host,aarch64=off argument. This is a case of my qemu failure. I suppose this is somehow connected to the new upstream OBS ARM workers, which are not able to run armv7 kernels inside VMs. Is it a known issue? How could I recover service operation? -- With best regards, Matwey V. Kornilov

2 4