October 2019 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] RHEL 8
by Stephan Duehr 09 Dec '19

09 Dec '19

Hi, just wanted to ask if/when you are planning to add RHEL 8? As of https://developers.redhat.com/blog/2019/05/07/red-hat-enterprise-linux-8-no… RHEL 8 was released on May 7, 2019 Regards, Stephan Dühr -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 2

[opensuse-buildservice] Cross Build Failure to Raspbian_9.0 arm7l
by Mark Grant 29 Nov '19

29 Nov '19

Hi, On an x86-64 openSUSE Leap 15.1 system I am trying to cross-build a package with osc to Raspbian 9.0 arm7l using the following command osc build Raspbian_9.0 arm7l It fails with the following build log. https://pastebin.com/raw/yQp0Kfyc An attempt for Raspbian_10 fails in the same manner. Any help would be appreciated. Regards, Mark -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 2

[opensuse-buildservice] Public Key not available SLE_12_SP3 s390x
by Usman Haider 27 Nov '19

27 Nov '19

Hi, I am new and trying local build on s390x with SLE_12_SP3 using the following command sudo osc build but I get the public key not available for many packages. You can see the output by clicking the following link https://pastebin.com/YBQk3vGe I know that I can use --noverify option to bypass this and builds complete successfully when I use --noverify option but how can I fix this? What will happen if I don't fix it? -- Usman -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 9

[opensuse-buildservice] arm builds on local OBS
by Srivats P 11 Nov '19

11 Nov '19

Hi, At the onset, thanks for your wonderful work on OBS! I have a local OBS instance (using the appliance download) which currently only builds x86_64 binaries. I'm now trying to build a Raspbian armv7l binary, but running into issues - * The Status Monitor shows both i586 and armv7l as "dead". Do I need to enable these arch in some config file? Or is some OBS service failing at startup that I need to start manually? * The project page shows the arm and i586 repository state as "Unknown", while the package page does not show that distro/arch combinations at all - not even when I click on "show excluded" * I don't have a armv7 worker, but from some googling it looked to me that armv7 can be built on a x86_64 worker using cross-builds. After further googling, I added the following to my project config, but still no luck - %ifarch armv7l Preinstall: qemu-linux-user Runscripts: qemu-linux-user Hostarch: x86_64 Macros: %qemu_user_space_build 1 :Macros %endif Any help or suggestions is highly appreciated. Thanks in advance, Srivats -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 9

[opensuse-buildservice] I can't trigger rebuild of package I'm maintainer of.
by Adam Mizerski 11 Nov '19

11 Nov '19

As in the title. I'm maintaining network:cryptocurrencies/ethereum-cpp. It has a test suite, which despite my efforts likes to randomly fail. When i try to trigger rebuilding, I get error: "Error while triggering rebuild for network:cryptocurrencies/ethereum-cpp: No permission to modify project 'network:cryptocurrencies' for user 'etamPL'." Obviously, I don't want to modify project. I just want to trigger rebuild. Is this desired effect, or should I report a bug? -- Adam Mizerski

3 4

[opensuse-buildservice] Need help with signing error in priv obs installation
by Stefan Botter 05 Nov '19

05 Nov '19

Hi all, I have a problem with my own installation of obs 2.10. Building works, but all builds are stuck in the "signing" phase. /srv/obs/log/signer.log shows lines like these: ====== gpg: decryption failed: No secret key sign failed: 256 - checking digest /srv/obs/jobs/x86_64/userweb::openSUSE_Leap_15.1::pure-ftpd-c0ae603b4c4953d7a0b214f7c15554b7:dir/pure-ftpd-1.0.47-lp151.95.1.src.rpm: digests OK sign failed: sign /srv/obs/jobs/x86_64/userweb::openSUSE_Leap_15.1::pure-ftpd-c0ae603b4c4953d7a0b214f7c15554b7:dir/pure-ftpd-1.0.47-lp151.95.1.src.rpm failed ==== All repositories are affected, the master GPG key is still valid until some time in 2021. Which key is at fault, how do I identify the cause? Thank you for pointers, Stefan -- Stefan Botter zu Hause Bremen

4 4

[opensuse-buildservice] KVM worker setup
by Morschhäuser, Mark 01 Nov '19

01 Nov '19

