openSUSE Build Service February 2008

buildservice@lists.opensuse.org

57 participants
69 discussions

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

by Carsten Schoene

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

13 years

[opensuse-buildservice] DKIM-milter addon for postfix

by Guillermo Ballester Valor

Hi all, this is my first mail to this mail-list. Before try to reinvent the wheel, is there any project to build DKIM-milter rpm package for openSUSE which can be used by postfix?. I'm afraid I will need soon to implement DKIM in my postfix sever, and a rpm providing this would make my life easy. Till the moment I just tried to build, and to achieve it I've had to install sendmail-devel. Thanks, Guillermo -- Guillermo Ballester Valor gbv(a)oxixares.com http://www.oxixares.com/~gbv Ogijares, Granada - SPAIN --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

13 years, 3 months

[opensuse-buildservice] osc build

by Dirk Stoecker

On Wed, 30 Jan 2008, Marcus Rueckert wrote: > On 2008-01-30 08:46:56 +0100, Dirk Stoecker wrote: > > osc build does not clear the build-environment, when the plattform is > > changed. So when I switch from 10.2 to 10.3, some packager get deinstalled > > and installed and the result is a (usually not working) mixed setup. > > in the general section of ~/.oscrc add: > build-root: /srv/osc/build-root-%(repo)s > > then you get one build chroot per repository. > > build-root: /srv/osc/build-root-%(repo)s-%(arch)s > > is also possible. > > now you just have to watch the diskusage.:) Workarounds are a lot. But the problem is not fixed by these. Under special conditions this bug may cause hard to track build errors, thus I reported it. Saving a "This build environment is xxx"-file somewhere in the build-dir should fix the problem. 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

13 years, 4 months

[opensuse-buildservice] Re: [opensuse-project] How should we inform packagers about new upstreamversions?

by Vincent Untz

Le mercredi 27 février 2008 à 20:15 +0100, Pascal Bleser a écrit : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Christian Morales Vega wrote: > > Sometimes do you find packages in the OBS that are outdated. You never > > know why, perhaps the packager doesn't knows about the new upstream > > version and perhaps he knows but is just busy. > > Up to now when I found such a case I reported it like an "Enhancement" > > bug in bugzilla. But some packagers think bugzilla isn't the correct > > place for such a thing. > > > > If the packager doesn't knows about the new version he can leave the > > package outdated for a long time. So would be good that, at some time, > > if an user finds the problem he reports it. But, how should be > > reported? There is any feature planned in the OBS to help with this? > > What other distros do? > > A very good point. > > Personally, I think Bugzilla is the best place to report it. > It also makes it much easier to track the status. I think another approach would make sense: users could report it on software.opensuse.org since that's where they look for software. Then we just need a way to mail the relevant packagers about this "new upstream" report. 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

13 years, 4 months

[opensuse-buildservice] Expansion errors Fedora 6 and 8 x86_64

by Dirk Stoecker

Hello, I now have dozens of expansion errors for Fedora 6 and 8 architecture x86_64 which have not been there some time ago. What's wrong here? 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

13 years, 4 months

[opensuse-buildservice] Build Service Status Meeting

by Adrian Schröter

present: froh, mls, rlihm, adrian, poeml guest: msrex Status ====== froh: * need second repo for publishing svn trunk packages of OBS AI: adrian create one -> done (openSUSE:Tools:Unstable) mls: * fine tuning on scheduling algorithm, it shall look a bit more often for Factory related projects now. * Slow down is also caused by checking projects, even when projects did not change. Need to fix that. rlihm: * worked on improving UI for repo addition page for FOSDEM. adrian: * imageing scheduling does work now, working on worker code now. * Discussed a concept for openSUSE:Factory checkins (esp. discussing review states). Need to write it down and to follow up. poeml: * FOSDEM preparations * Wrote mirror setup how-to. We have currently the problem that the repositories/ tree is already too large for the mirrors. Thinking about a way to promote the more often downloaded repos. We need the download stats update again soon. AI: abauer look into the status of the current code, if we can activate it again. * We may should offer a rsync modul, what offers only the more often downloaded repos and update that one regulary. * We need more mirrors, which accepts the push mechanism (we have currently only 5). * ftp crashed multiple times, looks like a network card driver problem. Hardware is scheduled for exchange anyway. This week: * merge request handling until end of week. AI: abauer * Basic image building should work for internal usage. AI: adrian * Release updated packages of version 0.5 with critical bugfix to avoid unwanted repo removal. (AI: mls/froh) * Need to follow up LSB build target discussion. AI: adrian Discussion how to handle changed packages. * We want to encourage everybody to work on packages from openSUSE:Factory. -- 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

13 years, 4 months

