May 2008 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] How can i setup package signing on local obs?
by Carsten Schoene 10 Jul '08

10 Jul '08

-----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

5 12

[opensuse-buildservice] openSUSE:Tools:Unstable/obs-server-svn + build-svn + osc-svn update svn trunc -r 3984
by Martin Mohring 05 Jun '08

05 Jun '08

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

3 3

Re: [opensuse-buildservice] Missing important debian functionality
by Amilcar do Carmo Lucas 04 Jun '08

04 Jun '08

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

6 21

[opensuse-buildservice] proposal or repository for branding, wallpapers, artwork, themes etc.
by Stanislav Brabec 02 Jun '08

02 Jun '08

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

2 1

[opensuse-buildservice] [patch] spec file wizard
by Michal Marek 02 Jun '08

02 Jun '08

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

3 3

[opensuse-buildservice] frontend does too much when uploading a file
by Marcus Hüwe 30 May '08

30 May '08

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:)

2 2

Re: [opensuse-buildservice] Missing important debian functionality
by Amilcar do Carmo Lucas 29 May '08

29 May '08

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

1 0

Re: [opensuse-buildservice] Missing important debian functionality
by Michael Schroeder 29 May '08

29 May '08

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

2 4

[opensuse-buildservice] python scientific tools (like scipy) on opensuse 11?
by David Strozzi 29 May '08

29 May '08

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

3 4

[opensuse-buildservice] Missing important debian functionality
by Amilcar do Carmo Lucas 28 May '08

28 May '08

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

2 2

[opensuse-buildservice] Request: Align sorting of the package list inside "Builder/Projects/<name>" and "Builder/Projects/<name>/Status Monitor"
by Martin Mohring 28 May '08

28 May '08

Hi, I have seen lots of fine tuning inside OBS last days, including sorting issues inside the webclient. Since I am not the ruby expert, so I have a request: Could the package sorting inside the project status monitor and inside the project view be the same? I is a bit annoying (especially for large projects) if the sorting is completely different. What do you think? Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 4

[opensuse-buildservice] New Project Outside of Home
by Jason Record 27 May '08

27 May '08

I would like request two projects be added to the build service that are outside my home:<login> namespace. They are: Package Name: ntsutils Title: NTS Troubleshooting Utilities Description: A noarch package that contains supportconfig and chkbin. These tools are used heavily is troubleshooting system and application issues. Supportconfig gathers system information and organizes it to assist in resolving problems quickly. Chkbin checks and confirms a binary and it's shared library dependencies. Package Name: sc-plugins Title: Supportconfig Plugins Description: A set of plugin scripts to be included with a supportconfig tar ball. Plugins are scripts that extend supportconfig functionality. It appears the best place for these packages is openSUSE:Tools. However, I'm open to wherever it fits best. Jason Record Novell Technical Services World Wide Support Linux OS Novell, the leading provider of Information Solutions jrecord(a)novell.com 801-861-5955 --------------------------------------------------------------------- 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] openSUSE Build Service status
by Adrian Schröter 27 May '08

27 May '08

