openSUSE Build Service May 2008

buildservice@lists.opensuse.org

45 participants
71 discussions

[opensuse-buildservice] How can i setup package signing on local obs?

by Carsten Schoene

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, can someone explain how to setup the signd & sign program on a local bs setup? I got the daemon running, and the sign program connects but than hangs, while the signd starts some subprocesses and nothing happens. I'm not sure where to place the key files used for signing, maybe someone can bring some light into the darkness ;) attached, a processlist and log entrys of signd thanks Carsten -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHRuae6NfbfHY52TsRAgubAJwNh/AXwCe6/XCVp2dPix/B4l0BdwCeLVVf z3ee5EhaDBaeVIcGeWdVpDI= =X06F -----END PGP SIGNATURE----- obsrun 25247 0.0 0.4 12632 9284 ? S 10:57 0:00 /usr/bin/perl -w ./bs_repserver obsrun 25248 0.0 0.0 1820 560 ? S 10:57 0:00 /srv/obs/sign/sign -r /srv/obs/jobs/x86_64/multimedia::SLE_10::portaudio18-6337f29c4f0b6a49147cef12bb42056f:dir/portau obsrun 25251 0.0 0.4 12632 9284 ? S 10:57 0:00 /usr/bin/perl -w ./bs_repserver obsrun 25252 0.0 0.0 1816 552 ? S 10:57 0:00 /srv/obs/sign/sign -r /srv/obs/jobs/i586/multimedia::SLE_10::portaudio18-6337f29c4f0b6a49147cef12bb42056f:dir/portaudi root 28395 0.0 0.1 9348 2816 ? Ss 13:34 0:01 sshd: root@pts/0 root 28397 0.0 0.0 4276 2044 pts/0 Ss 13:34 0:00 -bash postfix 31139 0.0 0.0 5692 1716 ? S 14:51 0:00 pickup -l -t fifo -u root 31790 0.0 0.0 2480 856 pts/0 R+ 15:26 0:00 ps axu obs-web:~/bin # ps axu|grep sign root 5981 0.0 0.1 4868 3196 ? Ss Nov21 0:00 /usr/bin/perl ./signd obsrun 6328 0.0 0.0 1820 560 ? S Nov21 0:00 /srv/obs/sign/sign -r /srv/obs/jobs/i586/internetx:mysql5::SLE_10::libmemcached-3baa823c6ef50fd1588d72fdcb28e683:dir/libmemcached-0.9-5.7.i586.rpm root 6329 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6330 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6331 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6332 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6333 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6334 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6335 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6336 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6337 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6338 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6340 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd obsrun 25248 0.0 0.0 1820 560 ? S 10:57 0:00 /srv/obs/sign/sign -r /srv/obs/jobs/x86_64/multimedia::SLE_10::portaudio18-6337f29c4f0b6a49147cef12bb42056f:dir/portaudio18-devel-18.1-1.1.x86_64.rpm obsrun 25252 0.0 0.0 1816 552 ? S 10:57 0:00 /srv/obs/sign/sign -r /srv/obs/jobs/i586/multimedia::SLE_10::portaudio18-6337f29c4f0b6a49147cef12bb42056f:dir/portaudio18-devel-18.1-1.1.i586.rpm obs-web:~/bin # cat /srv/obs/log/signd.log 2007-11-21 17:04:21: signproxy started 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2

13 years, 6 months

[opensuse-buildservice] openSUSE:Tools:Unstable/obs-server-svn + build-svn + osc-svn update svn trunc -r 3984

by Martin Mohring

Hi, I have put an updated, svn trunc -r 3984 based revision of the obs-server-svn + build-svn + osc-svn into openSUSE:Tools:Unstable. It has ate least these changes: - apidocs is displaying - build issues fixed, like mentioned by adrian, including a bug that prevented building debian based targets without XEN - download adresses fixed in webclient in the project view - obs-worker code only need /etc/sysconfig/obs-worker changed, no other files, when running remote - webclient uses https to communicate with server - "develproject" support - latest osc updates - support debuginfo project/package flag, add release workaround for kernel folks - added xml schema for _link files, causes broken _link files to be rejected I am sure I forgot to mention many important things... I also cleaned up "buildservice/dist" in svn repository now to be in sync with obs-server-svn package again. KEEP HAPPY TESTING, although it is a development release (I gave it a spin here before submitting, so it is not fundamentally broken). Regards, Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

13 years, 7 months

Re: [opensuse-buildservice] Missing important debian functionality

by Amilcar do Carmo Lucas

