March 2017 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Open Build Service (OBS) 2.7.4 released
by Björn Geuken 16 Mar '17

16 Mar '17

OBS 2.7.4 released ================== This release fixes several bugs. For more details please look into the ReleaseNotes. Updaters from any OBS 2.7.0 release can just upgrade 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.7 The appliance can be downloaded from http://openbuildservice.org/download =============================================================== Release Notes of 2.7.4: - OBS 2.7.4 release Feature backports: ================== * none Changes: ======== * none Bugfixes: ========= * [api] Fix API permission check for creating and changing (POST) attributes * [api] Fix API permission check for deleting (DELETE) attributes * [webui] Invalidate cached session in LDAP mode * [api][webui] Fail ldap authentification with empty password * [webui] Fix repository removal when updating project meta fails with an error -- Björn Geuken - Rails Developer - Open Build Service SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) -- 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] Track statistics on the openSUSE staging process to gain feedback on changes
by Jimmy Berry 15 Mar '17

15 Mar '17

I am looking to provide a variety of statistics and metrics relating to the staging workflow on OBS in onder to see the impact of automation and tune the tools. I have spent some time setting up a local OBS, obs_factory engine, looking through the database structure, and reviewing tools designed to present metrics. My understanding from @hennevogel is that Influx Data is planned to be used to provide this type of information and it makes sense to get a feel for the existing plans and how this may fit into that. The biggest hurdle seems to be trying to create timeseries information from event data by walking the events backwards from the known state (ie current) to find states of interest. At some point whatever solution is built will need access to the relevant data to do some aggregation and store intermediate results that can then be drawn on for presentation. Alternatively, I had some success using sub-selects, but that is likely not the most performant way forward. Given the design of the submit request/staging workflow, that no events are recorded after a request is declined, it is not possible to determine when a obsolete request was unstaged. The overall state of stagings cannot be accurately determined when such a workflow has occurred. It will likely also be difficult/impossible to determine when a build state complete, re-entered building due to manual rebuilds or re-freeze, or failed/passed testing. The dashboard [1] already provides this information, but re-creating a history in an aggregate form is likely near impossible if not very difficult. As such it likely makes sense to create a new polling job that stores facets of the information collected by the dashboard in a timerseries database. For the rest of the information tied specific to individual requests it seems possible to figure everything out from a handful of tables in the OBS database. Alternatively, I can write something that polls and scrapes data using the APIs into local storage, but that seems like unnecessary extra work. Is it feasible for me to be granted read access to the few tables of interest or the Influx/similar tool setup with access so that I can begin setting up some metrics of interest? A bit more on the topic of generating timeseries data. As an example, consider presenting a graph of the request backlog against Factory over time, the time until first staging, or the number of empty stagings over time. The event information is collected in the form of reviews. Anytime the request is staged or re-staged reviews for the particular staging project are added or accepted. Accepting or declining the request unfortunately stops future changes from being recorded which means the staging tools cannot indicate when the request is removed from a staging, but for simplicity it can be assumed complete after one of those states. Assuming one has a known state from which to start it should be possible to walk the event history and annotate states of interest. Given that the current state can be queried which indicates what requests are currently in a staging that provides a starting point. Assuming the script can be stopped anytime it encounters an annotation again (or other mechanism) the job can be run on some timely basis to annotate the desired information. The polling technique could be used to avoid all this walking the event history which is simpler, but cannot backfill the data. As such it is preferable to walk the event tree where possible. I look forward to your thoughts. [1] https://build.opensuse.org/project/staging_projects/openSUSE:Factory -- Jimmy -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 7

[opensuse-buildservice] Request for testing
by Adrian Schröter 14 Mar '17

14 Mar '17

Hi, we have a new (login) proxy host which handles all traffic to OBS. The plan is to switch to it by default on thursday. But you may want to give it a try before by adding the following line to your /etc/hosts 195.135.221.161 api.opensuse.org build.opensuse.org The new host is also connected in a different way to our OBS instance. We hope that traffic of other services won't affect the OBS traffic anymore. any feedback would be great, even when nothing changes to you ;) thanks adrian -- Adrian Schroeter email: adrian(a)suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 5

[opensuse-buildservice] Build issues against openSUSE Tumbleweed
by Dimstar / Dominique Leuenberger 13 Mar '17

13 Mar '17

