September 2013 - openSUSE Build Service

Re: [opensuse-buildservice] Stalled submit requests
by Matwey V. Kornilov 18 Feb '15

18 Feb '15

Hm... You have inspired me to try this on the coming weekend. :) With obs rest/xml api, I need a tiny python script to manage all the things out. It is easy, you're right. 2012/10/18 Jos Poortvliet <jos(a)opensuse.org>: > On Sunday, October 07, 2012 12:09:43 Matwey V. Kornilov wrote: > >> Hi, > >> > >> Is there a page to see full list of submit requests, ordered by date? This > >> statistics is of quite interest. > >> > >> For instance, there is no reaction for two month: (It is not ok for devel: > >> project, I think) > >> > >> >> https://build.opensuse.org/project/requests?project=network%3Amessaging%3Aam > >> qp > >> > >> I think, having such a page, such statistics, one would be able to > >> redistribute his power. > > > > Not a bad idea at all - it'd nice to show which projects need some help, > which are doing very well etcetera. Maybe a top-ten of fastest SR/MR > solvers, too ;-) > > > > Crazy idea: Adrian responded to you that it is possible to request this info > from the API. If you got the skillzz to do that, it'd be nice to publish > those statistics somewhere - and that part I could help with. Something like > a weekly overview of the health of the OBS projects and stuff like that. > > > > Up for it? > > > > /Jos -- With best regards, Matwey V. Kornilov http://0x2207.blogspot.com xmpp:0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 9

[opensuse-buildservice] Open Build Service(OBS) 2.3.4 released
by Adrian Schröter 17 Feb '15

17 Feb '15

Open Build Service(OBS) 2.3.4 just got released =============================================== This is a bugfix release in first place. But also the distribuition default target list has been updated. This release is most important for cross build support. Building against openSUSE 12.2 and Factory for ARM architecture works now out-of-the-box. OBS 2.3.4 is published in "openSUSE:Tools" project: http://download.opensuse.org/repositories/openSUSE:Tools/ Appliances can be used as usual: http://en.opensuse.org/openSUSE:Build_Service_Appliance Release Notes: ============== Feature backports: ================== * Added "Hostarch" in _buildinfo for osc local builds of cross builds Changes: ======== * package meta creation of package copy command is not copying relationships and devel definitions anymore. * Added openSUSE 12.2 to default target list * Removed openSUSE 11.4 from default target list (EOL soon) * Fedora 15 is EOL, removed from default list Bugfixes: ========= * backend: allow access to access protected project repositories when users are in both projects. * backend: increase vrev on package source copy * webui: fixed underscores in code listings * webui: Do not expose user email address in anonymous mode * obsworker: do not fail when no /etc/sysconfig/proxy exists * build: fixed cross architecture initilisation for chroot builds -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- 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] ubuntu build hangs in dh_installdocs
by Andreas Baumann 14 Oct '13

14 Oct '13

Hi, I installed a local OBS-Server 2.4 (as appliance image). Added a project, added a repository with Ubuntu 13.04. Running a build on the one local worker. I'm building a boost 1.49 package.. The build starts and then hangs forever in: /usr/bin/perl -w /usr/bin/dh_installdocs --all debian/README.Debian debian/NEWS.Debian 0 S 399 759 753 0 98 18 - 5968 wait 14:59 ? 00:00:00 /usr/bin/perl -w /usr/bin/dh_installdocs --all debian/README.Debian debian/NEWS.Debian stracing PID 399, I get: wait4(762, This process with PID 762 is a: chown -R 0:0 debian/libboost1.49-doc/usr/share/doc the strace of it shows it waits in: read(3, An lsof of it shows: chown 762 399 3u IPv4 516089 0t0 TCP localhost:39812->localhost:55332 (ESTABLISHED) So the read hangs getting an answer from the 'faked': tcp 0 0 0.0.0.0:55332 0.0.0.0:* LISTEN 813/faked-tcp I just wondered, if somebody else has experienced this problem before. I saw a rather old message of somebody who might have had the same problem: http://lists.opensuse.org/opensuse-buildservice/2008-11/msg00231.html Greetings Andreas -- Andreas Baumann Trottenstrasse 20 CH-8037 Zuerich Telefon: +41(0)76/373 01 29 E-mail: abaumann(a)yahoo.com Homepage: www.andreasbaumann.cc -- 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] network: nothing provides libsasl2.so.2()
by Dmitriy Perlow 27 Sep '13