On Thursday 29 May 2008 15:52:49 you wrote: I tried to use the new feature: https://build.opensuse.org/package/view_file?file=KDevelop3-xUbuntu_8.04.ds… But it does not work: https://build.opensuse.org/package/live_build_log?arch=x86_64&package=KDeve… I've read the debtransform file. But I do not understand the dotar() function. I think that is where the problem is. Can you please add comments to the code ? The entire file only has two small comments :( -- Amilcar Lucas KDevelop.org webmaster --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

13 years, 7 months

[opensuse-buildservice] proposal or repository for branding, wallpapers, artwork, themes etc.

by Stanislav Brabec

Hallo. I would like to propose a new repository (repositories) for several types of artwork: Branding I am thinking about subprojects with particular brandings. First planned item is the "Example" branding template. Proposing: Branding:Example or Artwork:Branding:Example Wallpapers and backgrounds It would be nice to package popular Propaganda abstract wallpapers set altogether with desktop integration stuff (KDE+GNOME wallpapers, nautilus background patterns,...). Proposing: Artwork or Artwork:Wallpapers Themes and metathemes Maybe bad idea. Could be GNOME:Themes, KDE:Themes or Artwork:GNOME, Artwork:KDE. Technical topic: Some of these project would be completely distro independent. Is it possible to create such build to prevent duplicated packaging of identical files? -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 966, +49 911 740538747 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

13 years, 7 months

[opensuse-buildservice] [patch] spec file wizard

by Michal Marek

Hi, I'm working on a new feature of the buildservice, a wizard that helps with creating spec files (and in the future maybe with other tasks). See http://lizards.opensuse.org/2008/05/26/learning-ruby/ . I now have a working prototype, including a webclient interface. It consists of - A controller on the api (frontend), that sends a set of xml-encoded questions to the client, receives answers from the client and either asks more questions (suggesting defaults where possible) or generates a spec file - A webclient part that converts the xml questions into a HTML form, let's the user fill in the form and sends the responses to the api. It should be possible to also write an osc command that asks the questions on terminal instead. Here are some screenshots of the webclient: http://michal.markovi.net/images/bs-wizard-2008-05-30-1.png http://michal.markovi.net/images/bs-wizard-2008-05-30-2.png http://michal.markovi.net/images/bs-wizard-2008-05-30-3.png http://michal.markovi.net/images/bs-wizard-2008-05-30-4.png http://michal.markovi.net/images/bs-wizard-2008-05-30-5.png http://michal.markovi.net/images/bs-wizard-2008-05-30-6.png http://michal.markovi.net/images/bs-wizard-2008-05-30-7.png http://michal.markovi.net/images/bs-wizard-2008-05-30-8.png http://michal.markovi.net/images/bs-wizard-2008-05-30-9.png An example of the an xml document describing the questions: $ curl -n 'http://localhost:3001/source/home:mmarek/hello/_wizard' <?xml version="1.0" encoding="UTF-8"?> <wizard last="false"> <label>Step 1/2</label> <legend>What do you want to package?</legend> <entry name="tarball" type="file"> <label>Source tarball to upload</label> <legend></legend> <value></value> </entry> </wizard> - label and legend are self-explanatory. - value is the default value to present to the user. - If the last attribute of the root element is true, it means that the client shouldn't send any further replies. - There can be an arbitrary number of <entry> elements, each representing a question to ask - The name attribute of an entry has the same meaning as in HTML forms - type can currently be one of - file: the client should PUT a file to the package directory in a *separate* request and send the filename as response (e.g. tarball=foo.tar.gz) - text or longtext: text data, longtext expects a multiline text (e.g. the package description) Client sends back either a GET request with the data in the query string or a POST request encoding the data either as application/x-www-form-urlencoded or multipart/form-data (i.e. anything rails handles). All communication with the API happens via the /source/<project>/<package>/_wizard url, which means that the client must first create the package by uploading a dummy _meta (see the wizard_new action in the webclient). To maintain it's state, the frontend stores a wizard.xml file in the package directory. I know it's a hack, but it seemed as the easies way for the time being :). $ curl -sn 'http://localhost:3001/source/home:mmarek/hello/wizard.xml' | xmllint -format - <?xml version="1.0"?> <wizard> <data name="name">hello</data> <data name="tarball">hello-2.3.tar.bz2</data> <guess name="license">GPL v2 or later</guess> <guess name="version">2.3</guess> </wizard> The patch is attached. Note that this my first ruby code ever (I started reading some tutorials this week), so please bear with me. If some of the ruby & rails experts have some time to review the patch for security, bugs, style, etc, that would be great. Michal

