May 2017 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] OBS down...?
by Giovanni Santini 15 May '17

15 May '17

Good morning, I was going to update my ArchLinux packages when I've noticed OBS was down. It seems down from yesterday... Any ideas? -- Giovanni Santini My blog: http://giovannisantini.tk My code: https://git{hub,lab}.com/ItachiSan My GPG: 2FADEBF5 -- 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] kiwi image build: nothing provides this-is-only-for-build-envs
by Tobias Klausmann 14 May '17

14 May '17

Hi, on my way to build a kiwi appliance in one of my repos [1], i hit some unmet dependencies: unresolvable: nothing provides this-is-only-for-build-envs needed by libudev-mini1 nothing provides this-is-only-for-build-envs needed by systemd-mini nothing provides this-is-only-for-build-envs needed by libsystemd0-mini nothing provides this-is-only-for-build-envs needed by udev-mini while researching the problem, i have tried to add Ignores to my project config, but without luck: Ignore: systemd-mini:this-is-only-for-build-envs Ignore: libsystemd0-mini:this-is-only-for-build-envs Ignore: udev-mini:this-is-only-for-build-envs Ignore: libudev-mini1:this-is-only-for-build-envs Any hints how to solve this, without creating a fake package with that name? [1] https://build.opensuse.org/projec/show/home:tobijk:Edison:Tumbleweed Greetings, Tobias -- 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] Unable to force lower version of package
by Till Dörges 11 May '17

11 May '17

Hello all, I'm running a private OBS 2.7 instance. For one of my projects A I have this in my meta configuration: --- snip --- <repository name="openSUSE_Leap_42.2"> [...] <path project="openSUSE.org:Leap:42.2:Update" repository="standard"/> <path project="openSUSE.org:Leap:42.2" repository="standard"/> <arch>x86_64</arch> </repository> --- snap --- A package B in project A has one BuildRequires, which in turn pulls in another package C (via Requires). Now C has a requires for a standard Leap 42.2 package D but with a version constraint. The required version of D is present in the Leap 42.2 repo. The version in the Leap 42.2 update repo is too high (from /srv/obs/log/scheduler_x86_64.log): --- snip --- 2017-05-10 20:28:59: looking at low prio A/openSUSE_Leap_42.2 (0/0/0/0/42) - A/openSUSE_Leap_42.2 scanning repo A/openSUSE_Leap_42.2... sorting 1 packages - B (spec) unresolvable: nothing provides D < 2.1.3 needed by C --- snap --- If I change the above meta configuration to --- snip --- <repository name="openSUSE_Leap_42.2"> [...] <path project="openSUSE.org:Leap:42.2" repository="standard"/> <arch>x86_64</arch> </repository> --- snap --- package B builds fine. But I'd like to use the RPMs from the update repository. How would I have to configure that? Or how can I track down this dependency issue? Thanks and regards -- Till -- Dipl.-Inform. Till Dörges doerges(a)pre-sense.de Tel. +49 - 40 - 244 2407 - 14 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 Wir sind wieder auf dem BSI IT-Sicherheitskongress 16.-18. Mai 2017 – Bonn -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] Open Build Service (OBS) 2.8.1 released
by Eduardo Navarro 10 May '17

10 May '17

OBS 2.8.1 released ================== This release fixes several bugfixes. For more details look at the release notes you can find below. Updaters from any OBS 2.8 release can just ugrade the packages and restart all services. Updaters from former releases should read the README.UPDATERS file. OBS update are available from the following projects: https://build.opensuse.org/project/show/OBS:Server:2.8 The appliance can be downloaded from http://openbuildservice.org/download Details from the Release Notes of 2.8.1: ======================================== Feature backports: ================== * [api][webui] Copy repositories when branching from a remote project Changes: ======== * Removed obsolete option api_relative_url_root * [backend] Implements 'donotcreatecert' option for _keyinfo Bugfixes: ========= * [webui] Fixes a bug in branch and submit dialog * [webui] Fixes a bug in live build log when no architecture or repository parameter was given * [webui] Fixes a bug in live build log when the package is a multibuild * [backend] Handles arch dependencies correctly -- Greetings, Eduardo J. -- 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] pcc64le hosts down?
by Bernhard Voelker 10 May '17

10 May '17

I see a pcc64le job as "scheduled" for 6 days now [1], with the tooltip message: "waiting for 96 compliant workers (51 of them down)" Is there something stuck? Thanks & have a nice day, Berny [1] https://build.opensuse.org/request/show/492649 -- 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] branching from working copy fails
by Olaf Hering 10 May '17

10 May '17