27 Sep '13

Hello. Could anybody fix this unresolvability please? https://build.opensuse.org/project/monitor/network?arch_x86_64=1&defaults=0… -- Best regards, Dmitriy DA(P).DarkneSS Perlow @ Linux x64 -- 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] GSoC 2013 Project Wrap up
by Shayon Mukherjee 27 Sep '13

27 Sep '13

Hello Folks, GSoC 2013 is finally coming to end. That being said, I had a great time working on Building a discussion system for the Open Build Service. I have learnt a lot in the past ~3 months and thankful to the people who guided and mentored me. Here are two posts I wrote on my work and lessons learnt: 1. Technical details: http://blog.wrkb.in/post/62022570851/part-1-of-3-technical-details-of-the-g… 2. Lessons learnt: http://blog.wrkb.in/post/62329077937/part-2-of-3-lessons-learned-from-my-gs… 3. GSoC Experience: To come later (once gsoc ends). I hope people enjoyed the work we did as part of the GSoC project. Bye for now. Have a great year ahead. Cheers! -- Shayon http://wrkb.in IRC nick: shayonj -- 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] signing key updates?
by Tim Serong 27 Sep '13

27 Sep '13

Hi All, Unless I'm confused (which I'm never willing to rule out as a possibility), the GPG signing key for the network project on OBS was updated recently. I discovered this while trying to install network:ha-clustering:Stable/cluster-glue on an FC19 VM. The install failed with: ... Downloading packages: warning: /var/cache/yum/x86_64/19/network_ha-clustering_Stable/packages/cluster-glue-1.0.11-3.1.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 7b709911: NOKEY Retrieving key from http://download.opensuse.org/repositories/network:/ha-clustering:/Stable/Fe… The GPG keys listed for the "Stable High Availability/Clustering packages (Fedora_19)" repository are already installed but they are not correct for this package. Check that the correct key URLs are configured for this repository. Failing package is: cluster-glue-1.0.11-3.1.x86_64 GPG Keys are configured as: http://download.opensuse.org/repositories/network:/ha-clustering:/Stable/Fe… So I triggered a rebuild of that package, and was then able to install it with no problems, but this raises the question: if a signing key for a project is updated, do we need something to automatically re-sign all packages in that project? Seems a bit sucky to have to manually trigger a rebuild... Thanks, Tim -- Tim Serong Senior Clustering Engineer SUSE tserong(a)suse.com -- 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] E-MARKETING
by ETG Ventas 26 Sep '13

26 Sep '13

