June 2008 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] rpmlint and "Packager"
by Dirk Stöcker 23 May '09

23 May '09

Hello, whether I add "Packager" in a spec file or not, rpmlint complains in both cases. One time because of hardcoding. The other time because it is missing. Could this please be fixed? What I would like to see is that the buildservice-email-address also used in the GPG key of the repository is automatically copied into the spec (like e.g. changelog or revision). Is this possible (thought that would not fix the hardcoding error message) or can the name+email be added in the build command directly? 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

4 7

[opensuse-buildservice] spec file wizard - how to proceed?
by Michal Marek 29 Aug '08

29 Aug '08

Hi, as you probably noticed, the buildservice web interface now has a wizard that helps with writing spec files. Yesterday, I improved it to generate better spec files for perl and python modules (not yet on build.o.o) and I hot already advice on how to add support for apache modules and ruby gems ;-). Of course I'd like the wizard to be able to package as many kinds of packages as possible, but I see some problems I'd like to solve somehow before adding more features: Problem #1 (more theoretical than practical): the main part of the wizard is implemented in the frontend (aka API), the webclient only translates xml to html forms and vice versa. The reason for this is that I'd like to add a wizard interface also to osc one day. The problem is that so far, the frontend has been just a simple proxy to the backend, with access control, without any fancy functionality. Now the wizard adds potentially buggy code that doesn't necessarily need to be there (it would be easily implemented as a standalone application talking to the frontend). The only reason for having the wizard on the frontend is to be able to use it from different clients easily. Problem #2 (practical): To implement good heuristics, the wizard at least needs to look into the source tarball (if not run some commands...). Here comes the problem: 'tar tf foo-1.1.tar.bz2' can take a *lot* of cpu time, so where to perform such expensive actions? a) on the frontend - can be abused for DoS easily b) let the client send the filelist along with the tarball - makes the client implementation too complicated, plus moves the DoS problem from the frontend to the webclient c) on the backend, dispatching the jobs to workers - would also allow for more dangerous analysis of the package, but would impose additional delays d) create a separate wizard service and do all the job there - would also solve problem #1, but would make the client implementation a bit more difficult (need to talk to two different servers) e) [insert great idea here]? Michal --------------------------------------------------------------------- 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] 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] Issues with debian files
by Piotr Pokora 30 Jun '08

30 Jun '08

Hi! I have quite weird issue with building debian binaries at opensuse build system. Locally ( debian etch ) , debian files are created without any problem ( with the same control file). I copied some information to pastie: http://pastie.org/224742 Piotras --------------------------------------------------------------------- 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-ftp 0.4
by Michal Marek 30 Jun '08

30 Jun '08

Hi, I uploaded a new version of the osc ftp plugin: http://software.opensuse.org/search?baseproject=home%3Amichal-m&q=osc-ftp . The most important change since version 0.3 is the addition of the edit (vi) command: osc ftp osc /source > cd home:michal-m osc /source/home:michal-m > vi icewm/_meta icewm-lite/_meta GET icewm/_meta GET icewm-lite/_meta 2 files to edit PUT /tmp/osc-ftp.ZsGUxd/_meta PUT /tmp/osc-ftp.ZsGUxd/2-_meta osc /source/home:michal-m > Also, cd now understands 'cd -' as 'change to the previous directory'. have fun, Michal --------------------------------------------------------------------- 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] eclipse-bs status report, week 26
by Michal Marek 30 Jun '08

30 Jun '08

[GREEN] - Long finished his thesis - got svn access, first code is under https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice/src/tools/ecli… --------------------------------------------------------------------- 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] Importing repo keys with OSC
by Pavol Rusnak 30 Jun '08

30 Jun '08