present: mls, abauer, ro, lrupp, froh, freitag, jcborn, poeml, adrian Minutes taker: froh, all errors added by adrian. Status: abauer - branch request takes devel project if no special parameter is given, change is non-intrusive, will go life it works with local testing. Status xml schema has been extended to pass data to clients. Will give back the real base project to the client. - headed to the railsconf, Portland, OR, back Tue, 2008-06-10 froh - digging through buglets after obs update freitag - blog entry that OBS is open to everybody and that the openSUSE project will allow everybody to contribute jcb - gave talk about KIWI internally, might get online as video - fixed scanner bug of download redirector tpatzig - new osc commands implemented - continued working on hermes web frontend (starship) adrian - devel projects are defined for most packages in openSUSE:Factory via script, but some are missing. Needs to get fixed. - Current maintainers will get a possibility to modify devel project definitions. - preparing talk on openSUSE day on LinuxTag - Coordinating 1.0 release announcement mls - scheduler is much fairer now, works smooth enough on factory - after bootstrap ~650 packages are built in parallel, blocking scheduler reaction for a while. - debuginfo support works now in backend (set debuginfo flag, this will build debuginfo packages), added to templates, schemata, buglet in API. this redefines %prep,%package so there is no need for "%debugpackage". This needs fixes in the frontend right now to get this working - reluctance to activate debuginfo because of tight disk space --> work around: don't enable debuginfo for now --> real fix: quota, analyze disk usage and split away debuginfo and source packages in not mirrored repositories. poeml - new osc release - after this (svn only currently) added branch call - respect $EDITOR if no check-in message is given, provide diff in message - make osc more robust wrt meta data formats - osc won't work on sles9 (python way too old). No real need to work on this atm. - use current distro to build to old targets, old runtime is supported, building new code on old environment isn't TODOs for 1.0 release: abauer: implement branch call devel project handling. adrian: finalize devel project definitions in openSUSE:Factory all: document how to use the new branch/merge request features poeml: tell real target project when brancjing, depends on abauer to go life with this. add --ignore-devel-project switch to branch call factory ftp tree generation has less priority than source handling. mls: dig into quota handling -- Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business OPS Engineering Maxfeldstraße 5 Processes and Infrastructure Nürnberg SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- 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] Re: Meta-data change for network:telephony
by Archie Cobbs 27 May '08

27 May '08

On Fri, May 23, 2008 at 11:43 AM, Peter Nixon <listuser(a)peternixon.net> wrote: > When you put another project as a dependency of your project in the metadata > it will allow your packages to build, but then when someone tries to use > your repo to install your package those dependencies will not be supplied if > they are needed as "Requires" forcing the user to go off in search of those > dependencies too. > > When you "link" a particular package into your project it is rebuilt which > takes up resources on the Build Service but is usefull if you want one of > IT'S dependencies to be supplied by a package in your project without > touching its spec, or if you want to build for a target which is not enable > in it's home project. Once built the package is uploaded to the mirrors > which also takes up mirror resources, and it also will have a different > build version number which means that you may (or may not) randomly upgrade > existing packages of the same name on your users system.. > > When you "aggregate" a particular package into your project it is not > rebuilt, but rather copied directly from its home project. It keeps the same > version number, so when it is uploaded to mirrors it does take up resources > on them but it will not replace the same package if already installed on a > users system (from the parent project). This is the preferred and cleanest > way of sucking in a few extra dependencies to your project. Peter, Thanks for the very clear and helpful description. This description seems to be missing from the wiki, so I added it, under a new section titled "Terminology". Hopefully I didn't include any wrong information. I'd appreciate a review from the OBS experts (I'm cc'ing the OBS list): http://en.opensuse.org/Build_Service/Tutorial Thanks, -Archie -- Archie L. Cobbs --------------------------------------------------------------------- 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] [ANN] osc 0.101 release (branch command, commit message editing)
by Peter Poeml 27 May '08

27 May '08

Hi, a new osc package is building in openSUSE:Tools right now (hopefully ;) The main changes are: * add osc branch command, using the branch API call to branch a package to home:poeml:branches:PRJ/PKG => this can be used to work on packages like those in Factory, where you don't have write permissions. You can "osc submitreq" your changes to Factory then. * osc commit now opens $EDITOR, if no commit message was specified on the commandline. Minor changes: - improved error handling, when API returns HTTP status code 400 (bad request) - osc status: implement -q/--quiet switch - osc info: slightly more verbose - osc deletepac: allow deletion of multiple packages at once - make "osc meta prjconf <project> -e" work again (probably caused by r3702) - osc maintainer: new -D/--devel-project switch Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development

1 0

[opensuse-buildservice] local obs problem - packages are not published after build
by Christian 27 May '08

27 May '08

Hi I setup a local obs. Added needed repos without problem. Great so far. :) under home:Admin added a package and triggered build. Package is build and webclient shows "finished" but build packages are not shown. They aren't listed under "/srv/obs/build/home:Admin" and "/srv/obs/repos". inside "/srv/obs/repos" there aren't any directories. And if I try a "rebuild" nothing happens. Thanks for any help. Kind regards Chris --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 10

