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 28 Jun '08

28 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