Hi all! I was building one of my packages with OSC when it bailed out with error: The following package could not be verified: /var/tmp/osbuild-packagecache/games/openSUSE_11.0/x86_64/SDL-1.2.13-49.6.x86_64.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#53a2e3f5) - If the key is missing, install it first. For example, do the following: gpg --keyserver pgp.mit.edu --recv-keys 53a2e3f5 gpg --armor --export 53a2e3f5 > /home/prusnak/keyfile-53a2e3f5 and, as root: rpm --import /home/prusnak/keyfile-53a2e3f5 Obviously the key is missing, but the problem is that it is not available from public PGP/GPG servers (no one has uploaded there yet). While I agree that somebody (project maintainer and/or OBS folks) should take care of these keys, we shouldn't give instructions that do not work either. I usually solve this situation by adding repository through zypper and it asks whether to import the right key (thus it has to be present in the repo structure somewhere). Isn't it possible to import the key (interactively) from repodata instead of printing broken instructions? -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o Package Maintainer Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9, CR prusnak[at]suse.cz 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] Newbie question
by Petit Eric 28 Jun '08

28 Jun '08

Hi I would like to know if with the Web interface of Open Suse Build service, i'm abble to manage two version of the same software/project. Lets say project "cs-obexftp" Can i have files : csobexftp0_14.spec csobexftp.0.14.tar.bz2 csobexftp0_17.spec csobexftp.0.17.tar.bz2 and then see : csobexftp.0.14.rpm csobexftp.0.17.rpm ? Thank's --------------------------------------------------------------------- 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] discontinued distributions
by Adrian Schröter 27 Jun '08

27 Jun '08

Hi, After the discussion from last month around the discontinued distribution handling, here's a proposal how to handle them in future. "Discontinued distributions" are the distributions, which receive no regular security updates anymore. These distributions stay accessible below DISCONTINUED name space. This means SUSE:SL-10.0 is accessible as DISCONTINUED:SUSE:SL-10.0 for example. We have currently the following distributions below DISCONTINUED names space: SUSE Linux 10.0 SUSE Linux 10.1 Fedora 6 Mandriva 2006 We will remove the official projects and all repositories building against them in two weeks (if we are not forced to do it earlier due to disc storage problems). The official 10.1 ftp tree from ftp.opensuse.org will get removed end of the year. If you want to keep building against these, you need to modify your project configuration replacing the project name of the path tag. Please keep in mind that the quota system will disable your whole project in case you reach quota setting. Also important, using discontinued distro means that: * Installing a package might not be possible because dependencies can not get solved (due to the fact that distro installation repo disappeared from the servers as well) * Using the repositories should not be done from a system connected to the internet. thanks adrian PS: we are again at > 95% disk usage, we will increase the disk space again, but we should remove all not necessary repositories to keep our resource for the really often downloaded stuff. Thanks a lot for your help. -- 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

6 6

[opensuse-buildservice] how to substitute a package including version requirement
by Marc Dietrich 26 Jun '08

26 Jun '08

Hi, I have the following substitution in my prjconf for fedora: Substitute: libcares-devel c-ares-devel In the spec file I wrote: Build-Requires: libcares-devel >= 1.5 but this can't be substituted, because it includes a version requirement (which should be the same as for c-ares-devel). Something I can do about it? Marc --------------------------------------------------------------------- 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 _link vs. _aggregate, saving resources
by Roman Fietze 26 Jun '08

26 Jun '08

Hello Everybody, I'm relatively new to the build service, abd I hope this question or the answer to it is not somewhere else and too easy to find. Details: I need libqwt5 to build s specific version of the most recent bacula version. I borrowed bacula from home:bastianfriedrich/Bacula and I am using a _link to his package and a patch to the spec file switching from SQLite to mySQL. I hope this is correct. Now, bacule needs libqwt5. I detected that bastianfriedrich links from dstoecker. So I was using dstoecker/libqwt using _aggregate, because I need it absolutely unchanged. I turned the words about _link and _aggregate from Tips&Tricks in my brain up and down, and I am still not sure that I am using the correct solution, trying to be a nice build service citizen. Q0: Where can I find a detailed description of the different XML files used for the build service? If there is any documentation answering the following two questions, just be so kind and ignore them. Q1: Should I use _aggregate in the case of libqwt5 is I do, or a _link? Q2: Or can I somwhow build my version of bacula directly to any other project/package without even _linking or _aggregating libqwt5? I really do not need this one in my own repository subdirectories. If yes, how? Thanks a lot for any help. Roman -- Roman Fietze rfno(a)fietze-home.de --------------------------------------------------------------------- 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] How to change password?
by Matwey V. Kornilov 25 Jun '08

