openSUSE Build Service September 2019

buildservice@lists.opensuse.org

37 participants
34 discussions

by Stephan Duehr

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

2 years, 5 months

[opensuse-buildservice] Public Key not available SLE_12_SP3 s390x

by Usman Haider

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

2 years, 5 months

[opensuse-buildservice] Need help with signing error in priv obs installation

by Stefan Botter

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

2 years, 6 months

[opensuse-buildservice] KVM worker setup

by Morschhäuser, Mark

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

2 years, 6 months

[opensuse-buildservice] A new user interface for you!

by Henne Vogelsang

Friends, the OBS team, together with many of you, has developed and beta-tested a new, more modern, user interface for the last couple of months. And today we are beginning to roll it out for everybody! Expect the OBS web user interface to change for you in the coming days, if it has not already. As always, please keep in touch and give us your feedback over IRC, this list or in case of problems, via github issues. https://openbuildservice.org/support/ Henne -- Henne Vogelsang http://www.opensuse.org Everybody has a plan, until they get hit. - Mike Tyson -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 years, 7 months

[opensuse-buildservice] service error: DEBUG:root:Cleaning: /var/cache/obs/trDXZ8kSZ2as/out/tmp_kh0857x

by Andreas Schwab

What does that mean when an obs_scm service fails with this error? Andreas. -- Andreas Schwab, SUSE Labs, schwab(a)suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 years, 7 months

[opensuse-buildservice] New deliverable is out!

by Victor Pereira

Hello everyone! The OBS Team delivered one more time. This time however, it was a real special milestone for us. You can learn more about it on https://openbuildservice.org/2019/09/25/bye-bye-bento/ On behalf of the OBS Team, Victor Pereira -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 years, 7 months

[opensuse-buildservice] error during repo signing?

by Morschhäuser, Mark

Hi, I currently use a Leap 15.1 system where I added a repo from my OBS instance and if I want to update the system with zypper everything works fine - but sometimes the following issue occurs: ======================== ~ # LC_ALL=C zypper se mypackage Retrieving repository 'myrepo' metadata ----------------------[\] Signature verification failed for file 'repomd.xml' from repository 'myrepo'. Note: Signing data enables the recipient to verify that no modifications occurred after the data were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system and in extreme cases even to a system compromise. Note: File 'repomd.xml' is the repositories master index file. It ensures the integrity of the whole repo. Warning: This file was modified after it has been signed. This may have been a malicious change, so it might not be trustworthy anymore! You should not continue unless you know it's safe. Signature verification failed for file 'repomd.xml' from repository 'myrepo'. Continue? [yes/no] (no): ======================== And basically there is nothing I can do against it. I tried to force the refresh, reset snapshots and try again... but this does not help. The repomd.xml exists and contains my file, the signed file has the same timestamp, triggering a rebuild does not help... I had this once and if I came back to work next day it magically worked (until I rebuilt the package, then I had the same issue again). I was able to work 2-3 weeks now without this issue but it occurred again. So it seems there is a bug in the sign or deployment process somewhere. Is this known? The signer.log contains the signing messages and the waiting for event messages. No errors here. What can I do? 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

2 years, 7 months

[opensuse-buildservice] Questions on automating

by Timothy O'Barr

I've got a few questions when it comes to automating the build process with OBS. I'm trying to make a bash script that'll saasuto clone from a source and run osc. One thing that's getting in the way is when I run osc commit to upload the new files to the obs repo it automatically opens the changes file in an editor like VI thus breaking the automation. is there a way to skip that? Or is there a better way to make OBS automatically compile the next version of a program? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 years, 7 months

[opensuse-buildservice] Thoughts on deploy Open Build Service in kubernetes cluster

by TommyLike Hu

Hey guys, Recently, we start to evaluate Open Build Service for our package build and publish system, considering the portability, scalability and ecosystem, our most of other services are deployed on kubernetes cluster, therefore, we are just wondering whether it's a possible or a good choice to deploy OBS in kubernetes. We would like start this thread for the purpose of discussion on these below: 1. Does there anyone have tried to deploy OBS in k8s cluster, Is there any suggestion/warning on that direction? 2. If possible, what's the best practice on how to deploying OBS, and what's the scale we can get? 3. If not, what's the disadvantages or issues we would have within that deployment? Thanks for your sharing! TommyLike -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 years, 7 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service September 2019