[opensuse-buildservice] Some suggestions

by Vaibhav Kaushal

Hi list, I know that this might be like I am overlooking things but yes, I do respect the hard work the community has done to make such a great distro. But as always it has some imperfections which I think can be improved upon. I have my suggestions here which I think could be worked upon on, in the next version i.e. version 11.0 . I have not tested the alpha versions due to bandwidth constraints but I would still like to tell these: 1. The YaST must refresh the repositories only if new additions have been done to the repository. So you may maintain a LAST UPDATE DATE / TIME for each repository. That will seriously help us people with lower bandwidth. 2. I am a student and I see that most of my friends do not run the Linux system just because they think that it is too geeky to run that or that it is really difficult. I know the friendliness of the system is more than Windows, just that the rules are diff. But, I just wanted if there could be a new 'STUDENT EDITION" of the distro in its new avtars. The reason is: they want to use linux for the college classes and such stuff. So, instead of pushing in much applications, why don't you create a new edition of the Distro with the shell tools available ion that. Such as gcc, make, dos2unix etc are missing in the CD versions. So you can just put in more and more shell tools and reduce on some of the messengers, browsers and photo management things. Anyway those tools are not used much by the students new to Linux. So that could be packed into one edition called as *student edition*. 3. I am a programmer but am not good enough to contribute in a project as such and have no time to learn how to do that. However I would like to help the community. I am soon to have a website of my own. I wanted to ask if I can host some of the images of the distro which I like and think are good for the download. I wont be able to mirror the whole distro due to space and bandwidth bottlenecks. However I can have 2 CD images and 2 DVD images (I would like to choose which one I would like to keep on the server) and I would allow downloads from my website without being listed on the mirror page (that will help me keep my bandwidth usage in reason and limits of the hosting providers). Is that possible? 4. A lot of software in the main DVD is not really useful to many people. for example, not everybody is interested in learning how to be a CELL developer or such thing. Instead of that you could provide more usefull and demanded software like compiz-fusion and google earth? Those which are less used, can always be there in the online repos. 5. I know it is not really easy to do it. but can yast be like apt-get? Or at least you can improve upon 'smart' and add it in the default DVDs. I hope you would like to discuss about the proposals given. Thanks a lot. ------- Vaibhav Kaushal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

13 years, 5 months

[opensuse-buildservice] ANN: Yet Another Build Service Client

by James Oakley

I have written a build service client using PyQt4 and Osc. It's intended purpose is to report status information of projects and packages, and it is geared towards packagers who maintain more than a few packages. You can get RPMs via software.opensuse.org: http://software.opensuse.org/search?baseproject=openSUSE%3A10.3&p=1&q=yabsc Or you can download the source package from http://www.funktronics.ca/yabsc/ It's quite a bit rough around the edges. It currently shows results for one target of a project at a time and the osc calls block, which means that the whole interface pauses while waiting for API calls to complete. I have ideas for solving both of these issues, but I decided to just release it now, to get feedback from anybody who might find it useful. -- James Oakley jfunk(a)funktronics.ca --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

13 years, 5 months

[opensuse-buildservice] Expansion error on Mandriva_2007 x86_64 but not in i586

by G. Massera

Hello, I successufully building my project on Mandriva_2007 i586 (32bit)... but for 64bit the same spec file give me the following expansion error: "nothing provides libtermcap2, nothing provides librpm4.4, nothing provides libreadline5, nothing provides libpopt0, nothing provides libbzip2_1, nothing provides libsqlite3_0, nothing provides libneon0.26, nothing provides libopenssl0.9.8, nothing provides libelfutils1, nothing provides libbeecrypt6, nothing provides libkrb53, nothing provides libext2fs2, nothing provides libpcre0" I don't understand why... because all library specified above are not directly in my .spec file... and I suppose the system setup of i586 and x86_64 would be the same, isn't it ?? Thanks, Gianluca --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

13 years, 5 months

[opensuse-buildservice] BuildService search engines gets unusable

by Dirk Stoecker

Hello, with increasing number of packages, projects and texts, the search engine gets more and more unusable. For example to find an updated perl, I would enter perl in the search engine. The result is an Timeout error. Also searching for ocaml results in lots of entries. Some suggestions: - Better sorting: - First projects, which match the name exactly. - Second projects, which match name - Third projects, which have name in description. - Allow more control: - Sorting - Matching - Exclusions - ... (whatever) - Cache database/results --> There should be no timeout for "perl" at all. - Allow different display forms: - Only name - Name+short description - Full - Allow inclusion/exclusion of: - home projects - non-published projects - linked projects - linked projects, which have local changes / have no changes - aggregated projects 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

13 years, 5 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service February 2008