25 Jun '08

Hi, I've installed obs 0.9.99 on my own server. How to change password for default admin account? There is the page change_password.rhtml in frontend, but I failed to open it. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

9 18

[opensuse-buildservice] Build Service downtime 2nd July
by Adrian Schröter 25 Jun '08

25 Jun '08

As announced earlier, we will do our maintenance day on Wednesday next week, the 2nd July A server room will get an upgrade and at the same time we may upgrade also our backend server. This might take the whole day and maybe even some hours on thursday. This will affect all package building, the access to build status and sources and also the package search behind http://software.opensuse.org/search. The current state of our backend server is that it is very loaded, the filesystem is nearly full which makes the system also slow. Please do NOT create large new repositories atm, we would need to remove them to keep the service running. thank you for your patience. adrian -- 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] Add repository (new)
by Ciro Iriarte 24 Jun '08

24 Jun '08

Hi, Trying to add a repository with "Add Repository (new)" I get a much nicer interface, I can drag and drop the distribution I would like to add, but then I can can't find a "OK" or "Done" or "Proceed" button... So basically I doesn't allow me to add repositories to a project... Regards, Ciro --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 4

[opensuse-buildservice] Talk about the build service
by Vincent Untz 24 Jun '08

24 Jun '08

Hi, I'll be attending the RMLL conference next week: http://2008.rmll.info/ That's a big community event in France. And I'm doing a talk about the build service there since, well, it's really cool :-) I'll prepare my slides in the next few days, so if you can think of things that are really important and that I shouldn't forget, just tell me. FWIW, I'll most probably use the doc in the wiki and the LinuxTag talk as starting points. Thanks, Vincent -- Les gens heureux ne sont pas pressé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] Build Service Status wk 24
by Adrian Schröter 24 Jun '08

24 Jun '08

present: lrupp, rlihm, froh, jcborn, mjung, mls, adrian, poeml, mls Topics: * General Status round rlihm: * Worked on download page for 11.0 release. * Followed up on build service web design together with Sigi. froh: * Rethinking configuration system for build service (one config file (set) for frontend and backend) jcborn: * Code modularization in kiwi * Focusing on ftp tree generation, goal is to have one module (aka kiwi plugin) for DVD and FTP tree mjung: * Finished proposal write up for trust system, request for feedback from group before public presentation. adrian: * Working again on image system again, goal is to get LimeJeOS image building working in OBS. * Removed discontinued distributions and repositories -> we have some space again to run the service. * prepare to add further 600GB to the storage. We will need a downtime for this. abauer: * Fixed smaller things on web client. * Finished promo DVD order page. * Added "involved project / package" list. It shows all projects and packages where the user is added as maintainer. * Gave overview about Ruby on Rails conference visit. poeml: * Focused on 11.0 release from infrastructure side. -- 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

5 7

[opensuse-buildservice] rpmlint and 11.0
by Detlef Steuer 24 Jun '08

24 Jun '08

Hi, I understand, why rpmlint is a good thing. But my important packages stopped to be built with the release of 11.0. More precisely: They get built, but they get rejected after successful builds for too many rpmlint warnings/errors. My questions: a) Is there a way for at least temporarily removing rpmlint checks? b) My packages built fine all the time in Factory. I thought everything was fine for a quick release afer 11.0 came out. Where should I have found out _beforehand_, that a policy change regarding rpmlint will happen at the time of release 11.0 . My, perhaps naive, idea was, that new things get tested in Factory, exactly to be ready at release time. How should I have known? That's a serious question. I don't want to be bitten again in the future. Where was that information distributed? Even if I search on opensuse for rpmlint now, I only find references how to willingly start rpmlint, no notice of forced rpmlint checks starting with 11.0. Thx in advance Detlef Steuer --------------------------------------------------------------------- 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] openSUSE 11 and RPMLINT checks
by Andrea Florio 24 Jun '08

