September 2019 - openSUSE Build Service

[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] 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] 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] A new user interface for you!
by Henne Vogelsang 15 Oct '19

15 Oct '19

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

6 15

[opensuse-buildservice] service error: DEBUG:root:Cleaning: /var/cache/obs/trDXZ8kSZ2as/out/tmp_kh0857x
by Andreas Schwab 01 Oct '19

01 Oct '19

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 1

[opensuse-buildservice] New deliverable is out!
by Victor Pereira 27 Sep '19

27 Sep '19

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

3 3

[opensuse-buildservice] error during repo signing?
by Morschhäuser, Mark 27 Sep '19

27 Sep '19

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

1 1

[opensuse-buildservice] Questions on automating
by Timothy O'Barr 27 Sep '19

27 Sep '19

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

5 4

[opensuse-buildservice] Thoughts on deploy Open Build Service in kubernetes cluster
by TommyLike Hu 27 Sep '19

27 Sep '19

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

4 8

[opensuse-buildservice] SLE sources do not appear to generate events on message bus
by James Berry 26 Sep '19

26 Sep '19

No opensuse.obs.package.update messages appear for updates to SUSE:SLE-15- SP2:GA. Presumably this is not so much an OBS issue as much as the way the sync is going outside the normal usage bounds, hence the email instead of issue. Improving the syncing mechanism to generate events would be much appreciated. Tracking issue from our end: https://github.com/openSUSE/openSUSE-release-tools/issues/2239 -- Jimmy -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

[opensuse-buildservice] Cannot build RHEL packages anymore (package "epel-rpm-macros" suddenly not resolvable)...
by Olsson, Dennis 26 Sep '19

26 Sep '19

Hi There, I have been working on a package for RHEL 7 the last couple of days without any issues. My last successful build was on 24-Sep-2019 18:56. Yesterday, I made some reorganization of my local file system, which meant I had to recheck out my project as well as the package, I was working on, from OBS (using "osc checkout"). Having done that, I was able to make a few local builds without any issues, but when I wanted to make my final build of my package, I suddenly received this error message: $ osc build --local-package Building xscreensaver.spec for Fedora_EPEL_7_RHEL/x86_64 Getting buildinfo from server and store to /data/home/olsde000/devel/ATS/lp3/misc/sources/home:DOlsson/xscreensaver/.osc/_buildinfo-Fedora_EPEL_7_RHEL-x86_64.xml Getting buildconfig from server and store to /data/home/olsde000/devel/ATS/lp3/misc/sources/home:DOlsson/xscreensaver/.osc/_buildconfig-Fedora_EPEL_7_RHEL-x86_64 buildinfo is broken... it says: unresolvable: nothing provides epel-rpm-macros $ I simply do not understand, why I am getting this. When following the repository chain in OBS, I end up with Fedora:EPEL:7/RHEL x86_64 => Fedora:EPEL:7/standard x86_64 => x86_64 https://download.fedoraproject.org/pub/epel/7/x86_64 (rpmmd) where the package "epel-rpm-macros" definitively can be found: https://download.fedoraproject.org/pub/epel/7/x86_64/Packages/e/epel-rpm-ma… So why, all of a sudden, is not OBS capable of resolving this package. As written above, everything had working very nicely up till around 16:00 - 18:00 yesterday 25-Sep-2019, where this error message out of no where turned up. And, no, it does help to try to build the package on OBS either, the same error turns up here. Has any one gotten an idea as to what is going on here and how to solve this problem? Best regards & thanks for your help, Dennis Olsson-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

[opensuse-buildservice] Issue with revision in git services
by Dominig ar Foll (Intel Open Source) 25 Sep '19

25 Sep '19