E-MARKETING ( http://artechsv.com/index.php/servicios/e-marketing ) si ya no desea recibir nuestras promociones, puede seguir este link. Gracias ( http://174.142.32.116/~artechsv/index.php?subid=243871&option=com_acymailin… )

1 0

[opensuse-buildservice] Backend storage questions
by Daniel Drake 25 Sep '13

25 Sep '13

Hi, I am running an OBS private instance. Thanks for the great platform. I am curious about how OBS deals with sources storage on the backend. We will be linking git commits in a busy repository to automated package builds in OBS. Each git commit will therefore result in a new tarball being generated, and a new revision in OBS's revision control for that package. This will mean a lot of commits and a lot of tarballs. How will OBS deal with that, will we have disk space consumption issues in future? Looking on the backend, I see roughly how file storage works. At /srv/obs/sources/<pkg> I see that each file from each revision in the history is stored independently and wholly (no binary diffs at play, for example). Over time, it looks like this will use up enough disk space to cause us some problems. Will OBS ever purge files from ancient revisions? If I purge such files manually, will anything break beyond the ability to back through history to that particular revision? How do large instances e.g. openSUSE deal with this? Now looking at storage of resultant built binaries, it appears that OBS only keeps the most recently built version. Is this correct, and can this be tweaked? Thanks, Daniel -- 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] new OBS ups and downs
by Hans-Peter Jansen 25 Sep '13

25 Sep '13

Hi, the new expanded setup increased the "felt speed" significantly. Great work, Adrian, Michael, and Co. OTOH, I noticed some strange behavior, too. Please have a look at https://build.opensuse.org/package/show/home:frispete:python/python-ZODB3 Many builds are flagged failed, although they built perfectly, e.g.: [ 40s] RPMLINT report: [ 40s] =============== [ 42s] python-ZODB3.noarch: W: no-dependency-on python(abi) 2.7 [ 42s] 2 packages and 0 specfiles checked; 0 errors, 1 warnings. [ 42s] [ 42s] ... creating baselibs [ 42s] ... comparing built packages with the former built [ 42s] /usr/lib/build/rpm-check.sh [ 42s] compare /.build.oldpackages/python-ZODB3-3.11.0a3-2.1.src.rpm /home/abuild/rpmbuild/SRPMS/python-ZODB3-3.11.0a3-2.2.src.rpm [ 42s] compare /.build.oldpackages/python-ZODB3-3.11.0a3-2.1.noarch.rpm /home/abuild/rpmbuild/RPMS/noarch/python-ZODB3-3.11.0a3-2.2.noarch.rpm [ 42s] comparing /.build.oldpackages/rpmlint.log and /home/abuild/rpmbuild/OTHER/rpmlint.log [ 42s] compare validated built as identical ! [ 42s] ... saving built statistics [ 42s] ... saving built packages [ 42s] /home/abuild/rpmbuild/RPMS/noarch/python- ZODB3-3.11.0a3-2.2.noarch.rpm [ 43s] /home/abuild/rpmbuild/SRPMS/python-ZODB3-3.11.0a3-2.2.src.rpm [ 43s] /home/abuild/rpmbuild/OTHER/_statistics [ 43s] /home/abuild/rpmbuild/OTHER/rpmlint.log [ 43s] [ 43s] cloud119 finished "build python-ZODB3.spec" at Tue Sep 10 08:30:51 UTC 2013. [ 43s] [ 48s] [ 27.640676] SysRq : Power Off [ 48s] [ 27.796563] Power down. [ 48s] build: extracting built packages... [ 48s] python-ZODB3-3.11.0a3-2.2.noarch.rpm [ 48s] python-ZODB3-3.11.0a3-2.2.src.rpm [ 48s] _statistics [ 48s] rpmlint.log Of course, I tried a rebuild -f already. Any idea anybody? TIA, Pete -- 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] Error on osc commit when .spec uses <CI_CNT>.<B_CNT>
by Kristoffer Grönlund 24 Sep '13

24 Sep '13

Hi, I have a problem using osc with the OBS, and I haven't managed to figure out what is going on. I'm trying to commit an update to this package: https://build.opensuse.org/package/show/network:ha-clustering:Factory/crmsh I've branched it to my home project, made the change, updated the changelog and I then run osc commit. However, the source_validator script fails on the Release: line of the .spec file. If I run osc commit --noservice, it will commit and build successfully on the OBS itself. I haven't found any reference to anyone else having this issue, so is it something that is broken on my system? $ osc diff Index: crmsh.spec =================================================================== --- crmsh.spec (revision 1b18e4817954ed02363dca88657e8621) +++ crmsh.spec (working copy) @@ -56,6 +56,7 @@ Requires: python-dateutil Requires: python-lxml BuildRequires: python-lxml +BuildRequires: fdupes %if 0%{?suse_version} # Suse splits this off into a separate package @@ -133,6 +134,7 @@ %endif make %{_smp_mflags} docdir=%{crmsh_docdir} +%fdupes -s %{buildroot} %install rm -rf %{buildroot} $ osc vc $ osc commit Log template was not changed a)bort, c)ontinue, e)dit: c error: line 33: Illegal char '<' in: Release: 0.rc3.<CI_CNT>.<B_CNT> Aborting: service call failed: /usr/lib/obs/service/source_validator --outdir /tmp/tmp8PAm2G *** Error: -- // Kristoffer Grönlund // kgronlund(a)suse.com -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1