openSUSE Build Service November 2012

buildservice@lists.opensuse.org

57 participants
58 discussions

Re: [opensuse-buildservice] Stalled submit requests

by Matwey V. Kornilov

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 years, 7 months

[opensuse-buildservice] Open Build Service(OBS) 2.3.4 released

by Adrian Schröter

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

7 years, 7 months

[opensuse-buildservice] Expired OBS Keys?

by King Thorin

It seems the OBS Security key (keyid 79EAFD54) on keys.gnupg.net has expired (2011-Apr-2). Would it be possible for someone to update it? I know an updated key has been generated (which expires 2013) as it can be found here: http://download.opensuse.org/repositories/security:/OpenVAS:/STABLE:/v4/xUb… Further details can be found via: http://lists.wald.intevation.org/pipermail/openvas-distro/2011-April/thread… Basically the issue came to light when following instructions: http://www.openvas.org/install-packages.html#openvas4_ubuntu_obs -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

9 years, 2 months

[opensuse-buildservice] New project openSUSE:Current?

by Cristian Morales Vega

Sometimes you have appA in your repo building for both old and new openSUSE versions. appA depends on libA > X, but only the latest openSUSE version provides it. openSUSE <latest-1> came with libA <X-1>. The solution is to package libA > X for the old distributions and usually you do that linking to the devel project. I would like an openSUSE:Current project that would always contains the latest supported version of the packages. Right now the packages from openSUSE:12.1:Update, but once 12.2 is released it should be changed to openSUSE:12.2:Update. This way I could link to those packages instead of linking to the devel project. It would let me compile appA in old distros while giving to the users a libA package that is not soooooo unsupported (this would be officially unsupported anyway, but...). I would like this since it's a single place to change when a new openSUSE version is released (If needed I can do it). Looking at the openSUSE:12.1:Update project metadata I guess it would just need be something like <project name="openSUSE:Current"> <title>Current version of openSUSE</title> <description></description> <link project="openSUSE:12.1:Update"/> <debuginfo> <enable/> </debuginfo> </project> But I'm not sure since I never really saw a doc explaining the meaning of <link> in the *project metadata*, only in _link files. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

9 years, 6 months

[opensuse-buildservice] local packages do not override global packages

by Olaf Hering

The package ocaml-findlib in devel:languages:ocaml has a BuildRequires: "camlp4". In the same project ocaml-camlp4-devel (from package ocaml) provides "campl4". But this provides is not used, instead the package 'camlp4' from the main openSUSE_12.1 project is used: devel:languages:ocaml/ocaml-findlib $ obs r -v openSUSE_12.1 i586 unresolvable: nothing provides ocaml = 3.12.0-11.1.2 needed by camlp4 nothing provides ocaml(Arg) = 877340141c0babb58b3aaef2f5b70fc9 needed by camlp4 openSUSE_12.1 x86_64 unresolvable: nothing provides ocaml = 3.12.0-11.1.2 needed by camlp4 nothing provides ocaml(Arg) = 877340141c0babb58b3aaef2f5b70fc9 needed by camlp4 Is this a bug in the dependency solver? I reported it via bugzilla, but got no reply up to now: https://bugzilla.novell.com/show_bug.cgi?id=781120 Olaf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

9 years, 7 months

[opensuse-buildservice] [help] how to compile a kernel version in OBS?

by Jun Hu

Hi Guys: I'm use OpenSuse Linux os, now I need patch the kernel , I have known how to compile an application in OBS . how to compile a kernel version in OBS? -- -------------------------- Love suse, Love software! -------------------------- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

9 years, 8 months

[opensuse-buildservice] Increasing the throughput of Open Build Service (OBS) building packages in obs with fusion io pci-e drive card

by doiggl＠velocitynet.com.au