Hello, I try to extract a given review from gerrit with a service file and I get an error that I do not understand My _service points to a pending review. - If I run the service locally with "osc service localrun" it works. - if I run "git clone https://review.opendev.org/starlingx/fault refs/changes/95/684395/5" I get the code * if I run "osc service rr" I get an error "No such revision" Could some one explains me what is wrong ? My test project is at https://build.opensuse.org/package/show/home:dominig:starlingx-sandbox/fm-c… ------------------- _service ------------------------------ <services> <service name="obs_scm"> <param name="scm">git</param> <param name="url">https://review.opendev.org/starlingx/fault</param> <param name="revision">refs/changes/95/684395/5</param> <param name="version">1.0</param> <param name="subdir">fm-common</param> <param name="filename">fm-common</param> <param name="changesgenerate">disable</param> <param name="extract">opensuse/fm-common.spec</param> <param name="extract">opensuse/fm-common.changes</param> </service> <service mode="buildtime" name="tar" /> <service mode="buildtime" name="recompress"> <param name="compression">gz</param> <param name="file">*.tar</param> </service> <service name="set_version" mode="disabled"/> </services> ------------ OBS log --------------- service obs_scm failed: /srv/obs/service/12167 /srv/obs/service/12167/src /srv/obs/service/12167/src/_service /srv/obs/service/12167/src/.old /srv/obs/service/12167/out /srv/obs/service/12167/var /srv/obs/service/12167/var/cache /srv/obs/service/12167/var/cache/obs /srv/obs/service/12167/var/cache/obs/h9UaxI3JJ6e1 /srv/obs/service/12167/var/cache/obs/h9UaxI3JJ6e1/scripts /srv/obs/service/12167/var/cache/obs/h9UaxI3JJ6e1/scripts/inner.sh /srv/obs/service/12167/var/cache/obs/h9UaxI3JJ6e1/scripts/inner.sh.command /srv/obs/service/12167/home + echo Running /usr/lib/obs/service//obs_scm --scm git --url https://review.opendev.org/starlingx/fault --revision refs/changes/95/684395/5 --version 1.0 --subdir fm-common --filename fm-common --changesgenerate disable --extract opensuse/fm-common.spec --extract opensuse/fm-common.changes --outdir /var/cache/obs/h9UaxI3JJ6e1/out + export CACHEDIRECTORY=/var/cache/obs/h9UaxI3JJ6e1/scm-cache + CACHEDIRECTORY=/var/cache/obs/h9UaxI3JJ6e1/scm-cache + export HOME=/var/cache/obs/h9UaxI3JJ6e1/home + HOME=/var/cache/obs/h9UaxI3JJ6e1/home + /usr/lib/obs/service//obs_scm --scm git --url https://review.opendev.org/starlingx/fault --revision refs/changes/95/684395/5 --version 1.0 --subdir fm-common --filename fm-common --changesgenerate disable --extract opensuse/fm-common.spec --extract opensuse/fm-common.changes --outdir /var/cache/obs/h9UaxI3JJ6e1/out Running /usr/lib/obs/service//obs_scm --scm git --url https://review.opendev.org/starlingx/fault --revision refs/changes/95/684395/5 --version 1.0 --subdir fm-common --filename fm-common --changesgenerate disable --extract opensuse/fm-common.spec --extract opensuse/fm-common.changes --outdir /var/cache/obs/h9UaxI3JJ6e1/out refs/changes/95/684395/5: No such revision -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 6

[opensuse-buildservice] Repositories returning 403 - Access Forbidden
by Frederik Carlier 25 Sep '19

25 Sep '19