Hi, how do I need to configure an OBS worker to use KVM instead of a chroot? I checked the documentation but did not find information about that topic. I tried the following settings in /etc/sysconfig/obs-server and restarted the obsworker: OBS_VM_TYPE="kvm" OBS_VM_KERNEL="/boot/vmlinuz" OBS_VM_INITRD="/boot/initrd" OBS_VM_DISK_AUTOSETUP_ROOT_FILESIZE="4096" OBS_VM_DISK_AUTOSETUP_SWAP_FILESIZE="1024" OBS_VM_DISK_AUTOSETUP_FILESYSTEM="ext4" OBS_VM_DISK_AUTOSETUP_MOUNT_OPTIONS="" OBS_VM_USE_TMPFS="no" OBS_VM_CUSTOM_OPTION="" The OBS_WORKER_* settings are empty, I don't know what they are about. The WebUI tells me "scheduled" with overlay "waiting for <n> compliant workers <n> of them are bad". In screen -x I see fetching sources, packages, building... VM_ROOT: /mnt/ramdisk/obs/worker/root_1/root, VM_SWAP: /mnt/ramdisk/obs/worker/root_1/swap Creating /mnt/ramdisk/obs/worker/root_1/root (4096M) 0+0 records in 0+0 records out 0 bytes copied, 2.8003e-05 s, 0.0 kB/s fallocate: fallocate failed: No space left on device (the path is actually not a ramdisk, just an ordinary file system, everything there belongs to root who is also owner of the obsworker processes and there are 80GB disk free). I also see the following messages: send_state http://<myserver>: 404 remote error: Not Found They even appear when I use the build chroot configuration (which works so far - unless packages use ports in the %check section and collide with other build instances). Best regards, Mark -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 3

[opensuse-buildservice] Fedora 31 i586 Wine builds unresolvable
by Rosanne DiMesio 31 Oct '19

31 Oct '19

Trying to build Wine for Fedora 31 (https://build.opensuse.org/package/show/Emulators:Wine:Fedora/wine-devel), the i586 build shows as unresolvable due to missing pretty much everything--not just Wine's specific build dependencies, but basic build tools as well. I know Fedora has dropped bootable i586 images from 31, but everything I've read says they will continue to provide the 32 bit packages needed to support Wine. Is the i586 environment just not set up yet on the OBS? -- Rosanne DiMesio <dimesio(a)gmail.com> -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 8

[opensuse-buildservice] Failed to resolve "product_flavor(openSUSE) needed by openSUSE-release" in Dockerfile based container build (Tumbleweed)
by Oliver Kurz 31 Oct '19

31 Oct '19

since some days containers in OBS using the Dockerfile fail to fail to resolve due to ``` have choice for product_flavor(openSUSE) needed by openSUSE-release: openSUSE- release-appliance-custom openSUSE-release-appliance-docker openSUSE-release- appliance-hyperv openSUSE-release-appliance-kvm openSUSE-release-appliance- openstack openSUSE-release-appliance-vagrant openSUSE-release-appliance-vmware openSUSE-release-appliance-wsl openSUSE-release-ftp ``` If I set `Prefer: openSUSE-release-appliance-docker` in the project config I get ``` error running container: error creating container for [/bin/sh -c obs-docker- support --install]: time="2019-10-27T15:23:32Z" level=error msg="systemd cgroup flag passed, but systemd support for managing cgroups is not available ``` e.g. in https://build.opensuse.org/package/live_build_log/ home:okurz:container/yamllint/containers/x86_64 This is reproducible also when creating a new project based on the wizard following https://build.opensuse.org/image_templates selecting "Templates using openSUSE Tumbleweed", "Container built using docker tool". By comparison, a container built based on Leap 15.1 seems fine: https:// build.opensuse.org/package/show/home:okurz:branches:openSUSE:Templates:Imag…: 15.1/container_test Any ideas how to fix the container build using Dockerfile? Have fun, Oliver -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] OBS 2.10 not publishing, modifyrepo failed: 256
by Stefan Seyfried 29 Oct '19

29 Oct '19

I'm getting this in publisher.log: 2019-10-29 10:47:25: [19794] publishing GMPMS:CIS/SLES12-SP4 fetched 0 patterns running createrepo creating appdata files adding appdata.xml to repodata adding app-icons.tar to repodata Cannot open /srv/obs/repos/GMPMS:/CIS/SLES12-SP4/repodata/app-icons.tar: Cannot detect compression type publish failed for GMPMS:CIS/SLES12-SP4 : modifyrepo failed: 256 syncing database (6 ops) I'm using modifyrepo_c I don't care the least for appstream stuff anyway, so this fixes it: obs:/usr/lib/obs/server # diff bs_publish~ bs_publish -u --- bs_publish~ 2019-09-20 12:32:53.000000000 +0000 +++ bs_publish 2019-08-27 08:45:47.394200100 +0000 @@ -645,7 +645,7 @@ } if (-e "$extrep/repodata/app-icons.tar") { print " adding app-icons.tar to repodata\n"; - qsystem($modifyrepo_bin, "$extrep/repodata/app-icons.tar", "$extrep/repodata", @legacyargs) && die(" modifyrepo failed: $?\n"); + qsystem($modifyrepo_bin, "$extrep/repodata/app-icons.tar", "$extrep/repodata", @legacyargs) && warn(" modifyrepo failed: $?\n"); unlink("$extrep/repodata/app-icons.tar"); } } -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0