November 2009 - openSUSE Build Service

[opensuse-buildservice] Signer hardware failure lead to unsigned repos
by Michael Schroeder 24 Nov '09

24 Nov '09

Hi Builders, there seems to be some curse on the buildservice hardware: one disk of the sign server broke down this evening. Because of this some unsigned repositories got published (this is of course a bug that needs to be fixed, publishing should de delayed instead). We're now running in degraded raid mode, signing works again. Sorry for the inconvenience, Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] Re: Build logs on build.o.o/stage
by Stephan Kulow 24 Nov '09

24 Nov '09

Am Dienstag 24 November 2009 schrieb Dominique Leuenberger: > Hi everybody, especially coolo, as I think you're most hacking on > b.o.o/stage. > > I was just wondering regarding the build logs: when I check a log, like for > example > https://build.opensuse.org/stage/package/live_build_log?arch=i586&package= > me-tv&project=home%3Adimstar&repository=openSUSE_Factory > > this loads blazing fast (good), but does not show me the entire log. > Whereas I perfectly agree that on a build failure, this is normally what I > need in order to see what is wrong, it can also remove some information > which I would need to see. > > A real-life example: evince was built for a while (in devel project) > without PDF support. The configure check for it failed. Nevertheless, the > build succeeded perfectly (file list was ok and all that). Skimming > through the output of %configure showed what was wrong. > > What I'm missing now in the current build log viewer is a way to show me > the entire log. I think defaulting to the last 1000 lines (or whatever it > is now) is great, but the option for all the log is missing (another > option than removing /stage from the url I mean :) ) > > What do you think? completely non-sense? Or did I just miss the obvious > (yes, osc is obvious, but not the one I'm looking for). > Hi, Check the page, it has a "Download raw log" link. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] Build logs on build.o.o/stage
by Dominique Leuenberger 24 Nov '09

24 Nov '09

Hi everybody, especially coolo, as I think you're most hacking on b.o.o/stage. I was just wondering regarding the build logs: when I check a log, like for example https://build.opensuse.org/stage/package/live_build_log?arch=i586&package=m… this loads blazing fast (good), but does not show me the entire log. Whereas I perfectly agree that on a build failure, this is normally what I need in order to see what is wrong, it can also remove some information which I would need to see. A real-life example: evince was built for a while (in devel project) without PDF support. The configure check for it failed. Nevertheless, the build succeeded perfectly (file list was ok and all that). Skimming through the output of %configure showed what was wrong. What I'm missing now in the current build log viewer is a way to show me the entire log. I think defaulting to the last 1000 lines (or whatever it is now) is great, but the option for all the log is missing (another option than removing /stage from the url I mean :) ) What do you think? completely non-sense? Or did I just miss the obvious (yes, osc is obvious, but not the one I'm looking for). Dominique -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] mingw builds
by Roger Oberholtzer 24 Nov '09

24 Nov '09

I would like to build a few things for mingw targets. I have added one to a project, and a build happens. However, it looks like the library that was built is a Linux ELF. Not a DLL. So, I am guessing there is more than just selecting MinGW as a target in the OBS. I tried to find a sample spec file from any of the the mingw32-* RPMs that are on the OBS. But I guess I do not know where to find one. I thought of installing a source RPM for one of the mingw32-* packages, as those usually contain the spec file, but I don't see any. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] Build Team Meeting
by Adrian Schröter 24 Nov '09

24 Nov '09

Present: freitag, cwh, mls, adrian, coolo Topics: * Status round * libxml for api and webclient ? * 1.7 release * svn move to gitorious and berlios Status round: ============= freitag: * Working on http status delivery for hermes module. cwh: * Installed own OBS instance for working on driver build support in kiwi. coolo: * coolo branch is git now to make merging easy. * moved server_status / monitor page to trunk. * Worked on speedup of active xml, trying to switch from REXML to libxml. Speedup of factor 10, but currently too many places which depend on REXML. * analyzing frontend logs to speed up. * Introduced project status as generic base for factory status page. => Collecting source or verify md5, devel package status and further items. These get cached to be able to generate the status page fast. bg: * build03 XEN debugging, first Intel based worker in our farm mls: * Improved build log handling, coolo has implemented a "X last lines only" web client for the web ui * worked on scheduler support for clean product build support. * indexed openSUSE:11.2* projects for software.opensuse.org/search adrian: * Added Fedora 12 support together with mls. * Added project wide submit request support in osc. * Added request review mechanism. => complete, except for "superseded" funcationality in client. * Added patchinfo support to api and osc. => missing final implementation to create the ID. 1.7 release: ============ To be done until 1.7 beta 1, target release date is within december: * make new snapshot and fix new dependencies (esp. new ruby/rails modules) (done) * what dependson support in api and osc * make repository status visible * Final patchinfo support * Attribute definition shall not be stored in project meta data anymore. * DoD feature working again. XML changes in api and webclient ================================ REXML and activexml are not fast enough for real web browsing experience. SmartXML is only used on software.o.o atm. Coolo introduced a new rubyxml using libxml. API has no performance problem with activexml, but webclient has. A conversation from activexml to libxml is possible step by step. activesupport has now libxml also, problem is that we might have problems to get our REST interface working with it. Call for testing of https://build.opensuse.org/stage/ , to check if activexml with libxml backend is working in all cases. So we can maybe switch for 1.7 release. svn move ======== The current plan is: copy svn from forge to berlios project and remove OBS parts afterwards there. OBS parts will be imported to own "openSUSE Build Service" module on gitorious: software webclient -> rename webui frontend -> rename to api backend sign hermes osc build yabsc ? We should do this step by step for each module. All modules will become an own repository. Everbody should create an gitorious account. coolo will take care about import. adrian will create a temporary solution for push mails. AI: adrian&coolo write an anouncemout to all developers and anounce the point of time when the new repositories will be used as default. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] Howto submitting an older revision to the build?
by Karl Eichwalder 24 Nov '09

24 Nov '09

I want to modify a previous revision and then submit this modified revision to the build. How can I do this? I think I should add a changes entry to r23 of home:keichwa:branches:openSUSE:Factory/opensuse-manuals_en and then submit it to 11.2 resp. 11.2:Update. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 12

[opensuse-buildservice] Fedora 12 is deployed
by Adrian Schröter 23 Nov '09

23 Nov '09

Hi, JFYI, Fedora 12 now imported and working. (There was no time to debug why Ubuntu:9.10 is not building up yet, if someone tells me the fix it is deployed immediatly ;). -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 7

[opensuse-buildservice] search broken on webclient - EOM
by Christian 23 Nov '09

23 Nov '09

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] trigger rebuild of linked package sitting in failed state ignored
by Hans-Peter Jansen 23 Nov '09

