August 2010 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] [PATCH] osc-1.2.8 doesn't know about "signing" state
by Srinidhi B 08 Aug '10

08 Aug '10

Hi, When using osc-1.2.8 against 2.0.5 server, I got this: $ osc prjresults home:srinidhi osc: warn: unknown status 'signing'... please edit osc/core.py, and extend the buildstatus_symbols dictionary. So here is a small patch that adds "signing" state. I chose "S" just like that. Srinidhi. diff --git a/osc/core.py b/osc/core.py index df16258..ce5387e 100644 --- a/osc/core.py +++ b/osc/core.py @@ -185,6 +185,7 @@ buildstatus_symbols = {'succeeded': '.', 'scheduled': 's', 'excluded': 'x', 'dispatching': 'd', + 'signing': 'S', } -- 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] Error in osc; checkin doesn't run
by Sascha 'saigkill' Manns 06 Aug '10

06 Aug '10

Hello Mates, i've just updated my Spec from Skrooge [1]. But if i'm typing 'osc ci' i've got this message: error: Summary field must be present in package: (main package) ERROR: source_validator failed Has anyone seen this before? [1] http://susepaste.org/3530166 -- Sincerely yours Sascha Manns open-slx GmbH openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English)

2 4

[opensuse-buildservice] 'clicfs' not found / kiwi
by Javier Llorente 05 Aug '10

05 Aug '10

Hello listmates, I am trying to build a 11.2-based OEM image on the Build Service and I am getting the following error: 'clicfs' not found. https://build.opensuse.org/package/live_build_log?arch=x86_64&package=open- pc-image&project=spins%3Aopen-pc%3Aimages&repository=images How can I add it to my kiwi build environment? Another question: how can I build the OEM image against whatever version of kiwi is on Virtualization:Appliances? Thanks, -- Javier Llorente

2 6

[opensuse-buildservice] Safe way to remove /srv/obs/source folders
by Davis_Phillips＠Dell.com 05 Aug '10

05 Aug '10

Hello, I was wondering if there is considered a best practice for deleting the folders under /src/obs/source? The uploaded tarballs & spec files are being to consume a large amount of space on our front end servers. We would like to archive what we can in an effort to clean up the environment. Thanks in advance! Thanks! Davis Phillips Release Engineer Dell | PG Release Engineering office + 1 512 723 5910 -- 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] Question about Package Deletion
by Davis_Phillips＠Dell.com 05 Aug '10

05 Aug '10

Greetings everyone, I was hoping that someone would have a quick fix for an issue we are experiencing: There is a bad package in one of our projects: %{name} I can't delete the project or the package using osc or the front end. I temporarily removed the home page directories as a dependencies - this isn't preventing the project deletion. But: oscbdc rdelete --force OpenManage:640:HudsonBuilder_2 Server returned an error: HTTP Error 404: Not Found package '%{name}' does not exist in project 'OpenManage:640:HudsonBuilder_2' How do we get rid of this? I've already removed the %{name} files & folders in that repository on the frontend server: find /srv/obs/build/OpenManage:640:HudsonBuilder_2/ -name \*name\* | xargs sudo -u obsrun rm -rf And the :depends binary in the /srv/obs/builds repository holds this value. Is there a database table or something else we should look at first? Thanks! Davis Phillips Release Engineer Dell | PG Release Engineering office + 1 512 723 5910 -- 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] Bad interaction between sign-2.1.2/srcserver-2.0.5
by Jan Engelhardt 05 Aug '10

05 Aug '10

Hi, I followed http://wiki.opensuse.org/openSUSE:Build_Service_Signer and got sign/signd running so far. On trying to create a key with osc signkey --create localprj I get this in /srv/obs/log/src_server.log (I added the "but you used" line in the source code): 2010-08-04 18:59:22 [10022]: POST /source/osc2?cmd=createkey&user=jengelh usage: sign [-c|-d|-r] [-u user] <file> But you used: /usr/bin/sign --project osc2 -P /srv/obs/sources/:upload/signkey.10022 -g dsa@1024 800 osc2 OBS Project osc2(a)ares.medozas.de 127.0.0.1: /usr/bin/sign: 256 Why is obs-server-2.0.5 using all these options when sign-2.1.2 does not even accept them? -- 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] [PATCH] fix comps.xml generation
by Iain Arnell 04 Aug '10

04 Aug '10

