November 2007 - openSUSE Build Service

[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] Poor man's rpmlint integration
by Michal Marek 21 Jan '08

21 Jan '08

Hi, As you probably know, we use rpmlint internally in autobuild since some time. I wrote a hack to allow something similar in the buildservice (yes, I know that proper rpmlint integration is planned in the bs). Use <repository name="openSUSE_Factory"> <path repository="openSUSE_Factory" project="home:michal-m:rpmlint"/> <arch>i586</arch> <arch>x86_64</arch> </repository> in your project config to run rpmlint after each build. Unfortunately this only works for packages that have a %clean section and only for 10.3 and Factory builds. Also please note that the repositories can be broken at any time :) For example usage, see the home:michal-m:test project. have fun, Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 9

[opensuse-buildservice] Fedora8: have choice for text-www-browser needed by docbook-utils: lynx elinks w3m
by Ben Martin 11 Jan '08

11 Jan '08

As per http://en.opensuse.org/Build_Service/Tips_and_Tricks#Expansion_errors Perhaps using the default of lynx?

3 2

[opensuse-buildservice] patterns for speciffic build targets
by Michal Marek 17 Dec '07

17 Dec '07

Hi, Following http://en.opensuse.org/Build_Service_Tutorial#Create_Patterns , I'm trying to create some patterns (`osc meta -e mattern') for the server:php project. My goal is to - create a pattern, say PHP5, that installs php5 packages from the correstonding "base distro" repository, eg. when on 10.2, it would install from download.o.o/repositories/server:/php/openSUSE_10.2/ - create a pattern Apache2_and_PHP5, that installs php5 packages built against the Apache project, that is install from software.o.o/repositories/server:/php/server_apache_openSUSE_10.2/ _and_ from software.o.o/repositories/Apache/openSUSE_10.2/ - likewise for the server:database builds and the not yet present server:database + Apache combined builds My problem is that I don't know how to restrict a pattern to just some build targets. I created an Apache2_and_PHP5 pattern, but the resulting Apache2_and_PHP5.ymp files of course show up everywhere. I'd like to have different patterns with different descriptions for different build combinations. thanks, Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 6

[opensuse-buildservice] Ubuntu 7.10 ...
by Adrian Schröter 10 Dec '07

10 Dec '07

Hi there, there is now a Ubuntu:7.10 project. It is not mentioned on the web pages yet, since I consider the configuration for it still in BETA. But feel free to build against it using the web expert mask or osc and report success and failures :) Btw, this is our first .deb based distribution in the OBS, which also provides amd64/x86_64 packages :) 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

2 3

[opensuse-buildservice] temporarily disabling builds for selected architectures
by Petr Cerny 06 Dec '07

06 Dec '07

Is it possible to temporarily disable building for a specific architecture? Typical use would be in case when let's say 10.3 builds and older don't, so that after adding %if %suse_version stuff only affected versions (distros) trigger rebuild? Best regards Petr --------------------------------------------------------------------- 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] have choise for...
by Andrea Florio 05 Dec '07

05 Dec '07

hi! in home:anubisg1 i have a choice. is somebody able to fix it? thanks. have choice for qt = 4.1.0 needed by qt-devel: libqt4 qt, have choice for libQt3Support.so.4 needed by qt-devel: libqt4-qt3support qt-qt3support, have choice for libQtCore.so.4 needed by qt-devel: libqt4 qt, have choice for libQtGui.so.4 needed by qt-devel: libqt4-x11 qt-x11, have choice for libQtNetwork.so.4 needed by qt-devel: libqt4 qt, have choice for libQtSql.so.4 needed by qt-devel: qt-sql libqt4-sql, have choice for libQtXml.so.4 needed by qt-devel: libqt4 qt --------------------------------------------------------------------- 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] 2 different hylafax builds - only one shows up
by Axel Braun 03 Dec '07

03 Dec '07

Hi, in my home:DocB I have the builds for hylafax and hylafax+ When I want to install with 'one-click' the system just selects one of the packages. If I include the repository in YaST, only one of the two packages shows up. Is this a buildservice or more a YAST-issue? Thx Axel --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 5

[opensuse-buildservice] Kismet and aircrack-ng
by Eric M. Gearhart 03 Dec '07

03 Dec '07

For all you wireless auditing types, I have packaged up the latest stable Kismet (2007-10-R1) and Aircrack-ng (0.9.1) sources, for openSUSE 10.3 and SLE 10. http://download.opensuse.org/repositories/home:/ericgearhart:/Kismet http://download.opensuse.org/repositories/home:/ericgearhart:/aircrack-ng -- Eric http://nixwizard.net --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

7 11

[opensuse-buildservice] cross-compilation in OBS - analysis
by Stanislav Brabec 30 Nov '07

30 Nov '07

