openSUSE Build Service March 2019

buildservice@lists.opensuse.org

17 participants
16 discussions

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

12 months

Changing the OBS server's FQDN

by Morschhäuser, Mark

Hi, I found out that our OBS internally uses a wrong domain name: I saw the name as an alias in /etc/hosts, removed it and then the web UI did not show any build results anymore. After changing it back in /etc/hosts, it worked again. I guess some service uses the wrong name and maybe also the database from OBS contains the name somehow. I saw that some perl files in /usr/lib/obs/server use Net::Domain::hostfqdn(); from perl to resolve the hostname and it looks into /etc/resolv.conf and takes the first domain from the search(!) entry which is a bug I think. This is probably how the wrong domain name was introduced in the first place. Now... how can I change the currently used FQDN to the right one for all services and everything? Also: I actually wanted to find out how to change the URL for the package download from the Binaries page ("Detailed Information About foo.rpm" links to http://localhost/build/<Project>/<arch>/foo/foo.rpm and the localhost must be configurable somewhere - or it is resolved again and defaults to localhost because the resolve does not work properly). 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 year, 7 months

OBS Appliance - Unable to Update

by Khalil Graves

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

1 year, 7 months

OBS publisher queue in deep trouble

by Stephan Kulow

Hi, For everyone waiting for her packages to appear on download server, there are currently good and bad news. The good news first: you have more time for other hobbies. The bad news: it might take quite some time for the situation to restore. The openSUSE Leap 15.0 repos were triggered for republishing and our infrastructure has serious trouble getting through the backlog. I put some more data on the github issue: https://github.com/openSUSE/open-build-service/issues/7281#issuecomment-477… I hope this helps. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 year, 8 months

OBS is stuck since yesterday

by munix9

A large number of projects/repositories are set to status "Build jobs have been processed, new repository is not yet created" regards Paolo -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 year, 8 months

No new repository created since more then 12 hours

by Ralf Becker

Build jobs from yesterday evening (egroupware-collabora-key) have not yet resulted in a new repository: https://build.opensuse.org/project/monitor/server:eGroupWare Any idea why? Anything I can do? Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

1 year, 8 months

osc and gnome keyring

by Tony Jones

Hi Can anyone offer any advice on how to get this to work. In the past it worked for me but lately I've been unable to get it to work and I've had to resort to, ahem, clear text passwords. https://en.opensuse.org/openSUSE:OSC "There have been reports that with ... add solely the line gnome_keyring=1 instead of keyring=1 to the server section." Is "instead of keyring=1" correct or does it mean instead of "use_keyring=1"? Anyways, I've tried every version of use_keyring=1, keyring=1, gnome_keyring=1, removing python2-keyring and all I get is "Server returned an error: HTTP Error 401: Unauthorized" This is using a basic 'osc list' query I have an entry in my gnome keyring for <my external userid>@api.opensuse.org. It's unfortunate that the debug/verbose options don't provide any info about the interaction with the keyring as if I remove the opensuse entry from the keyring I get the exact same error so it's hard to tell what is occurring. Thanks $ rpm -q openSUSE-release openSUSE-release-20190320-77.1.x86_64 $ osc --version 0.164.2 $ osc -d -v -A https://api.opensuse.org list makeurl: https://api.opensuse.org ['source'] {} GET https://api.opensuse.org/source Server returned an error: HTTP Error 401: Unauthorized Date: Fri, 22 Mar 2019 19:24:40 GMT Server: Apache/2.4.23 (Linux/SUSE) WWW-Authenticate: Basic realm="Use your novell account" Vary: accept-language,accept-charset Strict-Transport-Security: max-age=31536000 Upgrade: h2 Connection: Upgrade, close Accept-Ranges: bytes Transfer-Encoding: chunked Content-Type: text/html; charset=utf-8 Content-Language: en <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head> <title>Authentication required!</title> <link rev="made" href="mailto:%5bno%20address%20given%5d" /> <style type="text/css"><![CDATA[/*></style> </head> <body> <h1>Authentication required!</h1> <p> This server could not verify that you are authorized to access the URL "/source". You either supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required. </p> <p> In case you are allowed to request the document, please check your user-id and password and try again. </p> <p> If you think this is a server error, please contact the <a href="mailto:%5bno%20address%20given%5d">webmaster</a>. </p> <h2>Error 401</h2> <address> <a href="/">api.opensuse.org</a><br /> <span>Apache/2.4.23 (Linux/SUSE)</span> </address> </bod -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 year, 8 months

Probleme nach .oscrc -> .config/osc/oscrc

by Christian

Hello since I moved my stuff from '.oscrc' to '.config/osc/oscrc' I have a problem with my 'alias' entry ... admin@lap:~/MyOBS/SIT:com> osc -A obs meta -e pkg test Failed to reach a server: invalid apiurl 'obs' (specify the protocol (http:// or https://)) config in '.oscrc' did work and it looks like: [https://api.opensuse.org] user=computersalat passx= email=chris(a)computersalat.de trusted_prj= [https://api.de.scorpio-it.net] alias=obs user=computersalat passx= email=chris(a)computersalat.de trusted_prj= [https://pmbs-api.links2linux.org] alias=pmobs user=computersalat passx= email=chris(a)computersalat.de trusted_prj= What am I missing now ? Thanks for help -- Christian ------------------------------------------------------------ https://join.worldcommunitygrid.org?recruiterId=177038 ------------------------------------------------------------ http://www.sc24.de - Sportbekleidung ------------------------------------------------------------

1 year, 8 months

putting files to OTHER directory and its availability in the API

by Stanislav Brabec

Hi. I am trying to implement a new translation update process. I need to export pot files from the build process. I have been told that files copied into %{_topdir}/OTHER will become available at api.opensuse.org after the build. But it is a half true. It works only for i586 but not x86_64. Is there any other step needed to get it working? https://build.opensuse.org/package/view_file/home:sbrabec:branches:Base:Sys… See %prep stage and the end of %install phase just above %pre. Log cleanly shows that it works correctly for x86_64: https://build.opensuse.org/public/build/home:sbrabec:branches:Base:System/o… [ 589s] + tar -jcf /home/abuild/rpmbuild/OTHER/pot.tar.bz2 po-suse/grub2-suse.pot [ 589s] + ls -al /home/abuild/rpmbuild/OTHER [ 589s] total 12 [ 589s] drwxr-xr-x 2 abuild abuild 4096 Mar 20 16:49 . [ 589s] drwxr-xr-x 9 abuild abuild 4096 Mar 20 16:40 .. [ 589s] -rw-r--r-- 1 abuild abuild 2312 Mar 20 16:49 pot.tar.bz2 But https://api.opensuse.org/build/home:sbrabec:branches:Base:System/openSUSE_F… does not contain any reference to pot.tar.bz2 https://api.opensuse.org/build/home:sbrabec:branches:Base:System/openSUSE_F… does: <binary filename="pot.tar.bz2" size="2315" mtime="1553100342" /> -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.com Křižíkova 148/34 (Corso IIa) tel: +420 284 084 060 186 00 Praha 8-Karlín fax: +420 284 084 001 Czech Republic http://www.suse.cz/ PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 year, 8 months

Ubuntu_Next:universe libsdl2 version is wrong

by Rosanne DiMesio

The version of libsdl2 in the Ubuntu disco universe repository is 2.0.9 (https://packages.ubuntu.com/disco/libsdl2-2.0-0), but my FAudio build for Ubuntu_Next installs libsdl2 2.0.8. If I specify libsdl2 >= 2.0.9 in the .dsc file, I get an unresolvable error. Is Ubuntu_Next_universe maybe still pointing to an older repository? -- 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

1 year, 8 months

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service March 2019