Hello, In the last hour or so, my home project (at https://download.opensuse.org/repositories/home:/qmfrederik/CentOS_7) started returning 403 - Access Forbidden. I've noticed there was some maintenance on OBS. Are there any steps I need to take to re-enable or refresh my repository, or is this a transient problem? Thanks! Frederik. -- 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] product creation
by Morschhäuser, Mark 25 Sep '19

25 Sep '19

Hi, which way (tool, workflow) is currently recommended to create a product in OBS? The webinterface does not have the editor anymore (which was barely functional anyways), SuSE Studio does not exist anymore, the yast module does not exist anymore, ... and I think it is quite impossible to create something like this https://build.opensuse.org/package/show/openSUSE:Leap:15.1/000product manually... 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 1

[opensuse-buildservice] Publisher not publishing to stageserver on private instance 2.10
by Stefan Botter 20 Sep '19

20 Sep '19

Hi all, I have trouble with my private OBS instance: I have configured a stageserver in BSConfig.pm, as ==== our $stageserver = 'rsync://192.168.22.23/repos'; ==== The target is available and running, but the publisher fails to send the data there. In /srv/obs/log/publisher.log the following error messages are logged: ==== 2019-09-18 15:07:17: [14920] publishing userweb/openSUSE_Leap_15.1 fetched 0 patterns running createrepo running rsync to rsync://192.168.22.23/repos at Wed Sep 18 15:07:18 2019 Use of uninitialized value $args[2] in exec at /usr/lib/obs/server/ bs_publish line 134. rsync version 3.1.3 protocol version 31 Copyright (C) 1996-2018 by Andrew Tridgell, Wayne Davison, and others. [... all the rest of a plain call of "rsync" ...] See http://rsync.samba.org/ for updates, bug reports, and answers rsync error: syntax or usage error (code 1) at options.c(2356) [client=3.1.3] publish failed for userweb/openSUSE_Leap_15.1 : rsync failed at Wed Sep 18 15:09:58 2019: 256 syncing database (6 ops) ==== I am pretty sure, that I did not change the setting for the stageserver in BSConfig.pm for several years now, and, according to logs, it worked until mid-July, when I updated the machine to OBS 2.10. Here my question for help: Did something change in the way staging is configured, and I missed a required configuration change, or is this a bug in the publisher of 2.10? Thank you for your help, Stefan PS: Even scarier question: Am I the only user using a stageserver? -- Stefan Botter zu Hause Bremen

2 2

[opensuse-buildservice] _service <revision> position important ?
by Dominig ar Foll (Intel Open Source) 17 Sep '19

17 Sep '19

Hello, I have lost a bit of time puzzled by my _service refusing to download a given git revision. I finally discover that if the revision if before the version, it does not work but when position after it does. Look like back magic to me. Any explanation of that strange behaviour ? Regards -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre -- 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] Best option to integrate StartlingX CI with OBS
by Dominig ar Foll (Intel Open Source) 16 Sep '19

16 Sep '19

Hello, I have spent a few hours at looking at various options on how best integrate StartlingX CI with OBS for our multiOS subproject. For info, StarlingX is a pilot project of OpenStack. https://www.starlingx.io/ I notice when looking at information on OBS and CI integration published by projects like OpenStack or obs-server that that prefer process seems to be, first build in a branch, followed by a second build in staging. It leads me to a few questions: 1) Why 2 builds ------------------------ What s the value of building of a package in Staging if that was already validated in a Branch ? Is there something that I missed that is possible in Staging but not in a branch ? 2) Managing builds ------------------------------ I do not have the knowledge of a build ID concept on OBS and that make a few things more difficult. I would be interested to understand the best way to work around. After creating my branch and changing the required files, my build can be tracked by osc. osc results -w --xml home:dominig:branches:....... The -w option might not be a good idea as I can see that SSL Error: (104, 'Connection reset by peer') are quite frequent. Is there a better asynchronous way to track the package build success/failure? If multiple changes are triggered in parallel on the same package, I would have a mess with my branches (naming conflict). What would be the best method to avoid serialisation on the test builds in that case ? 3) Cancelling build ------------------------------ It is not uncommon in a CI, that a new patch set is added before that the build result is known. What would be the best way to manage such situation ? Would an "osc restartbuild" on the same branch after source update the right solution ? Any other hints for CI integration would be welcome. -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 6

[opensuse-buildservice] Errors were encountered while processing: raspbian-archive-keyring
by Mark Grant 16 Sep '19

16 Sep '19