23 Nov '09

Hi, I have two branch projects home:frispete:branches:KDE:Qt and home:frispete:branches:KDE:KDE4:Factory:Desktop, where the latter links in some packages from the former, which itself links the packages from KDE:Qt. Today, the sip and PyQt4 updates arrived. I had to fix a conflict in ~frispete:branches:KDE:Qt/python-sip, and that build fine meanwhile, no matter, what I do, the python-sip packages of ~frispete:branches:KDE:KDE4:Factory:Desktop stay in broken state: "could not apply patch 'project.diff'", while this packages consists from a single _link, but no project.diff at all?! I tried: osc rebuild -f home:frispete:branches:KDE:KDE4:Factory:Desktop osc rebuild home:frispete:branches:KDE:KDE4:Factory:Desktop various web client options to rebuild the packages, but all attempts are ignored. Is there a way to solve this problem myself? Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 1

[opensuse-buildservice] Performance improvements
by Stephan Kulow 22 Nov '09

22 Nov '09

Hi, Having been frustrated by the slowness of activexml, I decided to give it a real xml parser and I think the arguments for it are pretty good. The port is just a couple of hours old, but it's speed is impressive. Check out /package/show?package=acl&project=Base%3ASystem both on https://build.opensuse.org and .../stage If you don't trust your eyes - these are the benchmarks from the log file: 17103ms for build, 1009ms for stage - note that I had to disable caching for stage so it's quite a tad slower than it can be. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0