[opensuse-buildservice] osc on SLES10
by Christian 26 May '08

26 May '08

Hi, how to fix missing dependencies to get osc installed on sles10 ? Es sind keine installierbaren Anbieter von python-elementtree verfügbar für osc-0.100-1.1.x86_64[20080517-232117] thanks for any advice. used repos: build:/srv/obs/build # zypper sl # | Enabled | Refresh | Type | Name | URI --+---------+---------+------+-------------------------------------+------------------------------------------------------------------------------- 1 | Yes | Yes | YUM | 20080517-233130 | ftp://192.168.101.1/pub/opensuse/repositories/server%3a/http/SLE_10 2 | Yes | Yes | YaST | SUSE Linux Enterprise Server 10 SP1 | ftp://192.168.101.1/pub/sles10/x86_64-SP1/CD1 3 | Yes | Yes | YUM | 20080517-231745 | ftp://192.168.101.1/pub/opensuse/repositories/devel%3a/languages%3a/lua/SLE_10 4 | Yes | Yes | YUM | 20080517-231318 | ftp://192.168.101.1/pub/sles10/x86_64-SP1/updates 5 | Yes | Yes | YUM | 20080517-232117 | ftp://192.168.101.1/pub/opensuse/repositories/openSUSE%3a/Tools/SLE_10 6 | Yes | Yes | YUM | 20080517-235011 | ftp://192.168.101.1/pub/opensuse/repositories/ruby/SLE_10 7 | Yes | Yes | YUM | 20080517-231414 | ftp://192.168.101.1/pub/sles10/extras Kind Regards Chris --------------------------------------------------------------------- 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] Can not create home project
by Felix-Nicolai Müller 26 May '08

26 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, sadly, I cannot create a home project. Using the webclient I get the following error: http://paste.phati.de/750 Using osc meta prj home:fnmueller -e I get: http://paste.phati.de/751 This is my XML file: http://paste.phati.de/752 We could not solve this problem in #opensuse-buildservice. I suspect my OBS account is somehow messed up. Could someone please take a look at this prob? Thank you Felix (fnmueller) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIOdihaQ44ga2xxAoRAvYMAJ0QdYXOwVT3aPPhDZOdj5BLRNY1EACfWaeF /yh8xRnOw6nL5s2Hi5bcX0I= =TN7s -----END PGP SIGNATURE----- --------------------------------------------------------------------- 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] eclipse-bs status report, week 21
by Michal Marek 26 May '08

26 May '08

[GREEN] - long prepared some sketches of the user interface, see http://picasaweb.google.com/longhong1985/MockupScans (click "Download Photo" to view the images in higher resolution) - learning osc --------------------------------------------------------------------- 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] Build a whole project with osc
by Carlos Goncalves 22 May '08

22 May '08

Hi, As requested by darix, I'm emailing oS-buildservice to ask for a new osc feature - capability to build a whole project (eg. KDE:KDE4:UNSTABLE:Desktop) with one single command. Currently there is only possible to do things like $ osc build PLATFORM ARCH BUILD_DESCR Which restricts builds to a given PRJCT:PGK so if one wants to build a whole project the following won't work: $ osc build PLATFORM ARCH PROJECT With my osc feature request something like it would be possible. For what I have understood, darix pointed out that to do that some API changes/exposing would be needed or so, which seems to concern him a little. - Build service/osc team, what do you thing about this request? Do you thing it's possible to implement? Any limitations? - Users, please let developers know if you also like this idea! The discussion has just began...! ;-) -- Regards, Carlos Goncalves --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

6 11

[opensuse-buildservice] RFC: small patch for "osc commit" with big effect
by Peter Poeml 22 May '08

22 May '08