I have a simple project which wraps a few apt commands. On my development machine a single set of files; control, rules, dsc, orig and source tar are used to build packages for Debian 9 and 10 and Raspbian 9 and 10 using pbuilder. All packages build successfully. Launchpad also builds from source using the same control and rules files and successfully creates packages. I transfer these file to OBS and packages for Debian and Ubuntu build succesfully, Raspbian 9 and 10 both fail with the same error. The key lines in the OBS build log are:- [ 187s] [201/204] installing raspbian-archive-keyring-20120528.2 [ 187s] /var/lib/dpkg/info/raspbian-archive-keyring.postinst: 8: /var/lib/dpkg/info/raspbian-archive-keyring.postinst: apt-key: not found [ 187s] dpkg: error processing package raspbian-archive-keyring (--install): [ 187s] installed raspbian-archive-keyring package post-installation script subprocess returned error exit status 127 [ 187s] Errors were encountered while processing: [ 187s] raspbian-archive-keyring [ 187s] exit ... Could there be a problem with the raspbian-archive-keyring package at OBS? 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

2 2

[opensuse-buildservice] Workflow for tuning release field using "obs_admin --set-relsync"
by Srinidhi B 16 Sep '19

16 Sep '19

Hello Everyone, Could someone please explain the exact workflow on how to tune the version-release field of a package using obs_admin --set-relsync? When I change the version-release value for a package in the :relsync file and rebuild the package, my changes are ignored. I know that I can modify build/$prpa/$packid/history and projects/$projid.pkg/$packid.rev file to get the desired affect, but I feel --set-relsync is much easier and script-able way. What do I need to do after running "obs-admin --set-relsync /bs/$prpa/:relsync $packid 'vers-rel'" for the next rebuild of the package to pick up the new 'ver-rel' values? Regards, Srinidhi. -- 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 ignoring %define _lto_cflags %{nil} in spec file
by Rosanne DiMesio 14 Sep '19

14 Sep '19

Wine does not build with LTO enabled. I have %define _lto_cflags %{nil} in my spec file, and this has worked in the past to disable it, but my Tumbleweed builds are suddenly failing with lto errors: wine-devel.x86_64: E: lto-no-text-in-archive (Badness: 10000) /usr/lib64/wine/libadsiid.a [ 993s] wine-devel.x86_64: E: lto-no-text-in-archive (Badness: 10000) /usr/lib64/wine/libdmoguids.a [ 993s] wine-devel.x86_64: E: lto-no-text-in-archive (Badness: 10000) /usr/lib64/wine/libdxguid.a [ 993s] wine-devel.x86_64: E: lto-no-text-in-archive (Badness: 10000) /usr/lib64/wine/libmfuuid.a [ 993s] wine-devel.x86_64: E: lto-no-text-in-archive (Badness: 10000) /usr/lib64/wine/libstrmiids.a [ 993s] wine-devel.x86_64: E: lto-no-text-in-archive (Badness: 10000) /usr/lib64/wine/libuuid.a [ 993s] wine-devel.x86_64: E: lto-no-text-in-archive (Badness: 10000) /usr/lib64/wine/libwmcodecdspuuid.a [ 993s] This archive does not contain a non-empty .text section. The archive was not [ 993s] created with -ffat-lto-objects option. My project is https://build.opensuse.org/package/show/home:dimesio/wine. -- 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 4

[opensuse-buildservice] Why does OBS think some packages are "unresolvable" while they are not?
by Manfred Hollstein 13 Sep '19

13 Sep '19

