January 2012 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Dependency resolution prefers package names rather than "provides"?
by Cristian Morales Vega 16 Jan '12

16 Jan '12

With the OBS down I can't give any example now. But if there is packageA-devel in openSUSE:12.1 and in the devel project it is renamed to stillpackageA-devel, the other packages in that devel project that require "packageA-devel" seem to prefer packageA-devel to stillpackageA-devel. stillpackageA-devel provides "packageA-devel = <new_version>" and obsoletes "packageA-devel < <new_version>". Is this expected? Usually what happens is that the devel project requires the exact version of "packageA" and the OBS gives an "unresolvable" state because it can't find "packageA = <old_version>", "packageA = <new_version>" hides it. -- 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] OBS down ?
by Christian 15 Jan '12

15 Jan '12

Hi, since yesterday eening OBS seem to be down. Anyone aware of this problem ? -- Christian ---------------------------------------------------- - Please do not 'CC' me on list mails. Just reply to the list :) ---------------------------------------------------- Der ultimative shop für Sportbekleidung und Zubehör http://www.sc24.de ---------------------------------------------------- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 16

Re: [opensuse-buildservice] Re: OBS down ?
by Bryen M Yunashko 15 Jan '12

15 Jan '12

On Sat, 2012-01-14 at 19:47 -0600, Archie Cobbs wrote: > > While some outages have been frustratingly low on information, I think > > this time we saw good spread of information and the bases were pretty > > well covered. However, let's at least be fair and give some benefit of > > the doubt by recognizing that in life there's always room for > > improvement. Where else do you feel it should have been posted? > > Hmmm... how about this: set up a blog page for OBS general news and info. Then we can all subscribe to the RSS feed in our google reader. > > -Archie 1. Please reply to list, I don't need to be CC'ed on a mailing list that we're already on. :-) 2. Isn't that already done? The information was posted on news.opensuse.org promptly and n.o.o is definitely "RSS-able." Bryen -- 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] libreoffice on onerirc takes an extremely long time to build
by Paul Elliott 13 Jan '12

13 Jan '12

Because it was not in BS, I attempted to build libreoffice for oneriric. It takes an extremely long time to build. The i586 version is still building. x86_64 version terminated with this error: > Job seems to be stuck here, killed. > qemu: terminating on signal 15 from pid 14358 > No buildstatus set, either the packager broke the base system > (glibc/bash/perl) or the build host has a kernel or hardware problem, OBS > server will retry... https://build.opensuse.org/package/live_build_log?arch=x86_64&package=libre… dependancies&repository=xUbuntu_11.10 https://build.opensuse.org/package/show?package=libre-office-java-common&pr… Did it stop because of a limit on total build time for a single source package? If so, that limit needs to be increased. Because it takes so long, I hesitate to trigger a rebuild without somekind of solution to this prpblem. Please suggest what I should do. Thank You. -- Paul Elliott 1(512)837-1096 pelliott(a)BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117

3 7

[opensuse-buildservice] are builds stopped or stuck on the build service ? , many are showing red
by doiggl＠velocitynet.com.au 13 Jan '12

13 Jan '12

Hello Some info - are builds stopped or stuck on the build service ? [1], many are showing red. [1] https://build.opensuse.org/monitor Cheers Glenn -- 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] special hack for handing off remote source requests to ajax server
by Robert Schiele 11 Jan '12

11 Jan '12