Hi, Index: osc/commandline.py =================================================================== --- osc/commandline.py (revision 4001) +++ osc/commandline.py (working copy) @@ -1029,6 +1029,9 @@ ${cmd_usage} ${cmd_option_list} """ + if not opts.message and not opts.file: + sys.stderr.write('You didn\'t specify a commit message.\n' + 'In the future, this will be mandatory.\n') msg = '' if opts.message: msg = opts.message Later, giving a commit message (-m / -F) will be enforced. What do people think about this? I think it is good, and I know some that agree, and I haven't seen anyone disagreeing yet. We can also make the messages mandatory right away, depending on what you think... Thanks, Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development

8 14

[opensuse-buildservice] Webclient
by Dirk Stöcker 20 May '08

20 May '08

Hello, could someone please add sorting for the repositories in "src/webclient/app/views/package/_buildstatus.rhtml" (affects https://build.opensuse.org/package/show?package=gpsbabel&project=Applicatio… right side) It is really disturbing, that these entries are not sorted and I was unable to fix it myself (don't know enough ruby for that). Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- 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] setting up an OBS
by John Calcote 20 May '08

20 May '08

Hi everyone, I've really enjoyed using the official obs server, and now I have a need to set one up locally on my own network. Can someone point me to the instructions for doing this? I presume there's a wiki page somewhere that gives a brief overview of which packages you need and such. Thanks, John --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

6 7

[opensuse-buildservice] Build Service Status
by Adrian Schröter 20 May '08

20 May '08

present: freitag, mjung, jcborn, tpatzig, froh, adrian, poeml, abauer Status: * general * 1.0 - devel project implementation General Status: =============== freitag: * Hermes support Jabber notifications now * Bugfixing and Documentation work for Hermes * Open question is if we want to run an own jabber server or to use existing ones. * Will be on LinuxTag next week. mjung: * Thinking about how to implement the trust handling. One single global trust seems to have some short commings, an individual trust to certain persons might be the way to go. Looking for specialised documentation around these topics and discusses with different people in house. * Will be on LinuxTag next week. jcborn: * Created installation isos with kiwi. YaST does start up, but YaST has some problems. Most likely due to missing incorrect repository setup. Need to debug esp. multiarch setup problems. tpatzig: * Worked on Starship, support for comments for types. * Implemented a filter for project results in osc. abauer: * Updated api.opensuse.org to current svn -> support for devel project -> branch request call * Fixing several bugzilla reports. adrian: * created scripts to write "devel project" definition to all packages in openSUSE:Factory. They run still in dry mode. * Debugged build host issues, switched all build systems to use LVM and switched off a number of build hosts which have currently problems. * Current backend server is at it's end (was running into swaping out schedulers, which decreased the speed a lot). We have already a new system, which was unstable in the past, but seems to run stable after firmware uprade. This should solve this. poeml: * released new osc package. Details are on http://en.opensuse.org/Build_Service/News 1.0 Status: =========== devel project handling: * Discussion to implement an api call to allow devel project change in foreign projects. This need a permission check, allowing it only, if the devel project points a project with write access for the user. * The (web/osc) client needs to check before branch, if devel project exists and report this to the user. The client should have a option to ignore the devel project setting. * look up for devel project on branch should get implemented in the API and not in the clients. AI: freitag define api branch call to follow devel project definition and how to ignore to follow the devel project. AI: adrian define used xml fields and create submission workflow in documentation. -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) 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] Dependencies from another buildservice repo
by Matthew Smith 17 May '08

17 May '08

Hi everyone, Matthew Smith (developer of QTM - qtm.blogistan.co.uk) here. The latest version of my package links against the QtDBus module. However, the version of CMake supplied with openSUSE 10.3 does not seem to recognise that module, which means the compiler can't find the include files. There is a newer version of CMake, in the devel:tools:building repository. However, both the methods I've used for using this package fail. I have linked the cmake package into my home project, but building still fails and tells me that nothing provides cmake at the version specified. I also tried editing the metadata in osc, adding this line into the repository element: <path repository="standard" project="devel:tools:building"/> However, it fails to save, with this error: <?xml version="1.0" encoding="UTF-8"?> <status code="package_save_error"> <summary>error saving project: unable to walk on path 'devel:tools:building/standard'</summary> <details></details> </status> What do I need to do? Thanks in advance, Matt Smith -- http://www.blogistan.co.uk/qt/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1