Hi there, I've given up (I think) trying to understand why OBS sometimes behaves different than what I'd expect. Here is my (current) challenge: I'm trying to build firefox69 in my own project in home:manfred-h:mozilla. The repository metadata is set up as follows: $ osc meta prj home:manfred-h:mozilla <project name="home:manfred-h:mozilla"> <title>mozilla</title> <description> Mozilla based projects and support packages. </description> <person userid="manfred-h" role="maintainer"/> <build> <disable/> </build> <repository name="openSUSE_Leap_42.3"> <path project="home:manfred-h:devel:languages:rust" repository="openSUSE_Leap_42.3"/> <path project="mozilla" repository="openSUSE_Leap_42.3"/> <path project="openSUSE:Leap:42.3:Update" repository="standard"/> <path project="openSUSE:Leap:42.3" repository="standard"/> <arch>x86_64</arch> </repository> <repository name="openSUSE_Leap_15.1"> <path project="devel:languages:rust" repository="openSUSE_Leap_15.1"/> <path project="mozilla" repository="openSUSE_Leap_15.1"/> <path project="openSUSE:Leap:15.1:Update" repository="standard"/> <path project="openSUSE:Leap:15.1" repository="standard"/> <arch>x86_64</arch> </repository> <repository name="openSUSE_Leap_15.0"> <path project="home:manfred-h:devel:languages:rust" repository="openSUSE_Leap_15.0"/> <path project="mozilla" repository="openSUSE_Leap_15.0"/> <path project="openSUSE:Leap:15.0:Update" repository="standard"/> <path project="openSUSE:Leap:15.0" repository="standard"/> <arch>x86_64</arch> </repository> </project> As you can see, nothing should get build by default (this is enabled purely on a package by package case) and repositories are setup so that "rust" and related packages should be taken from - devel:languages:rust for openSUSE_Leap_15.1 - home:manfred-h:devel:languages:rust for 42.3 and 15.0 firefox69 now needs rust-cbindgen >= 0.9.0, so I copied that package to my home:manfred-h:devel:languages:rust as rust-cbindgen-0.9.0 and built it there successfully for openSUSE_Leap_42.3 and openSUSE_Leap_15.0 Still OBS thinks "nothing provides rust-cbindgen >= 0.9.0" for 15.0 and 42.3, but the packages are there: <https://build.opensuse.org/package/binary/home:manfred-h:devel:languages:ru…> <https://build.opensuse.org/package/binary/home:manfred-h:devel:languages:ru…> both providing: rust-cbindgen = 0.9.0-1.1 rust-cbindgen(x86-64) = 0.9.0-1.1 FWIW, as a last resort, I linked my rust-cbindgen-0.9.0 package to rust-cbindgen in the home:manfred-h:devel:languages:rust project, but this did not change anything unfortunately. Can anybody tell me what I'm doing wrong here? Or is this a bug in the OBS resolver? TIA, cheers. l8er manfred PS: No complaints wrt/ 42.3, I'm not yet done with migrating all systems I maintain to 15.1 yet! Therefore I'm trying to keep those packages still building which are not services but still as close to the Internet as possible, i.e. the _bad world_ ;)

7 32

[opensuse-buildservice] Error "Version is invalid" for JeOS 15 and 15SP1
by Vincent Moutoussamy 11 Sep '19

11 Sep '19

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

3 3

[opensuse-buildservice] Enhancement ideas for https://build.opensuse.org/image_templates
by Vincent Moutoussamy 11 Sep '19

11 Sep '19

Hi, I think the former SUSE Studio UI* was a bit better than what we have on https://build.opensuse.org/image_templates. So here are some of my idea to improve the existing page: 1) Having “Template for”/“Templates using" in the name of each projects might be too much? In that regard I could rename “SLE 15 Code Line” by just “SUSE Linux Enterprise 15” and you could rename "Templates using openSUSE Leap 15.1” by just “openSUSE Leap 15.1”. 2) Emphasis on openSUSE and SLE latest version - By having a “UI frame” called "openSUSE and SLE latest versions” containing Leap 15.1, Tumbleweed and SLE 15.1. - Then a frame called “others” containing everything else but with Leap 15.0 and SLE 15.1 at the top, then the rest So do you like my ideas? I’m wondering if I could contribute/do this on my own and how? Thanks and have a nice day, Regards, * for reference https://nocnypingwin.pl/wp-content/uploads/2014/02/zrzutekranu23.png -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager

3 4

[opensuse-buildservice] Removing old template from Studio Express
by Vincent Moutoussamy 11 Sep '19

11 Sep '19