Hi, I identified a problem when accessing a remote OBS instance through a squid proxy. The change commit 5ed45e0096ff5051827c251c8fd384dd70debcbb Author: Michael Schroeder <mls(a)suse.de> Date: Wed May 26 11:26:55 2010 +0200 - handoff remote source requests to ajax server - make request data available diff --git a/src/backend/BSServer.pm b/src/backend/BSServer.pm index 154b965..afead0f 100644 --- a/src/backend/BSServer.pm +++ b/src/backend/BSServer.pm @@ -44,6 +44,7 @@ use BSHTTP; use strict; # FIXME: store in request and make request available +our $request; our $peer; our $peerport; our $slot; @@ -824,6 +825,7 @@ sub compile_dispatches { sub dispatch { my ($conf, $req) = @_; + $BSServer::request = $req; my $disps = $conf->{'dispatches'}; my $stdreply = $conf->{'stdreply'}; die("500 no dispatches configured\n") unless $disps; diff --git a/src/backend/bs_srcserver b/src/backend/bs_srcserver index 3364355..daf6662 100755 --- a/src/backend/bs_srcserver +++ b/src/backend/bs_srcserver @@ -2814,9 +2814,17 @@ sub getfile { die("404 $filename: no such file\n") unless $files->{$filename}; my @s = repstat($rev, $filename, $files->{$filename}); die("$projid/$packid/$files->{$filename}-$filename: $!\n") unless @s; - local *F; - repopen($rev, $filename, $files->{$filename}, \*F) || die("$projid/$packid/$files->{$filename}-$filename: $!\n"); - BSServer::reply_file(\*F); + if (!$BSStdServer::isajax && $rev->{'srcmd5'} && $rev->{'srcmd5'} ne 'upload' && $rev->{'srcmd5'} ne 'pattern' && $rev->{'srcmd5'} ne 'empty') { + # hack: we identify remote source downloads by looking at the user agent + my $useragent = $BSServer::request->{'headers'}->{'user-agent'} || ''; + if ($useragent =~ /BSRPC/) { + BSHandoff::handoff($ajaxsocket, "/source/$projid/$packid/$filename", undef, "rev=$rev->{'srcmd5'}"); + exit(0); + } + } + my $fd = gensym; + repopen($rev, $filename, $files->{$filename}, $fd) || die("$projid/$packid/$files->{$filename}-$filename: $!\n"); + BSWatcher::reply_file($fd); return undef; } @@ -4980,6 +4988,7 @@ my $dispatches_ajax = [ '/getbinaries $project $repository $arch binaries: nometa:bool? raw:bool?' => \&worker_getbinaries, '/lastevents $filter:* start:num? obsname:?' => \&worker_lastevents, '/source/$project/$package rev' => \&getfilelist_ajax, + '/source/$project/$package:package_pattern/$filename rev?' => \&getfile, ]; #################################################################### causes special handling if the user-agent string indicates that the other system is an OBS system as well, resulting in using chunked transfer encoding instead of having the content length. When this passes through the squid proxy the chunked transfer encoding is replaces by "normal" encoding but still the content-length not added. The receiving OBS cannot deal with that situation. Thus my question is, why was this special handling introduced and what would be the consequences if I disabled that? Is this just a performance downgrade or would that also have an impact on functionality. Robert -- 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] OBS Build Team meeting
by Adrian Schröter 10 Jan '12

10 Jan '12

present: mls, saschpe, adrian Open features until OBS 2.3 =========================== * Support issue tracking (mirror bug entries and owners) and assign it to packages. => Show open patchinfos to the packager based on bugzilla data. DONE, except update mechanism. AI: adrian * support osc search for published binaries with limiters: - version/release - base project AI: mls * webui patchinfo editor - add button: update _patchinfo file based on the mentioned (bugzilla and cve) issues from sources. AI: benjamin * enable publishing and useforbuild only for patchinfos on release project AI: adrian * maintenance request accept will create patchinfo on accept if none is provided. AI: adrian * enhance createrepo for delta downloads AI: sascha * Show required and existing fixes on incidents. required bug ids are defined in _patchinfo, existing are parsed from source diff. AI: sascha * Show incident status - build status - patchinfo bugnummer diffs: => take bug nummer => show package diff => link to bugzilla bug AI: sascha * A number of bugs have been opened by maintenance team to be verified/fixed. * Open question how to help the user to find sources in open incidents. (automatic devel package definition change in :Update project?) Implemented requests ==================== * Handle declined requests in UI (webui and osc): All requests (not just maintenance) will require a handling of submitter after getting the request declined (by reviewer or target). This is because declined request notifications can be easily overlooked, the current state should always be available. Therefore the declined request will stay visible for the creator until the submitter decides to: - revoke : Accepting the decline - superseed : Submitting an improvement - reopen : disagreement with the reason and ask back again. (DONE) * Support linking to not yet existing packages for release number handling * set bugowner on incident creation (DONE) * export severity to updateinfo.xml (DONE) * faster product build thanks to enhanced obs-worker (DONE) * Resign packages on release. Incident projects must never contain final signed packages, since they are not complete reviewed yet. (DONE) * Support aggregate of updateinfo.xml (DONE) * Cached issue parsing from source diffs in backend (DONE) * switch to security patchinfo category when found CVE (DONE) * Solution for bugzgilla groups (eg. kde-maintainers). Who should see open issues in bugzilla because of this ? DONE. bugzilla groups are created as users in OBS. -- 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