On Mon, 2017-03-13 at 16:25 +0100, Dimstar / Dominique Leuenberger wrote: > Dear hackers and packagers, > > My sincere apologies - once again we are struck by a delete request > having impacts way beyond what we expect to to touch. > > As part of the cleanup activities, gcc5 has been removed from the > distro. This also impacts libffi4; The distro has gained a new libffi > implementation (libffi7, version 3.2.1) which has been around for a > while. > > As we now deleted libffi4, though, it became apparent that not > everything is yet rebuilt against libffi7 (no real surprise there: we > have the rebuild strategy of least changes implemented) > > So far nothing bad - except: as libffi4 has been removed from > openSUSE:Factory, this not only impacts /standard (which we would not > have a problem - ever), but also /snapshot. Which means all the > builds > against openSUSE:Tumbleweed will be broken at least until the next > snapshot can be published (0313 that is). > > I apologize for this issue caused and will be trying to find a > workaround for now to get you guys going again. Please stay tuned. I filed this as https://progress.opensuse.org/issues/17688 Any ideas are welcome on how to avoid this in the future - the more automatic it is, the higher the chance of it not failing again. Please keep the discussion on -buildservice or in the ticket. -packaging should merely be informed of the outcome in the end. Cheers, Dominique -- Dimstar / Dominique Leuenberger <dimstar(a)opensuse.org>

4 5

[opensuse-buildservice] Problems with services
by Ingo Göppert 13 Mar '17

13 Mar '17

Hi, fetching sources via http, for example in https://build.opensuse.org/package/show/spins:invis:testing/SOPE does not work. Error message is: > service download_url failed: > /bs/service/4574 > /bs/service/4574/src > /bs/service/4574/src/SOPE.changes > /bs/service/4574/src/SOPE.spec > /bs/service/4574/src/_link > /bs/service/4574/src/_service > /bs/service/4574/src/.old > /bs/service/4574/src/.old/_service:download_url:SOPE-2.3.19.tar.gz > /bs/service/4574/out > /bs/service/4574/var > /bs/service/4574/var/cache > /bs/service/4574/var/cache/obs > /bs/service/4574/var/cache/obs/NCqG7DDBtIiS > /bs/service/4574/var/cache/obs/NCqG7DDBtIiS/scripts > /bs/service/4574/var/cache/obs/NCqG7DDBtIiS/scripts/inner.sh > /bs/service/4574/var/cache/obs/NCqG7DDBtIiS/scripts/inner.sh.command > docker: Error response from daemon: devmapper: Thin Pool has 7780 free > data blocks which is less than minimum required 7782 free data > blocks. Create more free space in thin pool or use dm.min_free_space > option to change behavior. See 'docker run --help'. Is this a problem at the buildservice-servers or is there something wrong in our packages? Ingo -- 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] initial configuration.xml
by Dinar Valeev 10 Mar '17

10 Mar '17

Hi, Is there a way to provide initial configuration.xml prior private instance start? I tried to place configuration.xml into OBS_DIR, but /configuration still reports previously configured values. What is the correct way to change configuration before service is started? Thanks, Dinar -- 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] api build cpio error 400
by Bernhard M. Wiedemann 10 Mar '17

10 Mar '17

> osc api "/build/SUSE:SLE-12:GA/standard/x86_64/_repository?binary=bash&view=cpio" Server returned an error: HTTP Error 400: remote error connect Connection refused remote error: connect Connection refused seems to be the minimal reproducer that prevents me from building packages for SLE in OBS And that also stops my experiment at https://build.opensuse.org/project/show/home:bmwiedemann:backports:SLE-12-S… -- 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] osc 0.157 is incompatible
by Olaf Hering 09 Mar '17

09 Mar '17

osc-0.157.1.rpm fails to run 'osc r -v': Server returned an error: HTTP Error 400: unknown parameter 'multibuild', 'locallink' unknown parameter 'multibuild', 'locallink' Version 0.156.0 works with the same. Olaf

3 2

[opensuse-buildservice] interconnect error: unknown host 'api.opensuse.org'
by Oliver Herrmann 08 Mar '17

08 Mar '17

Hi, after we moved our OBS appliance into a different network and assigning a new IP address we can't build anymore. The "Build Results" box in the Web GUI shows "broken" for all repositories. When moving the mouse over broken it displays "interconnect error: unknown host 'api.opensuse.org' ". DNS lookup is working since I can ping that address. Can somebody help please? Cheers Oliver -- 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] /usr/share/texmf/texconfig/update: No such file or directory
by Detlef Steuer 07 Mar '17

07 Mar '17

Hi! (first mail didn't make it to the list it seems) Project devel:languages:R:released/R-base The spec file is unchanged modulo version numbers (new upstream release). There were binaries before. Now I get /var/tmp/rpm-tmp.RKuIVr: line 3: /usr/share/texmf/texconfig/update: No such file or directory in various repos, but not all. Factory/tumbleweed/SL-12 work, but Leap* and others don`t. Happens during setup, before configure. I didn't change anything regarding texlive as far as I know. Any hint? Detlef -- "Wisely and slow. Those stumble that run fast." Shakespeare -- Romeo and Juliet -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 10