Hi there, Would it be possible to remove all the following unsupported openSUSE/SLE versions from https://build.opensuse.org/image_templates? Unsupported versions: - SLE: 12SP2, 12SP3, 11SP4, - Leap: 42.3 Thanks, Regards, -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] missing _rpmmacrodir for SLE 12 / Leap 42 in devel:languages:ruby PRJ
by Christian 10 Sep '19

10 Sep '19

Hi, may we have the following added to projconf of devel:languages:ruby please ? ### seems that _rpmmacrodir is not known on SLE 12 / Leap 42 %if %{suse_version} == 1315 Macros: %_rpmmacrodir /etc/rpm :Macros %endif This will fix some of the existing build errors in devel:languages:ruby Thank you :-) -- Christian ------------------------------------------------------------ https://join.worldcommunitygrid.org?recruiterId=177038 ------------------------------------------------------------ http://www.sc24.de - Sportbekleidung ------------------------------------------------------------

2 2

[opensuse-buildservice] Mirroring an Open Build Service repository
by Linux Kamarada 09 Sep '19

09 Sep '19

Hi, everyone! Is it possible to mirror an Open Build Service repository? I tried some commands such as: # rsync -avz --delete rsync://download.opensuse.org/repositories/home:/kamarada:/15.1/ /srv/www/htdocs/kamarada-repo/15.1/ or # lftp -c mirror https://ftp.opensuse.org/pub/opensuse/repositories/home:/kamarada:/15.1/ /srv/www/htdocs/kamarada-repo/15.1/ But they didn't work. Thanks! Antonio The Linux Kamarada Project http://kamarada.github.io/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] python3.4-venv and python3-wheel missing from Ubuntu 14.04 standard
by Neal Gompa 06 Sep '19

06 Sep '19

Hey, I'm trying to build packages with python3.4-venv and python3-wheel as build dependencies on Ubuntu 14.04, but they appear to be missing. These packages are included in the Ubuntu main repo, so I would have expected them to exist in the Ubuntu 14.04 standard target... Can someone please fix this? Thanks in advance, Neal -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 7

[opensuse-buildservice] repodata not matching sha256 for a package
by Julio Gonzalez 06 Sep '19

06 Sep '19

I have this strange issue: https://github.com/uyuni-project/uyuni/issues/1261#issuecomment-528854701 The repodata XML [1] says that the package zypp-plugin-python-0.6.2- lp150.2.1.noarch.rpm has the following sha56sum: e713e07a5d980f49da0224348e9d5c65414feb3d8257eb7f8e43e32493081f68 While downloading the package from the repository [2] and running sha25tsum returns: ec3b1d39297966d6e972b449f02a161ebc1b93f794e3bfde16d53cb63e9ea234 In case it's relevant, the source package: https://build.opensuse.org/package/ show/systemsmanagement:Uyuni:Stable:openSUSE_Leap_15-Uyuni-Client-Tools/zypp- plugin Was "promoted" using "osc release" (as you can see at the package history). Other packages seem to be fine. So the thing is: is there any way of republishing the repodata without rebuilding any package? Why did this happen? Did we do anything wrong? Best regards. [1] https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/ Stable:/openSUSE_Leap_15-Uyuni-Client-Tools/openSUSE_Leap_15.0/repodata/ fda1b74b6cc4109175630e001eaea9f02f9c3f0a684763ba47920303dd0918ed- primary.xml.gz [2] https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/ Stable:/openSUSE_Leap_15-Uyuni-Client-Tools/openSUSE_Leap_15.0/noarch/zypp- plugin-python-0.6.2-lp150.2.1.noarch.rpm -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

[opensuse-buildservice] Extracting spec file from a git repo on OBS
by Dominig ar Foll (Intel Open Source) 04 Sep '19

04 Sep '19

Hello, I would like to maintain my spec file in git repo like I do for the rest of the code with "obs_scm" in "_service". It would allow to enforce the same change control process on spec files than on the rest of the code. I know that Tizen in it's time, had done a hack on their own OBS, but I wonder if the same facility would be now available on the public OpenSUSE OBS. A pointer to a solution would be very appreciated. Regards -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 6