1 0

[opensuse-buildservice] Job seems to be stuck here, killed.No buildstatus set, either the packager broke the base system (glibc/bash/perl) or the build host has a kernel or hardware problem
by doiggl＠velocitynet.com.au 10 Jan '12

10 Jan '12

Hello Saw a odd message in a build job [1] odd , something broken ? Glenn [1] Source: https://build.opensuse.org/package/live_build_log?arch=x86_64&package=libre… Job seems to be stuck here, killed. qemu: terminating on signal 15 from pid 14358 No buildstatus set, either the packager broke the base system (glibc/bash/perl) or the build host has a kernel or hardware problem, OBS server will retry... -- 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] "dead lock" between autoyast2 and yast2-schema
by Joop Boonen 09 Jan '12

09 Jan '12

All, Currently there is a "dead lock" between package autoyast2 and yast2-schema (for the openSUSE:Factory:ARM build). The thing is that autoyast2 Requires yast2-schema. Because of this yast2-schema is blocked. I got around this by removing the autoyast2 requirement. Until yast2-schema has been build. When this package was build I added the Requirement again. I wonder if there is a better "mechanism" in OBS that solves such "lock issue" automatically? Otherwise someone has to handle this by hand. Regards, Joop. -- 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] about latest openssl update for SLE_11_SP1
by Christian 09 Jan '12

09 Jan '12

Hi, latest updates for SLE_11 SP1 brought 0.9.8j --snip-- v | SDK-SP1_upd | libopenssl-devel | 0.9.8h-30.42.1 | 0.9.8j-0.24.1 | x86_64 v | SP1_upd | libopenssl0_9_8 | 0.9.8h-30.42.1 | 0.9.8j-0.24.1 | x86_64 v | SP1_upd | libopenssl0_9_8-32bit | 0.9.8h-30.42.1 | 0.9.8j-0.24.1 | x86_64 v | SP1_upd | nscd | 2.11.1-0.32.1 | 2.11.1-0.34.1 | x86_64 v | SP1_upd | openssl | 0.9.8h-30.42.1 | 0.9.8j-0.24.1 | x86_64 --snip-- shouldn't a SLES be "binary compatible" ? building proftpd and starting will show following: proftpd[4078]: mod_tls/2.4.3: compiled using OpenSSL version 'OpenSSL 0.9.8h 28 May 2008' headers, but linked to OpenSSL version 'OpenSSL 0.9.8j-fips 07 Jan 2009' library so should we have the new openssl in "SUSE:SLE-11 <https://build.opensuse.org/project/show?project=SUSE%3ASLE-11>:Update <https://build.opensuse.org/project/show?project=SUSE%3ASLE-11%3AUpdate>" ? -- Christian ---------------------------------------------------- - Please do not 'CC' me on list mails. Just reply to the list :) ---------------------------------------------------- Der ultimative shop für Sportbekleidung und Zubehör http://www.sc24.de ---------------------------------------------------- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1