December 2018 - openSUSE Build Service

[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] OBS Appliance - Unable to Update
by Khalil Graves 15 Apr '19

15 Apr '19

I am running OBS Appliance 2.8.2 on VMware ESX. When the appliance boots I get an error "Failed to start LSB: Finds the storage device to be used for OBS server and/or worker." I have included a dump of systemctl status obsstoagesetup.service below. I Just want to confirm if this is normal or should be addressed. I also attempted and update of a clone of my appliance via zypper but 2 GB root drive is not sufficient for upgrades. Update begins but end with "Error Code: Write Error". I checked root drive and it was up to 100% utilization from 93% prior to update. I decided to install latest version of OBS appliance over existing install. New appliance adopts my old setting but now I am getting and error on boot "Failed to start LSB: open build service source service server." In addition I am unable to build rpms in this current state. Not sure what to do next to get the cloned appliance to build a package. SYSTEMCTL status obsstoragesetup.service obsstoragesetup.service - LSB: Finds the storage device to be used for OBS server and/or worker Loaded: loaded (/etc/init.d/obsstoragesetup; bad; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2018-03-06 18:44:59 UTC; 16min ago Docs: man:systemd-sysv-generator(8) Process: 1365 ExecStart=/etc/init.d/obsstoragesetup start (code=exited, status=1/FAILURE) Mar 06 18:44:59 linux obsstoragesetup[1365]: OBS_SERVER_SIZE=38912 Mar 06 18:44:59 linux obsstoragesetup[1365]: TOTAL_SWAP_SIZE=1024 Mar 06 18:44:59 linux obsstoragesetup[1365]: FINAL_VG_SIZE = 12284 - 38912 - 25600 - 1024 Mar 06 18:44:59 linux obsstoragesetup[1365]: FINAL_VG_SIZE=-53252 Mar 06 18:44:59 linux obsstoragesetup[1365]: OBS_WORKER_ROOT_SIZE=-26626 Mar 06 18:44:59 linux obsstoragesetup[1365]: MIN_WORKER_ROOT_SIZE=4096 Mar 06 18:44:59 linux systemd[1]: obsstoragesetup.service: Control process exited, code=exited status=1 Mar 06 18:44:59 linux systemd[1]: Failed to start LSB: Finds the storage device to be used for OBS server and/or worker. Mar 06 18:44:59 linux systemd[1]: obsstoragesetup.service: Unit entered failed state. Mar 06 18:44:59 linux systemd[1]: obsstoragesetup.service: Failed with result 'exit-code'. SYSTEMCTL status obsservice.service obsservice.service - LSB: open build service source service server Loaded: loaded (/etc/init.d/obsservice; bad; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2018-03-09 11:59:39 UTC; 3min 34s ago Docs: man:systemd-sysv-generator(8) Process: 1761 ExecStart=/etc/init.d/obsservice start (code=exited, status=7) Mar 09 11:59:38 linux systemd[1]: Starting LSB: open build service source service server... Mar 09 11:59:39 linux startproc[1788]: startproc: exit status of parent of /usr/lib/obs/server/bs_service: 13 Mar 09 11:59:39 linux obsservice[1761]: Initializing obsservice..failed Mar 09 11:59:39 linux systemd[1]: obsservice.service: Control process exited, code=exited status=7 Mar 09 11:59:39 linux systemd[1]: Failed to start LSB: open build service source service server. Mar 09 11:59:39 linux systemd[1]: obsservice.service: Unit entered failed state. Mar 09 11:59:39 linux systemd[1]: obsservice.service: Failed with result 'exit-code'. '. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 4

[opensuse-buildservice] OBS + GitHub - deprecation of GitHub Services
by Linux Kamarada 19 Mar '19

19 Mar '19

Hello, guys! I searched how to integrate OBS with GitHub so that a git push would cause OBS to fetch the source code and build. I followed directions on these pages: https://openbuildservice.org/2013/11/22/source-update-via_token/ https://github.com/seccubus/obs_autobuild_test (CC their authors, thank you for the great material!) But when I opened GitHub's Integration & services to add the Obs service, I read this: "Note: [GitHub Services are being deprecated][1]. Please contact your integrator for more information on how to migrate or replace a service with [webhooks][2] or [GitHub Apps][3]." [1]: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ [2]: https://developer.github.com/webhooks/ [3]: https://developer.github.com/apps/differences-between-apps/#about-github-ap… The news is from April 25, 2018. The first paragraph summarizes it: "GitHub plans on shutting down GitHub Services so we can shift focus to other areas of the API, such as strengthening GitHub Apps and GraphQL, and improving webhooks. The intention of GitHub Services was to allow third-party developers to submit code for integrating with their services, but this functionality has been superseded by GitHub Apps and webhooks. GitHub Services has not supported new features since April 25, 2016, and we plan to officially deprecate it on October 1st, 2018." Although I successfully integrated OBS with GitHub using a GitHub Service, is it already possible to do that same integration using GitHub Apps or webhooks? Thank you! 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

7 12

[opensuse-buildservice] build.opensuse.org's Debian:Next project URL is wrong
by Jan Engelhardt 04 Jan '19

04 Jan '19

The URLs in the Debian:Next meta are no longer valid. DoD therefore practically does not work since quite a while. The nearest OBS global project admin: please edit the URLs as per the following change: $ osc meta prj Debian:Next <repository name="update"> - <download arch="x86_64" url="http://ftp.de.debian.org/debian/testing-updates/main" repotype="deb"> + <download arch="x86_64" url="http://ftp.de.debian.org/debian/dists/testing-update/main/" repotype="deb"> (including any other url= occurrences in the XML) -- 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] back-home x86_64 is dead
by munix9 02 Jan '19

02 Jan '19

Hi, back-home x86_64 is dead. https://build.opensuse.org/monitor Happy holidays. Paolo -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 7

[opensuse-buildservice] creating a "backup" of a project with "osc release" possible?
by Stefan Seyfried 02 Jan '19

02 Jan '19

Hi all, First, what do I want to achieve? The VDR project (https://build.opensuse.org/project/show/vdr) will get a version update to version 2.4 in the near future (hopefully ;-) In the past (when updating from 1.6.x to 2.0...) I created a vdr:legacy project where I just copied all sources before updating. I'd like to do something similar now, this time "vdr:2.2", but I'd rather not copy the sources over and build everything again. Instead I was wondering if nifty tricks with "osc release" could be used to achieve what I want. My idea was to temporarily set a release target for vdr (and vdr:plugins) to vdr:2.2, release everything and then remove the release target again. Will this work as I intend it to? Or will the binaries vanish once I remove the release target from the vdr repo? (I doubt it, but who knows ;-) Have fun, seife -- 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

3 3

[opensuse-buildservice] "release management chapter in the OBS book"
by Stefan Seyfried 20 Dec '18

20 Dec '18

Good morning. Quote: ------------------------------------------------------------------------------ seife@vbox-seife:~> osc help release release: Release sources and binaries This command is used to transfer sources and binaries without rebuilding them. It requires defined release targets set to trigger="manual". Please refer the release management chapter in the OBS book for details. ------------------------------------------------------------------------------ I'm desperately seeking for the "OBS book" which contains a "release management chapter". Can anyone help me find it? Have fun, seife -- 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

4 4

[opensuse-buildservice] "State needs recalculations" forever, on a release project
by Julio González Gil 20 Dec '18

20 Dec '18

I am trying to release packages from: https://build.opensuse.org/project/show/systemsmanagement:Uyuni:Master:Cent… to: https://build.opensuse.org/project/show/systemsmanagement:Uyuni:Stable:Cent… With: $ osc release systemsmanagement:Uyuni:Master:CentOS6-Uyuni-Client-Tools <status code="invoked"> <summary>Job invoked</summary> </status> But for some reason only one package (cobbler) was released. I can't see any errors, but no other packages are released, and the status of the repositories is "State needs recalculations, former state was: No build possible atm, waiting for jobs in other repositories" The strange thing is CentOS7 worked fine when I released packages from: https://build.opensuse.org/project/show/systemsmanagement:Uyuni:Master:Cent… to https://build.opensuse.org/project/show/systemsmanagement:Uyuni:Stable:Cent… With: $ osc release systemsmanagement:Uyuni:Master:CentOS7-Uyuni-Client-Tools <status code="invoked"> <summary>Job invoked</summary> </status> It is hard to me to believe that this is a config problem, as meta and project are almost the same at origin and destination (only exception being that at Master:CentOS6-Uyuni-Client- Tools there is an extra patch project to systemsmanagement:Uyuni:Master:Temp). Any idea of what is going on? -- Julio González Gil <jgonzalez(a)suse.com> Release Engineer SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

3 4

[opensuse-buildservice] Doc/experiences about migrations from _product to 000product (old to new format for product definition)
by Julio González Gil 19 Dec '18

19 Dec '18

I reviewed so far: - https://en.opensuse.org/openSUSE:Build_Service_Concept_Product_Definition is outdated (it still refers to _product) - https://speakerdeck.com/openbuildservice/open-build-service-project-workshop (linked at https://openbuildservice.org/help/ is outdated as well) - Nothing at this list https://lists.opensuse.org/cgi-bin/search.cgi? query=000product&advanced.x=0&advanced.y=0&list=opensuse-buildservice I also had a look at the differences between _product for Leap 42.3 and 000product for Leap 15.0 and the only BIG difference I can see so far is that, for 000product, there are .kiwi files. But what puzzles me is that the image definition is still at the .product file. Has anyone here experience with migration from _product to 000product and things we should keep in mind? :-) And one extra question: is the migration mandatory, keeping in mind that our product will be based on SLE15 (SUSE Manager) or openSUSE 15 (Uyuni)? -- Julio González Gil <jgonzalez(a)suse.com> Release Engineer SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

3 2

[opensuse-buildservice] What are the steps required for setting up partitions in the backend?
by Srinidhi B 17 Dec '18

17 Dec '18

Hello Everyone, I couldn't find any resource so far on how to setup partitions on the backend. There is a reference about partitions on the OBS Architecture page [1] in the reference guide, but no instructions on how to go about setting things up. While searching the archives of this list, I came across one thread where Adrian suggested [2] what is explained in BSConfig.pm. I want to split backends for "existing" projects (let's say, home:). From what I understand from reading code, only "newer" content will be pushed / moved to the partitioned servers. My questions are: - What contents should I be moving to the new partitioned server? (e.g., partitioning home: projects) * /srv/obs/build/home:* * /srv/obs/repos/home:/* - Do I need move any other data? - Do I need to stop all backend services on the main server before moving this data? I'm assuming yes, but wanted a confirmation. - Do I need to run or check something else after moving the data over to partitioned server(s)? Regards, Srinidhi. [1] https://openbuildservice.org/help/manuals/obs-reference-guide/cha.obs.archi… [2] https://lists.opensuse.org/opensuse-buildservice/2016-07/msg00041.html -- 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] Phantom binaries in openSUSE:Factory:PowerPC/standard/ppc/_repository
by Andreas Schwab 13 Dec '18

13 Dec '18

The repository in openSUSE:Factory:PowerPC/standard/ppc contains a lot of binaries that are not originating from any package build. Especially the python{2,3}-pluggy.rpm binaries are obnoxious because they are overriding the ones built from the python-pluggy package. $ osc api build/openSUSE:Factory:PowerPC/standard/ppc/_repository | grep python.-pluggy <binary filename="python2-pluggy.rpm" size="31706" mtime="1513504048" /> <binary filename="python3-pluggy.rpm" size="31974" mtime="1513504048" /> $ osc api build/openSUSE:Factory:PowerPC/standard/ppc/python-pluggy | grep python.-pluggy <binary filename="python2-pluggy-0.7.1-1.1.noarch.rpm" size="38904" mtime="1538147591" /> <binary filename="python3-pluggy-0.7.1-1.1.noarch.rpm" size="39604" mtime="1538147591" /> When I disable useforbuild in the python-pluggy package the phantom binaries disapper, and reenabling useforbuild brings the correct binaries into the repository. But after some time the phantom binaries reappear. Other than that there are about 150 phantom binaries in the repository. 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

1 1

[opensuse-buildservice] News from OBS UI revamp!
by Saray Cabrera Padron 12 Dec '18

12 Dec '18

People of the Builds! We have done some progress in revamping the user interface of OBS. This time we have focused on project, user and group pages. Please try it out and give us feedback! We'dbe happy to read your comments and make it even better! More details in our blog post: https://openbuildservice.org/2018/12/10/revamping-project-ui/ -- Saray A. Cabrera Padrón | scabrerapadron(a)suse.de | scabrerapadron(a)suse.com Full Stack Web Developer - Open Build Service SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

4 4

[opensuse-buildservice] Random delays during worker start
by Keil, Karsten 11 Dec '18

11 Dec '18

Hello, In our private OBS instance we use KVM workers on SLE12S-SP3. The build servers are HP DL380 Gen9 with 40 cores with 256GB RAM for big workers, 128 GB Ram for smaller ones. On such HW we running for example 10 instances with 3 Jobs. The Problem is that after the initial install stage here are very often (I would say ~ 1/3 of the builds) huge delays in the start of the VM: A good one: .... [ 10s] booting kvm... [ 10s] ### VM INTERACTION START ### [ 11s] /usr/bin/qemu-kvm -nodefaults -no-reboot -nographic -vga none -object rng-random,filename=/dev/random,id=rng0 -device virtio-rng-pci,rng=rng0 -runas qemu -cpu host -net n [ 11s] [ 1.063999] dracut-pre-udev[161]: modprobe: FATAL: Module kqemu not found. [ 12s] [ 2.047790] dracut-pre-udev[161]: modprobe: FATAL: Module ibmvscsi not found. [ 12s] [ 2.052451] dracut-pre-udev[161]: modprobe: FATAL: Module ibmveth not found. [ 12s] ### VM INTERACTION END ### [ 12s] 2nd stage started in virtual machine [ 12s] machine type: x86_64 ... Bad looks like: ... [ 11s] booting kvm... [ 12s] ### VM INTERACTION START ### [ 12s] /usr/bin/qemu-kvm -nodefaults -no-reboot -nographic -vga none -object rng-random,filename=/dev/random,id=rng0 -device virtio-rng-pci,rng=rng0 -runas qemu -cpu host -net n [ 12s] [ 1.437692] dracut-pre-udev[161]: modprobe: FATAL: Module kqemu not found. [ 111s] [ 98.122901] dracut-pre-udev[161]: modprobe: FATAL: Module ibmvscsi not found. [ 112s] [ 99.982451] dracut-pre-udev[161]: modprobe: FATAL: Module ibmveth not found. [ 112s] ### VM INTERACTION END ### [ 112s] 2nd stage started in virtual machine [ 112s] machine type: x86_64 ... This could also up to 300 seconds, I do not really found a relationship to the size of the build jobs or amount of packages to install. Also the build itself seems not to be much slower after the delay. The host itself does not have any high load at these moments, most of CPUs is idle. So my questions are: What exact happens in that stage of the VM start, are there copies of the initial packages ongoing ? Does somebody see similar things ? OBS version is 2.92. Thank you Karsten Keil The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

[opensuse-buildservice] Only root can link in OBS
by Till Dörges 09 Dec '18

09 Dec '18

Hello all, I have a weird problem with a package on a private OBS (x86-64, 2.9.4). It's basically a C program against some external proprietary lib. On any developer's machine it builds just fine with: ./configure make make install for both openSUSE Leap 42.3 (x86-64) and openSUSE Leap 15.0 (x86-64). I put the sources in OBS with the following in my SPEC file --- snip --- [...] %build %{_configure} %{__make} %install # Don't want to register our ext. lib via /etc/ld.so.conf.d/XXX.conf or similar. # Therefore we go with an rpath for the time being. export NO_BRP_CHECK_RPATH=true %{make_install} [...] --- snip --- Compiling works fine. Problem now is, the %{__make} fails when trying to link the final binary with lots of "undefined reference to" symbols from the external proprietary lib. What does work, is to use root4abuild or similar and then adjust the SPEC file like so sudo %{__make} instead of %{__make}. Obviously I don't want to stick with that, but I have no idea on how to debug this any further. Any hints would be greatly appreciated! Thanks and regards -- Till -- Dipl.-Inform. Till Dörges doerges(a)pre-sense.de Tel. +49 - 40 - 244 2407 - 0 Fax +49 - 40 - 244 2407 - 24 PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 4

[opensuse-buildservice] Are aarch64 workers broken today?
by Julio González Gil 07 Dec '18

07 Dec '18

I see some of my packages failing to build with the following error (or similar, as /var/cache/obs/worker/root_7/ changes for each package): ---------- [ 15s] ### VM INTERACTION START ### [ 15s] /usr/bin/qemu-system-aarch64 -nodefaults -no-reboot -nographic -vga none -enable-kvm -cpu host -M virt,gic-version=host -object rng- random,filename=/dev/hwrng,id=rng0 -device virtio-rng-device,rng=rng0 -runas qemu -net none -kernel /var/cache/obs/worker/root_7/.mount/boot/kernel -initrd /var/cache/obs/worker/root_7/.mount/boot/initrd -append root=/dev/disk/by-id/ virtio-0 rootfstype=ext4 rootflags=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=ttyAMA0 init=/.build/build -m 4096 -drive file=/var/cache/obs/worker/root_7/ root,format=raw,if=none,id=disk,serial=0,cache=unsafe -device virtio-blk- device,drive=disk -drive file=/var/cache/obs/worker/root_7/ swap,format=raw,if=none,id=swap,serial=1,cache=unsafe -device virtio-blk- device,drive=swap -serial stdio -chardev socket,id=monitor,server,nowait,path=/var/cache/obs/worker/root_7/root.qemu/ monitor -mon chardev=monitor,mode=readline -smp 6 [ 15s] qemu-system-aarch64: -drive file=/var/cache/obs/worker/root_7/ root,format=raw,if=none,id=disk,serial=0,cache=unsafe: 'serial' is deprecated, please use the corresponding option of '-device' instead [ 15s] qemu-system-aarch64: -drive file=/var/cache/obs/worker/root_7/ swap,format=raw,if=none,id=swap,serial=1,cache=unsafe: 'serial' is deprecated, please use the corresponding option of '-device' instead [ 321s] ### WATCHDOG TRIGGERED, KILLING VM ### [ 322s] /var/cache/obs/worker/root_7/root: 6794 [ 322s] qemu-system-aarch64: terminating on signal 15 from pid 13040 () [ 322s] ### VM INTERACTION END ### [ 322s] /var/run/obs/worker/7/build/build-vm: line 462: kill: (6787) - No such process [ 322s] No buildstatus set, either the base system is broken (kernel/initrd/ udev/glibc/bash/perl) [ 322s] or the build host has a kernel or hardware problem... gave up after 13 failed build attempts... ---------- As far as I can tell, the following workers are affected: * obs-arm-1: https://build.opensuse.org/build/ systemsmanagement:Uyuni:Master:Temp/SLE_12/aarch64/python-argparse/_log * obs-arm-2: https://build.opensuse.org/build/ systemsmanagement:Uyuni:Master:SLE12-Uyuni-Client-Tools/SLE_12/aarch64/mgr- daemon/_log * obs-arm-7: https://build.opensuse.org/build/ systemsmanagement:Uyuni:Master:SLE12-Uyuni-Client-Tools/SLE_12/aarch64/ spacewalk-koan/_log and https://build.opensuse.org/build/ systemsmanagement:Uyuni:Master:Temp/SLE_12/aarch64/python3-base/_log I can't see anything reported at https://status.opensuse.org/ -- Julio González Gil <jgonzalez(a)suse.com> Release Engineer SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

1 1

[opensuse-buildservice] build.opensuse.org: command not found
by Nicolas Quiniou-Briand 05 Dec '18

05 Dec '18

Hello, Thanks for this great service/software ! I'm trying to build a test package on build.opensuse.org [0] but I got this error: ``` [ 68s] /usr/bin/asciidoctor \ [ 68s] -n \ [ 68s] README.asciidoc [ 68s] make: /usr/bin/asciidoctor: Command not found [ 68s] make: *** [html] Error 127 [ 68s] error: Bad exit status from /var/tmp/rpm-tmp.3YzfxW (%build) ``` That's strange because rubygem-asciidoctor-1.5.6.1-1.el7 has been installed before by the worker. I added the EPEL repository to my repositories list. On my laptop, I'm able to build this package in a CentOS 7 VM with rubygem-asciidoctor-1.5.6.1-1.el7 package installed. I didn't find any help in documentations regarding this issue. [0] https://build.opensuse.org/package/live_build_log/home:nqb/hello-doc/CentOS… -- Nicolas Quiniou-Briand -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

[opensuse-buildservice] OBS Administrator ERROR
by Christof Hanke 03 Dec '18

03 Dec '18

Hi, I get from my private OBS instance mails with subject given above and it says : """ Additional projects in api: ["deleted"] Additional projects in backend: ["xxx", "yyy"] """ How can I clean this up safely? Many thanks, Christof -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2