April 2010 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] local obs using remote obs repo
by Robert Xu 06 Apr '10

06 Apr '10

hello all, is it possible, on a local obs, to provide your own project configs for the openSUSE.org repo? i.e. Letting openSUSE.org:Fedora:12 be a link to opensuse's OBS Fedora:12 but having custom project configs for openSUSE.org:Fedora:12 on the local obs. -- Cya Later, Robert Xu Ever tried Linux? :) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3

[opensuse-buildservice] Upcomming OBS 1.8 release (aka MeeGo release)
by Adrian Schröter 06 Apr '10

06 Apr '10

Hello, you might have already noticed the created 1.8 branch in git. The reason behind this "sudden" planned 1.8 release before 2.0 in summer is a request by the MeeGo group. The MeeGo group (LinuxFoundation, Intel and Nokia) are about to use their own instances of OBS for creating their releases. They want also to extend OBS with new features, current most needed feature is the group handling and read permission control. Since they have a tight timeline, we agreed to roll a 1.8 release end of next month based on their contributions. This is reflected in the roadmap here: http://wiki.opensuse.org/openSUSE:Build_Service_Roadmap#Upcoming_Releases The backend code part from master may also get backported entirely to 1.8, but api and webui stay based on 1.7 branch plus some hand picked backports. It is great to see more parties using and contributing to OBS. You are highly welcome ! Please speak up if someone wants to add a certain feature to the 1.8 release, but from the SUSE side we want to concentrate on our 2.0 release and make the other features in "master" branch complete and solid. So we want to avoid to backport too much to the 1.8 release. bye adrian -- 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

2 2

[opensuse-buildservice] openSUSE:Tools:Devel is about to get removed.
by Adrian Schröter 06 Apr '10

06 Apr '10

Hi, if no one protests, I will remove the openSUSE:Tools:Devel project tomorrow. We will still have: openSUSE:Tools -- the official stable releases. openSUSE:Tools:Unstable -- "official" unstable releases (obs-server from today git) openSUSE:Tools:MeeGo -- the upcomming 1.8 release bye adrian -- 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] delete broken _link
by doiggl＠velocitynet.com.au 06 Apr '10

06 Apr '10

Hello, Could someone delete this _link file please as its broken. The message I get is: openSUSE Webclient Error: Error Details: Errorcode: unknown Message: Parsing XML failed from: http://api-internal.opensuse.org:80/source/home:doiggl/wflogs/_link What is the correct way to create a link to another package. Thanks Glenn -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 8

[opensuse-buildservice] 'finished' status seems to be stalled
by Matwey V. Kornilov 06 Apr '10

06 Apr '10

Hi, I am running my local obs 1.7.2. All of my current builds are 'finished' now but not published. I can't detect the origin of the problem. Is there a way to force republish of finished builds? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3

[opensuse-buildservice] new version of the dod patch
by Marcus Hüwe 06 Apr '10

06 Apr '10

Hi, here's a new version of the dod patch. Changes: - bs_repserver: * hand-off all fetching requests to the ajaxsocket: this means only one request for the same project/repo/arch is served and all other subsequent requests for the same project/repo/arch are "blocked" until the first request finished. This way we can avoid that the same package is fetched multiple times. The drawback of this approach is that the worst-case running time is O(n^2) (where n := number of packages to be fetched) but this can be ignored because it is usually a one-time job IMHO. * notify scheduler if a package was fetched - bs_sched: * removed old code to support updates of the metafile (now the repserver has to notify the scheduler if it fetched a package). For instance if a more frequently changing repo (e.g. an update repo) is used as a dod repo the scheduler has to detect "meta changes" and trigger rebuilds (which was not possible with the old code). Feedback, objections etc. are welcome:) Btw. I've a general question about the ajaxsocket. For instance if the srcserver does a RPC to the repserver and the repserver hands-off this request to its ajaxsocket, should the srcserver hand-off the request to its ajaxsocket too (before it does the RPC)? If I understand it correctly all requests which can't be served "immediately" are handed-off to the ajaxsocket because otherwise they may "block" other requests which can be served immediately (if the "maxchild" limit is reached). If this is correct why do we handoff requests like "/build/<projid>/<repoid>/<arch>/_repository?view=solvstate"? Can you enlighten me?:) Marcus

2 1

[opensuse-buildservice] [PATCH] Add support for patterns to yum-based distros
by iarnell＠gmail.com 06 Apr '10

06 Apr '10