13 years, 7 months

[opensuse-buildservice] frontend does too much when uploading a file

by Marcus Hüwe

Hi, during a file upload the frontend performs superfluous (IMHO) tasks like sending the package metadata (which doesn't change during the upload) to the backend etc. The problematic method is "update_timestamp" in the Package() class (see models/package.rb). Instead of simply updating some timestamp tables it regenerates the complete metadata. I attached a small patch which _only_ updates the timestamp without touching any metadata. Btw. with this patch we gain a small perfomance boost: - executing the old version takes around 2.81 seconds - executing the new version takes around 1 second (measured with ruby's 'profiler' module) Marcus Ps. I don't know if this is a good "ruby style" but it works for me:)

13 years, 7 months

Re: [opensuse-buildservice] Missing important debian functionality

by Amilcar do Carmo Lucas

On Thursday 29 May 2008 15:52:49 you wrote: > There's also 'Debtransform-Series' if you want to use different > series files in your dscs. > > > How to use these tags ? What should they contain ? > > AFAIK you're already using them. Yes, I'm using the tags, but it would be nice to have documentation on the wiki, so that others could also use them. Otherwise only you and I know how to use them. For example mo one on the IRC channel knows how to use them. Cheers, -- Amilcar Lucas KDevelop.org webmaster --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

13 years, 7 months

Re: [opensuse-buildservice] Missing important debian functionality

by Michael Schroeder

On Wed, May 28, 2008 at 06:13:06PM +0200, Amilcar do Carmo Lucas wrote: > > So you want some more functionality for the "debtransform" program. > > > > Currently you could just add your control file to the "debian tar" > > file you already have, e.g. debian-xUbuntu_6.06.tar.gz. > Yeap I know, but that means lots of code duplication. Why's that? You already have those debian-<flavor>.tar.gz files, can't you just add another file to them? Or do you want to get rid of them? > > If that's not flexible enough, we would need a way to tell debtransform > > which files to use and what name the files should get, i.e. > > > > debian-xUbuntu_8.04.control -> debian/control > > > Yeap that would be great, the debian.tar.gz file would provide the base files > for all distros, after that the other files would come from the debtransform. > > > I don't think it is a good idea to imitate the way the source > > server selects the dsc file in debtransform, one such selection > > should be enough. So I'd prefer some way of putting this information > > in the corresponding dsc file. > I do not get your idea here. Well, you already use "Debtransform-*" in your dsc file. Here are two ideas: 1) allow multiple tar files in "Debtransform-Files-Tar". You could use debian.tar.gz for your base files and debian-<flavor>.tar.gz would just contain some files that need to be different. 2) add some new "Debtransform-Files" tag where you can specify in some syntax which files to take and where to put them. Cheers, 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

13 years, 7 months

[opensuse-buildservice] python scientific tools (like scipy) on opensuse 11?

by David Strozzi

Hi, I am beta-testing opensuse 11, most things seem to work. There's some annoying aspects of the KDE desktop but that's not for here. I was hoping to test out some scientific tools in python. I've gotten ipython and numpy, from the build service, for OS11 (ie, for the factory). It seems scipy hasn't been built yet. scipy's in the science project on the build service, and it's been built against various OS10's, but not yet for OS11. Anyone mind giving it a try? On a related note, I noticed numpy and matplotlib are part of project devel:languages:python. I am not active on the build service and don't know how things are organized. Namely, I wonder why scipy is in science but the others in d:l:p. Thanks, Dave --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

13 years, 7 months

[opensuse-buildservice] Missing important debian functionality

by Amilcar do Carmo Lucas

Hi, I'm a VERY demandant user of the build system. I build for ALL supported distros. As such I need to support all xUbuntu flavors. I got around that by providing one .dsc file per distro. It works great, I have: # KDevelop3.dsc for normal cases # KDevelop3-xUbuntu_6.06.dsc for 6.06 # KDevelop3-xUbuntu_8.04.dsc for 8.04 And it works fine, I would prefer patches, instead of code duplication, but for now it just works. But it does not work for debian "control" files :( I want to have: # debian.control # debian.control-xUbuntu_6.06 # debian.control-xUbuntu_8.04 But I get: dpkg-checkbuilddeps: failure: cannot read debian/control: No such file or directory dpkg-buildpackage: warning: Build dependencies/conflicts unsatisfied; aborting. Can someone fix it please ? Regards, -- Amilcar Lucas KDevelop.org webmaster --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

13 years, 7 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service May 2008