24 Jun '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 what's wrong now? rpmlint looks to be broken (on x86_64 only) > RPMLINT report: > =============== > Traceback (most recent call last): > File "rpmlint.py", line 293, in <module> > File "rpmlint.py", line 97, in main > File "rpmlint.py", line 166, in runChecks > File "TagsCheck.py", line 708, in check > File "Filter.py", line 24, in printError > File "Filter.py", line 45, in _print > TypeError: not all arguments converted during string formatting > md: stopping all md devices. > xenbus_dev_shutdown: device/console/0: Initialising != Connected, skipping > System halted. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFIYLuhyCZT87TFPugRAj8eAKDaPK//9y15knAKSjK6stkzEDcuDQCfZb5x 0nzk2UWgS/lAkO8P9j+52WM= =VqwO -----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 2

Re: [opensuse-buildservice] conditional tags in debian control file
by Mathieu OUDART 21 Jun '08

21 Jun '08

Thanks Amilcar, good to see that it's possible :) The news link doesn't work for me but I saw your project files. So suffixing your sources with the platform (-xUbuntu_8.04) is enough for OBS or do you script it somewhere (I looked around but didn't find it) ? -- Mathieu OUDART - MindTouch ----- Original Message ----- From: "Amilcar do Carmo Lucas" <webmaster(a)kdevelop.org> To: opensuse-buildservice(a)opensuse.org Sent: Friday, June 20, 2008 10:35:19 AM GMT -08:00 US/Canada Pacific Subject: Re: [opensuse-buildservice] conditional tags in debian control file On Friday 20 June 2008 19:13:21 Mathieu OUDART wrote: > sure, I just though that OBS could have some extended syntax .. and I > haven't found any way to set soft dependencies in a control file. > > any thoughts on how to handle this issue ? Yes, I handle it in KDevelop For more info see: http://news.opensuse.org/2008/06/04/kdevelop-and-the-opensuse-build-service/ and: http://en.opensuse.org/Build_Service/Deb_builds Here you can see how I drive the build service to it's limit. So far I'm the only user that I know of that does this kind of stuff. https://build.opensuse.org/package/show?package=KDevelop3&project=home%3Aam… -- 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 --------------------------------------------------------------------- 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] OBS Version 0.9.1 Release
by aledr 21 Jun '08

21 Jun '08

Rubygem / rubygem-actionpack-2_0 missing "update_element_function"? ---------- Forwarded message ---------- From: aledr <matrixworkstation(a)gmail.com> Date: Fri, Jun 20, 2008 at 2:20 AM Subject: Re: [opensuse-buildservice] OBS Version 0.9.1 Release To: Adrian Schröter <adrian(a)suse.de> And this is what I still getting from my fresh install on openSuSE 11.0 and obs-* 0.9.99-3.2: ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ActionView::TemplateError (undefined method `update_element_function' for #<ActionView::Base:0x7f31ed37d4f0>) on line #4 of package/_update_build_log.rhtml: 1: <% if @finished %> 2: <%= update_element_function "status", :content => "Build finished" %> 3: <% else %> 4: <%= update_element_function "status", :content => "Updating..." %> 5: <%= update_element_function "log_space", :content => @log_chunk, :position => :bottom %> 6: <%= remote_function( 7: :url => {:action => :update_build_log, :package => @package, :project => @project, :arch => @arch, :repository => @repo, :offset => @offset}, app/views/package/_update_build_log.rhtml:4:in `_run_erb_47app47views47package47_update_build_log46rhtml' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_view/base.rb:637:in `send' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_view/base.rb:637:in `compile_and_render_template' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_view/base.rb:365:in `render_template' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_view/base.rb:316:in `render_file' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_view/base.rb:331:in `render' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_view/partials.rb:117:in `render_partial' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/benchmarking.rb:26:in `benchmark' /usr/lib64/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib64/ruby/1.8/benchmark.rb:307:in `realtime' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/benchmarking.rb:26:in `benchmark' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_view/partials.rb:116:in `render_partial' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:896:in `send!' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:896:in `render_with_no_layout' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/layout.rb:270:in `render_without_benchmark' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/benchmarking.rb:51:in `render' /usr/lib64/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/benchmarking.rb:51:in `render' app/controllers/package_controller.rb:557:in `update_build_log' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:1158:in `send' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:1158:in `perform_action_without_filters' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/filters.rb:697:in `call_filters' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/filters.rb:689:in `perform_action_without_benchmark' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib64/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/rescue.rb:199:in `perform_action' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:524:in `send' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:524:in `process_without_filters' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/filters.rb:685:in `process_without_session_management_support' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/session_management.rb:123:in `process' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:388:in `process' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/dispatcher.rb:171:in `handle_request' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/dispatcher.rb:115:in `dispatch' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/dispatcher.rb:126:in `dispatch_cgi' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/dispatcher.rb:9:in `dispatch' /usr/lib64/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:101:in `process_request' /usr/lib64/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:149:in `with_signal_handler' /usr/lib64/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:99:in `process_request' /usr/lib64/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:77:in `process_each_request' /usr/lib64/ruby/vendor_ruby/1.8/fcgi.rb:612:in `each_cgi' /usr/lib64/ruby/vendor_ruby/1.8/fcgi.rb:609:in `each' /usr/lib64/ruby/vendor_ruby/1.8/fcgi.rb:609:in `each_cgi' /usr/lib64/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:76:in `process_each_request' /usr/lib64/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:50:in `process!' /usr/lib64/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:24:in `process!' public/dispatch.fcgi:24 rescue_action_in_public: caught ActionView::TemplateError: undefined method `update_element_function' for #<ActionView::Base:0x7f31ed37d4f0> default exception handling ERROR: unknown injecting error instance variables into template object ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -- [ ]'s Aledr - Alexandre "OpenSource Solutions for SmallBusiness Problems" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 1

Re: [opensuse-buildservice] conditional tags in debian control file
by Mathieu OUDART 20 Jun '08

20 Jun '08

sure, I just though that OBS could have some extended syntax .. and I haven't found any way to set soft dependencies in a control file. any thoughts on how to handle this issue ? -- Mathieu OUDART ----- Original Message ----- From: "Carsten Hoeger" <choeger(a)open-xchange.com> To: opensuse-buildservice(a)opensuse.org Sent: Friday, June 20, 2008 12:22:05 AM GMT -08:00 US/Canada Pacific Subject: Re: [opensuse-buildservice] conditional tags in debian control file On Thu, Jun 19, Mathieu OUDART wrote: > I'm falling into an issue building my software for debian flavored > platforms. One dependency (libmono-i18n2.0-cil) appeared with Ubuntu 8.04. > Previously these libs were included in the libmono-corlib2.0-cil package. So > I would need to do something like : > > %if 0%{?ubuntu_version} < 8 > Depends: libmono-corlib2.0-cil > %else > Depends: libmono-corlib2.0-cil, libmono-i18n2.0-cil > %endif > > I use that kind of tags in my RPM spec file but would that also work for > Debian control files ? Thanks Not according to http://www.debian.org/doc/debian-policy/ch-controlfields.html -- With best regards, Carsten Hoeger --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

Re: [opensuse-buildservice] Fw: Error in Downloading Packages on an independent setup of Buildservice
by abhijit srivastav 20 Jun '08

20 Jun '08

Thanks Hoeger, That works for me but it means that my obs packages are not up to date. anyways how do you prefer to download your packages ? ----- Original Message ---- From: Carsten Hoeger <choeger(a)open-xchange.com> To: opensuse-buildservice(a)opensuse.org Sent: Friday, June 20, 2008 11:20:37 AM Subject: Re: [opensuse-buildservice] Fw: Error in Downloading Packages on an independent setup of Buildservice On Fri, Jun 20, Hoeger, Carsten wrote: > > 3) The download link to the created packages searches the package on the > > internet, i.e. official website of openSUSE > > ( https://api.opensuse.org/rpm/home:Admin/openSUSE_10.2/tina/i586/tina-3.7-8.… > > ) instead of the loopback address 127.0.42.1. It appears to have some > > configuration errors in the vhosts.d or lighttpd. > > You need to edit > > /srv/www/obs/webclient/app/helpers/package_helper.rb > > That's how I solved it. > > Find attached the version I use internally. Hm, well, now that I try it, that doesn't seem to work anymore since any of the last updates, but I do not use that way to download, anyway. -- With best regards, Carsten Hoeger --------------------------------------------------------------------- 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] Fw: Error in Downloading Packages on an independent setup of Buildservice
by abhijit srivastav 20 Jun '08

20 Jun '08

Goodmorning, I am a student and am working on my university project regarding the Build Service. My task is to install the obs packages and try to deliver a full working architecture of BuildService in our universities architecture. Presently I am testing it for the openSUSE 10.2 version and so followed the giudeline present on the net. I was able to install the obs packges and activate the distribution for openSUSE 10.2. I tried to create a package of a small software and want to discuss some of the test results. 1) The spec file creation does not work. The template file does not exist. 2) I have to login with the Admin rights, what I want to do is to create different users and allow them to connect to the buildservice and be able to package their softwares. These is no way to create any users. 3) The download link to the created packages searches the package on the internet, i.e. official website of openSUSE ( https://api.opensuse.org/rpm/home:Admin/openSUSE_10.2/tina/i586/tina-3.7-8.… ) instead of the loopback address 127.0.42.1. It appears to have some configuration errors in the vhosts.d or lighttpd. What we tried to achieve was to test the buildservice in the independent environment. Once installed it should work properly on the intranet without any references to the internet. I was hoping someone in the forum could help me. Regards Abhijit --------------------------------------------------------------------- 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] Fw: Error in Downloading Packages on an independent setup of Buildservice
by abhijit srivastav 20 Jun '08

20 Jun '08

Thanks Adrian for such a prompt reply. Regarding the spec file, it is good to know that we will have something new from you. Even I tried to create a simple spec file creator something like the KRPM Builder etc. Something like that will be a good option. For the admin console frontend, the users password cannot be changed as I didnt find any link to it. Moreover for a distributed environment it is important to change the password of the Admin. Lastly, the download option is a problem. For each file that we want to download it has the same problem. Regards, Abhijit ----- Original Message ---- From: Adrian Schröter <adrian(a)suse.de> To: opensuse-buildservice(a)opensuse.org Cc: abhijit srivastav <abhijit_s_cvs(a)yahoo.com> Sent: Friday, June 20, 2008 9:46:43 AM Subject: Re: [opensuse-buildservice] Fw: Error in Downloading Packages on an independent setup of Buildservice Hello, On Friday 20 June 2008 09:23:12 abhijit srivastav wrote: > I am a student and am working on my university project regarding the Build > Service. My task is to install the obs packages and try to deliver a full > working architecture of BuildService in our universities architecture. > Presently I am testing it for the openSUSE 10.2 version and so followed the > giudeline present on the net. I was able to install the obs packges and > activate the distribution for openSUSE 10.2. I tried to create a package of > a small software and want to discuss some of the test results. cool :) > 1) The spec file creation does not work. The template file does not exist. Hm, we removed the template in favor of the new wizard lately. How do you want to get the template ? > 2) I have to login with the Admin rights, what I want to do is to create > different users and allow them to connect to the buildservice and be able > to package their softwares. These is no way to create any users. There is, just connect with the web browser to the api (by default http://127.0.42.2) There is an admin interface to manage the users. > 3) The download link to the created packages searches the package on the > internet, i.e. official website of openSUSE > ( https://api.opensuse.org/rpm/home:Admin/openSUSE_10.2/tina/i586/tina-3.7- >8.1.i586.rpm ) instead of the loopback address 127.0.42.1. It appears to > have some configuration errors in the vhosts.d or lighttpd. > What we tried to achieve was to test the buildservice in the independent > environment. Once installed it should work properly on the intranet without > any references to the internet. > I was hoping someone in the forum could help me. hm, need to look at that .. bye adrian -- 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 --------------------------------------------------------------------- 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] conditional tags in debian control file
by Mathieu OUDART 20 Jun '08

20 Jun '08

Hi, I'm falling into an issue building my software for debian flavored platforms. One dependency (libmono-i18n2.0-cil) appeared with Ubuntu 8.04. Previously these libs were included in the libmono-corlib2.0-cil package. So I would need to do something like : %if 0%{?ubuntu_version} < 8 Depends: libmono-corlib2.0-cil %else Depends: libmono-corlib2.0-cil, libmono-i18n2.0-cil %endif I use that kind of tags in my RPM spec file but would that also work for Debian control files ? Thanks -- Mathieu OUDART - MindTouch --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1