Hello, I see about 110 jobs on obs with a job time greater than 2 or more hours processing time.[1] on Open Build Service (OBS) Reason for asking. Improve the packaging times during busy times on (OBS). Some questions. - Has SSD fusion io pci-e drive card ever been tried on obs - Would a SSD fusion io pci-e drive help shrink down the processing time on all obs jobs, therefore improving obs job turnaround times. - I know it costs for a card [Depends what capacity/model] - I saw some pci-e drive Manufacturer refurbished cards on ebay[2] Cheers Glenn Demo at [3] [1] https://build.opensuse.org/monitor/old [2] http://www.ebay.com/sch/Computers-Tablets-Networking-/58058/i.html?LH_BIN=1… [3] Demo http://www.youtube.com/watch?v=9J5xGwdmsuo -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

9 years, 9 months

[opensuse-buildservice] syslog-ng in buildservice

by Peter Czanik

Hello, This is something driving me crazy: as far as I can see, Marius and I have the completely same setup for syslog-ng compilation. I can't spot any other differences than that he also has rsyslog and dependencies there. Still, syslog-ng post install script for openSUSE 12.2 and preinstall for 12.1 fail in my home and do not fail in his. Mt's syslog home: https://build.opensuse.org/project/show?project=home%3Amtomaschewski%3Asysl… czanik's syslog-ng home: https://build.opensuse.org/package/show?package=syslog-ng&project=home%3Acz… Could someone with more trained eyes check what causes this difference? Thanks, bye, CzP -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

9 years, 9 months

[opensuse-buildservice] hermes no working?

by Ruediger Meier

Hi, Since a few days (or weeks?) I don't get any messages anymore from hermes, nothing about submit requests and no Build Failure messages. Is this a known problem? cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

9 years, 9 months

[opensuse-buildservice] how does osc handle long-lived branches?

by Adam Spiers

Example scenario: - configure 'submitrequest_on_accept_action = update' in ~/.oscrc (BTW I can't find documentation for this option anywhere except for comments in the config file template. Once you delete them, the only way of retrieving them is to read the source :-/ ) - osc bco $prj $pkg - hack on home:$me:$prj/$pkg, test, hack, test etc. - commit to home:$me:$prj/$pkg - submitrequest to $prj/$pkg - submitrequest gets accepted - wait a couple of months for $prj/$pkg to get updated by other people At this point, I have numerous questions: 1. What is the state of home:$me:$prj/$pkg server-side? 2. Does it automatically contain all the latest changes from the upstream $prj/$pkg? i.e. if I do 'osc up' on my working copy, will I get them? 3. If so, why? - how does this work? 4. If not, presumably there is some equivalent of 'osc pull' which applies to branches rather than linkpac'd packages? 5. How would I cherry-pick some but not all of the upstream changes into my branch? 6. Is any of this workflow documented anywhere? http://en.opensuse.org/openSUSE:Build_Service_Collaboration would be the obvious place for it, but it's not there yet. So, trying to reverse-engineer this, I see that my working copy of home:aspiers:branches:openSUSE:Tools/obs-service-tar_scm contains the following line in .osc/_files: <linkinfo baserev="663c096f8c0695af0960d98d6ed7b435" lsrcmd5="b01017819c52ddd0eabd72fd7d5d3c64" package="obs-service-tar_scm" project="openSUSE:Tools" srcmd5="ffd170170ba0a40a0db1015702ccdee5" /> and also 'osc log' shows: ---------------------------------------------------------------------------- r9 | buildservice-autocommit | 2012-07-27 13:35:33 | b01017819c52ddd0eabd72fd7d5d3c64 | unknown | rq129093 baserev update by copy to link target Looking in my working copy of openSUSE:Tools/obs-service-tar_scm, I see that .osc/_files contains: <directory name="obs-service-tar_scm" rev="ffd170170ba0a40a0db1015702ccdee5" srcmd5="ffd170170ba0a40a0db1015702ccdee5"> So 'lsrcmd5' in the branch points to the baserev update autocommit, and 'srcmd5' points to the directory revision of the upstream project. But I'm still not really any wiser - what does baserev point to, how is it used? Thanks! Adam -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

9 years, 10 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service November 2012