Hallo. I just tried to analyze the cost of the cross-compilation support in OpenSUSE BS. This long mail attempts to describe steps to this goal: Numbers mean steps needed for solution. Letters mean alternative solutions. + means (probably) mandatory step to make initial support +1. Provide cross compilation tools. 2. Prepare build environment. +2.1 Prepare host environment. 2.1.1 RPM level problems. 2.2 Prepare target environment. +2.2a sysroot 2.2b target root map 2.2a.1 RPM level problems. +2.2a.1a Use rpm --noscripts. 2.2a.1b Use virtual host for installation. 3. Compilation problems. 3a Native compilation in the virtual build host +3b Cross-compilation +3b.1 Bootstrapping 3b.2 QA +3b.3 Provide cache +3b.4 RPM level problems +3b.5 Fix packages 3b.6 Fix autotools 4. Fix remaining problem Details: 1. Provide cross compilation tools. Thanks top huge amount of work on gcc, it's trivial. Setting additional configure switches to gcc and binutils will provide needed support for as many targets as we want. 2. Prepare build environment. 2.1 Prepare host environment. Trivial. Build environment consists from the compilation environment, typically including cross-compiler, cross-binutils, language tools (bison, flex,...), documentation processing tools etc. 2.1.1 RPM level problems: I am not sure, whether RPM discriminates between Build Target Requires and Build Host Requires. If not, then we should provide sufficient host environment for all packages. 2.2 Prepare target environment. There are two approaches to prepare target environment: 2.2a sysroot The whole target system image resides in one sub-directory. Pros: Easy to create using existing tools. Some tools already have support for it (gcc, binutils). sysroot can be used by virtual hosts and emulators directly. Cons: If you want to build more targets at once, it is a waste of resources. 2.2b target root map Target root map splits target build system to more sub-directories - one contains architecture independent packages, another contains architecture dependent packages, and others can contain target system or even device specific. AFAIK, target root map is currently used only by OpenEmbedded projects. Pros: Easy to build for many targets at one recycling most of files. Cons: Set-up needs special tools, no chance to use existing tools. Needs special tools to operate with compiler and linker paths. I can imagine, that 2.2a would be much easier to create using existing tools for creating chroot. 2.2a.1 RPM level problems: RPM has no support for discriminating between scriptlets usable in a cross-platform way (and using relative paths) and scriptlets creating platform specific data. There is also no discrimination between scriptlets required to use this package for compilation and to use this package for runtime. There are only two obvious work-arounds: 2.2a.1a Use rpm --noscripts. Nobody knows, what will happen, but one could expect, that the package will be still usable for compilation. It is obvious, that the target sysroot will not be usable by emulators directly. 2.2a.1b Use virtual host for installation. You will get a perfect image of the target system, but it is expected to be much slower. Obviously 2.2a.1a is the only acceptable solution. Other (minor) problems would require fixes to discriminate between CFLAGS (for target) and HOST_CFLAGS (for build host). 3. Compilation problems Nowadays, in the age of autotools, simple changing of paths to basic tools (CC, LD,...) works surprisingly well. But well, there are still two ways to compile packages: 3a Native compilation in the virtual build host If you have a running virtual host, it is a very simple way, which makes no cross-compilation problems. On the other hand, it has a very poor performance. 3b Cross-compilation Cross compilation provides a full performance compilation, but needs a support from each part of the toolchain, which may bring some problems. But as we can see, there are several toolchains providing complete or nearly complete build using only cross-compilation: http://www.openembedded.org/ https://dev.openwrt.org/ 3b.1 Bootstrapping Bootstrapping would require initial steps to provide initial base system. It is a bit specific - to compile glibc, you don't need target compiler. But this step needs rpm level solution to ignore selected BuildRequires. 3b.2 QA It works well, but not perfectly. Many checks provide bad values and running QA checks rejecting traces of sysroot paths in the result seems to be mandatory. 3b.3 Provide cache values configure provide an option to use cached values. This feature (with required infrastructure to share these caches) allows to run complicated autoconf checks once on the target system and recycle cache variables for cross-compilation builds. Autotools provide support for system-wide check cache. 3b.4 RPM level problems Cross compilation would require changes in particular RPM scripts. For example AutoReqProv may need to be changed. 3b.5 Fix packages Particular packages may not support cross compilation well. The main reasons are: - Missing AC_CACHE_VAL wrapper disables to provide correct check result. - Poorly written check. - Attempt to use target binary in the host system without defining it. - (Not autotools) toolchain is not ready for cross compilation 3b.6 Fix autotools Autotools has a nice cross compilation support yet. Most checks are written in a very pure way and work well for cross compilation. But autotools has no support for sysroot and checks, which could benefit from it does not yet work. For example AC_CHECK_FILE could work well with sysroot support. 4. Fix remaining problem Here we have to provide solution for remaining problems, which cannot be provided by a cross compiler. It might include special actions like providing initial values of system caches, locales etc. It might or might not be critical for packaging itself. Having a working virtual build host would be a generic solution for all remaining problems. -- 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 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

6 15