[opensuse-buildservice] HowTo of AppImage repo facility in OBS
by Dominig ar Foll (Intel Open Source) 04 Sep '19

04 Sep '19

Hello, I see that OBS now offers an AppImage repo option for any project. When I activate the Option, on one of my working project which provides many working packages, OBS informs me that the building of my packages for AppImage are deactivated. I guess that it's due to a missing file or option somewhere. But what ? Is it possible to simply build an AppImage by adding the repo to a project ? What else I need to add to my project to publish an AppImage as well as my traditional packages ? https://build.opensuse.org/project/show/home:dominig:opencpn-sandbox My objective would be to package my full project (I have a meta package that loads all the sub packages) as a single AppImage. Any help would be appreciated. -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] leap 15.0 builder problem?
by Peter Czanik 03 Sep '19

03 Sep '19

Hi, While trying to upgrade syslog-ng in Base:system I ran into a strange problem. Builds for openSUSE Leap 15.0 x86_64 fails, but with an error message, which does not seem to be related to syslog-ng.spec: [ 9s] booting kvm... [ 9s] ### VM INTERACTION START ### [ 9s] /usr/bin/qemu-kvm -nodefaults -no-reboot -nographic -vga none -cpu host -object rng-random,filename=/dev/random,id=rng0 -device virtio-rng-pci,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=ext3 rootflags=data=writeback,nobarrier,commit=150,noatime ext4.allow_unsupported=1 kpti=off pti=off spectre_v2=off panic=1 quiet no-kvmclock elevator=noop nmi_watchdog=0 rw rd.driver.pre=binfmt_misc console=ttyS0 init=/.build/build -m 8192 -drive file=/var/cache/obs/worker/root_1/root,format=raw,if=none,id=disk,cache=unsafe -device virtio-blk-pci,drive=disk,serial=0 -drive file=/var/cache/obs/worker/root_1/swap,format=raw,if=none,id=swap,cache=unsafe -device virtio-blk-pci,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 8 [ 10s] c[?7l[2J[0mSeaBIOS (version rel-1.12.0-0-ga698c89-rebuilt.opensuse.org) [ 13s] Booting from ROM..c[?7l[2J[ 2.518420] dracut-pre-udev[231]: modprobe: FATAL: Module kqemu not found in directory /lib/modules/4.12.14-lp150.11-default [ 13s] [ 2.635247] dracut-pre-udev[231]: modprobe: FATAL: Module ext2 not found in directory /lib/modules/4.12.14-lp150.11-default [ 13s] [ 2.667787] dracut-pre-udev[231]: modprobe: FATAL: Module ext3 not found in directory /lib/modules/4.12.14-lp150.11-default [ 14s] [ 3.712514] dracut-pre-udev[231]: modprobe: FATAL: Module ibmvscsi not found in directory /lib/modules/4.12.14-lp150.11-default [ 14s] [ 3.773479] dracut-pre-udev[231]: modprobe: FATAL: Module ibmveth not found in directory /lib/modules/4.12.14-lp150.11-default [ 16s] /bin/bash: error while loading shared libraries: libreadline.so.8: cannot open shared object file: No such file or directory [ 16s] [ 5.267243] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 [ 16s] [ 5.267243] [ 16s] [ 5.268429] CPU: 0 PID: 1 Comm: build Not tainted 4.12.14-lp150.11-default #1 openSUSE Leap 15.0 (unreleased) [ 16s] [ 5.268429] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.0-0-ga698c89-rebuilt.opensuse.org 04/01/2014 [ 16s] [ 5.268429] Call Trace: [ 16s] [ 5.268429] dump_stack+0x5c/0x82 [ 16s] [ 5.268429] panic+0xd5/0x230 [ 16s] [ 5.268429] do_exit+0xb2e/0xb30 [ 16s] [ 5.268429] ? __schedule+0x247/0x870 [ 16s] [ 5.268429] do_group_exit+0x3a/0xa0 [ 16s] [ 5.268429] SyS_exit_group+0x10/0x10 [ 16s] [ 5.268429] do_syscall_64+0x7b/0x140 [ 16s] [ 5.268429] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 16s] [ 5.268429] RIP: 0033:0x7f6164b6e288 [ 16s] [ 5.268429] RSP: 002b:00007ffc94f644c8 EFLAGS: 00000202 ORIG_RAX: 00000000000000e7 [ 16s] [ 5.302348] RAX: ffffffffffffffda RBX: 00007ffc94f64920 RCX: 00007f6164b6e288 [ 16s] [ 5.302348] RDX: 000000000000007f RSI: 000000000000003c RDI: 000000000000007f [ 16s] [ 5.302348] RBP: 0000000000000000 R08: 00000000000000e7 R09: ffffffffffffffff [ 16s] [ 5.325271] R10: 0000000000000000 R11: 0000000000000202 R12: 00007ffc94f64940 [ 16s] [ 5.325271] R13: 00007f6164b74c28 R14: 0000000000000002 R15: 00007f6164b729fc [ 16s] [ 5.325271] Kernel Offset: disabled [ 16s] [ 5.325271] Rebooting in 1 seconds.. [ 17s] ### VM INTERACTION END ### [ 17s] No buildstatus set, either the base system is broken (kernel/initrd/udev/glibc/bash/perl) [ 17s] or the build host has a kernel or hardware problem... For complete logs check: https://build.opensuse.org/package/live_build_log/home:czanik:branches:Base… Bye, CzP -- 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] wipebinaries doesn't work as expected
by Hans-Peter Jansen 03 Sep '19