--- This fixes the redhat-style comps.xml generation problem reported by Robert Xu. It also makes a better job of cleaning up old group.xml files. It needs to be applied to 2.0 and later. src/backend/bs_publish | 5 ++--- 1 files changed, 2 insertions(+), 3 deletions(-) diff --git a/src/backend/bs_publish b/src/backend/bs_publish index d6c51c4..229dd5b 100755 --- a/src/backend/bs_publish +++ b/src/backend/bs_publish @@ -546,8 +546,7 @@ sub createpatterns_comps { my @grps; for my $pattern (@$patterns) { my $pat = XMLin($BSXML::pattern, $pattern->{'data'}); - next unless $pattern->{'name'} =~ /^(.*)\.xml$/s; - my $grp = { 'id' => $1 }; + my $grp = { 'id' => $pattern->{'name'} }; for (@{$pat->{'summary'}}) { my $el = { '_content' => $_->{'_content'} }; $el->{'xml:lang'} = $_->{lang} if $_->{'lang'}; @@ -587,7 +586,7 @@ sub createpatterns_comps { sub deletepatterns_comps { my ($extrep) = @_; for my $pat (ls("$extrep/repodata")) { - next unless $pat =~ /^group/; + next unless $pat =~ /group.xml/; unlink("$extrep/repodata/$pat"); } } -- 1.7.2 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 2

[opensuse-buildservice] OBS 2.0.5 released
by Adrian Schröter 04 Aug '10

04 Aug '10

OBS 2.0.5 is on the way to http://download.opensuse.org/repositories/openSUSE:Tools/ As usual also available as appliance: http://en.opensuse.org/Build_Service/OBS-Appliance This is a pure bug fix release this time. Please find details below. Special thanks go to * David Greaves for init script fixes and * Iain Arnell for fixing redhat repo pattern generation From the release notes file: ============================ Updaters from 2.0.X can just update the packages and restart all services. Updaters from former releases need to check the 2.0.0 Release Notes file. Changes since 2.0.4: ==================== Changes: * api: do not allow operations on packages included via project link Fixes: * api: handle usage of default reviewers correctly * backend: handle package add or removal via project link to remote OBS correctly * backend: fixes in init scripts for workers using automatic storage setup * backend: fix for RedHat pattern generation (comp.xml) generation * backend: in existing, but configured keyfile is not fatal for publisher anymore -- 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] comps.xml
by Robert Xu 04 Aug '10

04 Aug '10

Hi all, Fedora's style of patterns with the yum metadata is by adding another file, comps.xml. What if it was possible to make a patterns file, and have OBS convert it into comps.xml and include it? Example of a comps.xml file: http://mirrors.kernel.org/fedora/releases/13/Everything/x86_64/os/repodata/… This could provide compatibility under other clients like yum. (Someone should make a how-to for creating a patterns file in the wiki... I'll look into it, maybe?) -- later, Robert Xu -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 10

[opensuse-buildservice] REMINDER: please extend the signkey of your projects
by Marcus Rueckert 03 Aug '10

03 Aug '10

hi to check when the key will expire/has expired: 1. osc signkey <yourproject> | gpg --import - example: [[[ $ osc signkey devel:languages:ruby | gpg --import - gpg: key 0E9AF123: public key "devel:languages:ruby OBS Project <devel:languages:ruby@build.opensuse.org>" imported gpg: Total number processed: 1 gpg: imported: 1 gpg: 3 marginal(s) needed, 1 complete(s) needed, classic trust model gpg: depth: 0 valid: 1 signed: 4 trust: 0-, 0q, 0n, 0m, 0f, 1u gpg: depth: 1 valid: 4 signed: 41 trust: 3-, 0q, 0n, 0m, 1f, 0u gpg: depth: 2 valid: 26 signed: 56 trust: 26-, 0q, 0n, 0m, 0f, 0u gpg: next trustdb check due at 2010-12-31 ]]] 2. run gpg --fingerprint <keyid> [[[ gpg --fingerprint 0E9AF123 pub 1024D/0E9AF123 2008-07-14 [expires: 2010-09-22] Key fingerprint = A9EA 39C4 9B6B 9E93 B686 3F84 9AF0 C9A2 0E9A F123 uid devel:languages:ruby OBS Project <devel:languages:ruby@build.opensuse.org> ]]] 3. if your key is expired or about to expire run: osc signkey --extend <yourproject> thank you in advance darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3