From: Iain Arnell <iarnell(a)epo.org> This patch adds support for patterns to standard yum-based distros such as Fedora, Red Hat, and CentOS. Once applied, setting Patterntype to 'comps' in prjconf will enable generation of groups.xml file and allow users of these distros to "yum groupinstall <patternname>". --- src/backend/BSXML.pm | 23 +++++++++++++++++ src/backend/bs_publish | 63 ++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 86 insertions(+), 0 deletions(-) diff --git a/src/backend/BSXML.pm b/src/backend/BSXML.pm index 8630f29..7e745ab 100644 --- a/src/backend/BSXML.pm +++ b/src/backend/BSXML.pm @@ -988,5 +988,28 @@ our $person = [ ], ]; +our $comps = [ + 'comps' => + [], + [[ 'group' => + [], + 'id', + [[ 'description' => + 'xml:lang', + '_content', + ]], + [[ 'name' => + 'xml:lang', + '_content', + ]], + [ 'packagelist' => + [[ 'packagereq' => + 'type', + [], + '_content', + ]], + ], + ]], +]; 1; diff --git a/src/backend/bs_publish b/src/backend/bs_publish index 15f8bf1..fbd5fb3 100755 --- a/src/backend/bs_publish +++ b/src/backend/bs_publish @@ -525,6 +525,64 @@ sub deletepatterns_rpmmd { } } +sub createpatterns_comps { + my ($extrep, $projid, $repoid, $signargs, $pubkey, $repoinfo, $patterns) = @_; + + deletepatterns_comps($extrep); + return unless @{$patterns || []}; + + # create comps data structure + my @grps; + for my $pattern (@$patterns) { + my $pat = XMLin($BSXML::pattern, $pattern->{'data'}); + (my $name = $pattern->{name}) =~ s/\.xml$//; + my $grp = { + id => $name, + }; + for ( @{$pat->{summary}} ) { + my $el = { '_content' => $_->{_content} }; + $el->{'xml:lang'} = $_->{lang} if $_->{lang}; + push @{$grp->{name}}, $el; + } + for ( @{$pat->{description}} ) { + my $el = { '_content' => $_->{_content} }; + $el->{'xml:lang'} = $_->{lang} if $_->{lang}; + push @{$grp->{description}}, $el; + } + for ( @{ $pat->{'rpm:requires'}->{'rpm:entry'} } ) { + push @{ $grp->{packagelist}->{packagereq} }, { _content => $_->{name}, type => 'mandatory' }; + } + for ( @{ $pat->{'rpm:recommends'}->{'rpm:entry'} } ) { + push @{ $grp->{packagelist}->{packagereq} }, { _content => $_->{name}, type => 'default' }; + } + for ( @{ $pat->{'rpm:suggests'}->{'rpm:entry'} } ) { + push @{ $grp->{packagelist}->{packagereq} }, { _content => $_->{name}, type => 'optional' }; + } + push @grps, $grp; + } + print " adding comps to repodata\n"; + my $comps = {'group' => \@grps}; + writexml("$extrep/repodata/group.xml", undef, $comps, $BSXML::comps); + qsystem('modifyrepo', "$extrep/repodata/group.xml", "$extrep/repodata") && print(" modifyrepo failed: $?\n"); + unlink("$extrep/repodata/group.xml"); + + # re-sign changed repomd.xml file + if ($BSConfig::sign && -e "$extrep/repodata/repomd.xml") { + my @signargs; + push @signargs, '--project', $projid if $BSConfig::sign_project; + push @signargs, @$signargs; + qsystem($BSConfig::sign, @signargs, '-d', "$extrep/repodata/repomd.xml") && print(" sign failed: $?\n"); + } +} + +sub deletepatterns_comps { + my ($extrep) = @_; + for my $pat (ls("$extrep/repodata")) { + next unless $pat =~ /^group/; + unlink("$extrep/repodata/$pat"); + } +} + sub createpatterns_ymp { my ($extrep, $projid, $repoid, $signargs, $pubkey, $repoinfo, $patterns) = @_; @@ -1086,6 +1144,11 @@ sub publish { } else { deletepatterns_rpmmd($extrep, $projid, $repoid, $signargs, $pubkey); } + if ($patterntype{'comps'}) { + createpatterns_comps($extrep, $projid, $repoid, $signargs, $pubkey, $repoinfo, $patterns); + } else { + deletepatterns_comps($extrep, $projid, $repoid, $signargs, $pubkey); + } publishprog_done: unlink("$uploaddir/publisher.$$") if $signkey; -- 1.6.6.1 -- 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 Status unavailable"
by Abel Alfonso Firvida Donestevez 03 Apr '10

03 Apr '10

Hello: After two days trying I have installed the OBS Appliance on a local server, and I got it working perfectly but it doesn't build packages. I always get the "Build Status unavailable" message. I check into the appliance and there is no gcc or any other compiler. My question is: Do I have to install anything else? If so, where I can find it ? sorry for my english. Thanks a lot -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 5

[opensuse-buildservice] obs signer
by Robert Xu 03 Apr '10

03 Apr '10

Hi all, How can I configure the obs signer? I haven't been able to find any guides on this... And, when I try to do it myself something goes wrong... -- Cya Later, Robert Xu Ever tried Linux? :) -- 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] %prefix variable not being substituted
by Matt Williams 02 Apr '10

02 Apr '10

I'm trying to update OGRE in the games project (https://build.opensuse.org/package/show?package=ogre&project=games) to the latest version but in the process of updating the .spec file for some reason the %prefix variable isn't being substituted. I call (in %prep but maybe it should be in %build) CMake with something like: cmake .. -DCMAKE_INSTALL_PREFIX=%prefix which I would expect to get turned in to: cmake .. -DCMAKE_INSTALL_PREFIX=/usr but it doesn't as can be seen at https://build.opensuse.org/package/rawlog?arch=x86_64&package=ogre&project=… (search for "CMAKE_INSTALL_PREFIX"). Now, I assume this is caused by something I'm doing wrong but I can;t work out what it is. Can anyone be of any help? Regards, Matt Williams http://milliams.com -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 1