03 Sep '19

Hi, I've build a package, that needs to link with problematic libs, therefor I've added these dependencies with publishing disabled. For some reason, they were published anyway, so I used my usual procedure: osc wipebinaries --all prj pkg disable publishing for pkg with web ui Expected result: pkg gets rebuilt, but not published. Achieved result: pkg gets rebuilt, but binaries are not wiped. IOW, they're still published. Next, I've tried to disable build for the whole project, and wiped everything: osc wipebinaries --all prj Now, *all* binaries vanished, but those, that I want to get rid of *remained*! Next, I've tried all the other options as well: osc wipebinaries --build-disabled home:frispete:Tumbleweed osc wipebinaries --build-failed home:frispete:Tumbleweed osc wipebinaries --unresolvable home:frispete:Tumbleweed osc wipebinaries --broken home:frispete:Tumbleweed osc wipebinaries --all home:frispete:Tumbleweed but, after waiting for the project to be published, those packages still exist: https://download.opensuse.org/repositories/home:/frispete:/Tumbleweed/ openSUSE_Tumbleweed/x86_64/ Any idea, how I can get rid of these remaining packages? Call the Air Forces? Thanks in advance. Cheers, Pete System: Tumbleweed 20190829, osc 0.165.4 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] pre_checkin.sh and obs_scm git service
by Hans-Peter Jansen 03 Sep '19

03 Sep '19

[next try here, since this request seems to be misplaced in -packaging] Hi, if I understand the pre_checkin.sh concept correctly (docs are quite sparse to put it friendly: https://en.opensuse.org/ openSUSE:Build_Service_Concept_PreCheckinFeatures) pre_checkin.sh is executed on check in time, but I'm looking for a similar mechanism, that is executed after git checkout and before build on the server (pre_build.sh?) Background: in order to produce a reproducible build, sometimes, we need to generate the necessary information from running a script out of the git tree. Example: https://build.opensuse.org/package/show/home:frispete:Tumbleweed/HandBrake While at it, with obs_scm in default mode and changesgenerate option enabled, changelog handling is suboptimal as well. It would be cool to have changespersistent option, that would copy the _service:obs_scm:HandBrake.changes to the HandBrake.changes, as this process would do in disabled mode. Of course, this changespersistent option could be dealed with in a pre_build.sh as well... Thanks, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 5