Branching a pkg from one prj to another fails if osc is called from a copy of prj: olaf@satriani:~/work/obs/home:olh:ocaml $ obs branch devel:languages:ocaml ocaml-curses home:olh:ocaml Traceback (most recent call last): File "/usr/bin/osc", line 41, in <module> r = babysitter.run(osccli) File "/usr/lib/python2.7/site-packages/osc/babysitter.py", line 61, in run return prg.main(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 343, in main return self.cmd(args) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 366, in cmd retval = self.onecmd(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 500, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 1230, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python2.7/site-packages/osc/commandline.py", line 3414, in do_branch if conf.get_configParser().get('general', 'apiurl') != apiurl: File "/usr/lib64/python2.7/ConfigParser.py", line 607, in get raise NoSectionError(section) ConfigParser.NoSectionError: No section: 'general' olaf@satriani:~/work/obs/home:olh:ocaml $ .. olaf@satriani:~/work/obs $ obs branch devel:languages:ocaml ocaml-curses home:olh:ocaml BuildService API error: failed to branch: branch target package already exists: home:olh:ocaml/ocaml-curses To me it looks like doing the branch is working fine, but dealing with the result is what confuses osc. I tried it with another pkg (ocaml-dbus) and that one failed in the same way. rpm -q --changelog osc | head * Di Mai 09 2017 marco.strigl(a)suse.com - 0.158.0 Olaf

2 2

[opensuse-buildservice] Add a proper ARM Download on Demand Repository
by Mathias Radtke 09 May '17

09 May '17

Hi, I am currently trying to add a proper download on demand URL to my repositories. The current one looks like this: <repository name="Debian_8.0"> <download arch="armv7l" url="ftp://ftp.de.debian.org/debian/dists/jessie/main/binary-armhf/" repotype="deb"> <pubkey>{}</pubkey> </download> <arch>armv7l</arch> <path project="openSUSE.org:Debian:8.0" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> However the dodup.log tells me that this fails 2017-05-03 05:52:00: [1002] checking home:uibmz:opsi:opsi41-experimental/Debian_8.0/armv7l... updating metadata for deb repo at ftp://ftp.de.debian.org/debian/dists/jessie/main/binary-armhf/ bad uri: ftp://ftp.de.debian.org/debian/dists/jessie/main/dists/binary-armhf/Release Where does this additional dists substring come from? I didn't add this in my url as seen in the log. Any suggestion how to properly add debian based ARM Repos to my local instance? Cheers -- Mathias Radtke --- http://uib.de/de/support-schulung/schulung/ --- uib gmbh Bonifaziusplatz 1B 55118 Mainz Tel. 06131 / 27561-16 <phone:061312756116> Fax 06131 / 27561-22 <phone:061312756122> E-Mail: m.radtke(a)uib.de Internet: www.uib.de Geschäftsführer: dr. detlef oertel & erol ueluekmen Handelsregister: Amtsgericht Mainz HRB 6942 -- 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] OBS frontend 1st sprint report
by Henne Vogelsang 08 May '17

08 May '17

Hey, following the YaST Teams brilliant example, the OBS frontend team started to write sprint reports. Enjoy the first development report from the team while it's fresh! http://openbuildservice.org/2017/05/05/frontend-sprint-report-1/ You OBS Team -- 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

1 0

[opensuse-buildservice] Short downtime of build.opensuse.org
by Eduardo Navarro 08 May '17

08 May '17

Hi! We are now going to repeat a failed deployment from last week, and you might experience a short (less than 5 minutes) downtime of build.opensuse.org. Please bare with us. Greetings, OBS team. -- 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] What defines the package version in OBS as later shown version in https://software.opensuse.org
by Dominig ar Foll (Intel Open Source) 03 May '17

03 May '17

Hello, I maintain the packages for the navigation SW OpenCPN and I use a sandbox in my home for testing new releases and fixing build an integration issues. When my test are completed (users do not like to discover bugs when at sea) I copy the project on the publication repo Application:Geo:OpenCPN with osc copypac. - https://build.opensuse.org/package/show/Application:Geo:OpenCPN/OpenCPN-4.x… - https://build.opensuse.org/project/show/home:dominig:opencpn-sandbox Knowing that as today both packages are at the same release 4.6.1, I do not understand why the release shown in https://software.opensuse.org for home:dominig:opencpn-sandbox claims to be at release 4.6.1 while the one from Application:Geo:OpenCPN indicates release 4.6.0. This is annoying as it can lead user to take my sandbox version as source and get in trouble when I will integrate the new release. The actual packages are are the same in both repos (4.6.1) https://build.opensuse.org/package/binaries/Application:Geo:OpenCPN/OpenCPN… The published packages are at the correct release in both repo, only the release indication for 'one click install' is incorrect. Questions: - where does come the version indication in https://software.opensuse.org ? - is there a way to publish packages without getting them listed in https://software.opensuse.org ? I would love such feature to restrict visibility of my sandbox to my beta tester only. I only know the flag publish or nor publish which is too violent for my use case. A flag in project meta to remove publication from https://software.opensuse.org would be very handy. Thanks. -- 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 1