openSUSE Build Service March 2009

buildservice@lists.opensuse.org

62 participants
69 discussions

[opensuse-buildservice] rpmlint and "Packager"

by Dirk Stöcker

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

11 years, 6 months

Re: [opensuse-buildservice] [PATCH] osc: add -c flag to check package out to current diretory

by Peter Poeml

On Wed, Mar 25, 2009 at 01:38:42PM -0700, Brandon Philips wrote: > Any thoughts on why we don't move to git? If a community member wanted > to interact it seems like giving them SVN access would be a bottle neck. > > Just a thought. I don't really understand how a switch to git (which would cost us quite some effort I assume) would enable you to get changes into mainline easier. How would that work, or avoid human bottlenecks? Peter -- Contact: admin(a)opensuse.org (a.k.a. ftpadmin(a)suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development

11 years, 7 months

[opensuse-buildservice] Where can I find the keys for a project?

by Andreas Vetter

Hi, my name is Andreas Vetter. I'm administrating SUSE Linux systems for more than 10 years now - at that time there were still the dots in S.u.S.E. ;-). I'm not a programmer, but have the need to package 3rd party software or dropped packages from time to time. I have a (sub-)project home:asvetter:Shibboleth2:ServiceProvider with several packages. When I try to build a package that depends on another package from that project, I get the following: The following package could not be verified: /var/tmp/osbuild-packagecache/home:asvetter:Shibboleth2:ServiceProvider/openSUSE_11.1/x86_64/liblog4shib-devel-1.0.1-17.1.x86_64.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#678f1fc6) - If the key is missing, install it first. For example, do the following: gpg --keyserver pgp.mit.edu --recv-keys 678f1fc6 gpg --armor --export 678f1fc6 > /home/vetter/keyfile-678f1fc6 and, as root: rpm --import /home/vetter/keyfile-678f1fc6 Then, just start the build again. - If the key is unavailable, you may use --no-verify (which may pose a risk). vetter:~/home:asvetter:Shibboleth2:ServiceProvider/xmltooling> gpg --keyserver pgp.mit.edu --recv-keys 678f1fc6 gpg: requesting key 678F1FC6 from hkp server pgp.mit.edu gpgkeys: key 678F1FC6 not found on keyserver gpg: no valid OpenPGP data found. gpg: Total number processed: 0 My questions: 1. Is the 678f1fc6 created by OBS? 2. Is it my responsibility to create a key for my OBS account? How? 3. Is it my responsibility to publish the key? 4. Is it just the wrong key server? TIA, Andreas -- Mit freundlichen Gruessen, Andreas Vetter Informations- und Kommunikationstechnik Fakultaet fuer Physik und Astronomie Universitaet Wuerzburg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years, 7 months

[opensuse-buildservice] How to build deb packages

by Richard Bos

Hi, I have successfully build packages for my project "inkomstenbelasting" for openSUSE, fedora, mandrake and centos. I now would like to extent this to the debian based distributions. I would like to know how this should be done. I have read the wiki page http://en.opensuse.org/Build_Service/Deb_builds, but after reading it, it was still not clear :( Neither does the email that the wiki page refers to (http://lists.opensuse.org/opensuse- buildservice/2007-03/msg00067.html) make things clearer, perhaps the contrary :( The rpm that I would like to debianize is this one: http://download.opensuse.org/repositories/home:/rbos:/ib/openSUSE_11.1/repo… It seems like a simply package and it consist of only a few files: # rpm -ql inkomstenbelasting /usr/share/belastingdienst.nl /usr/share/doc/packages/inkomstenbelasting /usr/share/doc/packages/inkomstenbelasting/Aandachtspunten /usr/share/doc/packages/inkomstenbelasting/README /usr/share/doc/packages/inkomstenbelasting/TODO /usr/share/icons/hicolor/16x16/apps/inkomstenbelasting.png .... /usr/share/icons/hicolor/128x128/apps/inkomstenbelasting.png There is no debian package for it. The build server work directory holds the following files: inkomstenbelasting-2008.tar.bz2 inkomstenbelasting.changes inkomstenbelasting.spec The changes file is in the spec file format. What do I need to add to the spec file? Should I use the DebTransformTar tag to refer to inkomstenbelasting-2008.tar.bz2 file? Is there a .dsc file required or is this created from the spec file by the build service? What to do with the changes files, must it be renamed to e.g debian.changes, must the format be adjusted or will this be taken care of by the build service? Looking forward to your advice. -- Richard -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years, 8 months

[opensuse-buildservice] Building python packages on OBS

by Axel Braun

Hi, I'm trying to build a package for tryton on the OBS buildservice using the web interface. I get a couple of expansion errors, e.g. for python-psycopg2 python-egenix-mx-base python-dot These packages are all available under http://download.opensuse.org/repositories/devel:/languages:/python/openSUSE… for a normal openSUSE environment. How can I include them in the build environment? More, some additional packages are missing, that are grabbed by easy_install, but are not in the current repositories: relatorio (http://relatorio.openhex.org/) pywebdav (http://sourceforge.net/projects/pywebdav/) pytz (http://pytz.sourceforge.net/) openoffice.interact (http://pypi.python.org/pypi/openoffice.interact/) sphinx (http://sphinx.pocoo.org/) How can I get this software in? Yes, I read the documents, but..... Thanks Axel -- OS: openSUSE 11.1 (i586) Kernel: 2.6.27.19-20090309_908fc8df-default KDE: 3.5.10 "release 21.9" -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years, 8 months

[opensuse-buildservice] Build Team Meeting

by Michael Schroeder

TOPs ---- - status - password-less read-only access Status ------ mls - management offsite: held build service talk - multiple improvement in source server's link handling ("keeplink" mode) abauer - worked on new web UI implementation, created library for API access rlihm - worked on new web UI design - playing with ideas about displaying information in a more terse way freitag - management offsite: held fate & opensuse ecosystem talks - thinking about new portal page providing an uniform access to all opensuse services froh - management offsite: held driver build talk - finished driver build project form poeml - visited the nuernberg office huewe - osc cpio optimization - tracking down XEN problem @ ARM inside XEN worker image moeller - fix remaining Base:build @ ARM package errors (84 pkgs bootstrapped) - build "accelerators" for ARM (package that do not get emulated with QEMU) mohring - tested "accelerator" packages - fixed ARM expansion error on build.o.o => osc local build works now for Fedora:10 @ ARM - supported build of new XEN worker images on build.o.o with new qemu - tracked down boot error of new XEN worker images on build.o.o @ ARM - supported import of Maemo port for non N810 devices called "Project Mer" - packaged and tested openSUSE:Tools:Devel/obs-all-svn & qemu-svn cross-build summary - for openSUSE @ ARM, now only a natively build cross compiler and a working linux kernel is missing, then we have working Base:build like x86 - OBS @ ARM works, but currently not with the XEN workers (worker bootstrap problem) Password-less read-only access ------------------------------ discussed if we should drop password enforcement for read-only mode advantages: - people can have a look at build service features, download sources - search engines will index the build service disadvantage: - one week work for abauer We'll probably do it unless some valid reasons come up against it. Need some more input from build service community. 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

11 years, 8 months

Re: [opensuse-buildservice] problem after upgrading to 1.5 (and 1.5.1)

by Srinidhi B

Hi, On Tue, 2009-03-24 at 10:46 -0500, Jon Nelson wrote: > the db:migrate step fails: > > > obs1:/srv/www/obs/frontend # RAILS_ENV="production_slave" rake db:migrate > (in /srv/www/obs/frontend) > rake aborted! > Multiple migrations have the name AddArchs > > (See full trace by running task with --trace) > obs1:/srv/www/obs/frontend # > Had reported it sometime back. This was already fixed: https://bugzilla.novell.com/show_bug.cgi?id=463172 I think the fix wasn't ported to 1.5 branch. HTH, Srinidhi. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years, 8 months

[opensuse-buildservice] Build hanging forever when worker dies/is shut down during build

by Carsten Hoeger

Hi, is there a way to prevent obs builds to hang forever in case of a failing or stopped worker that is currently building? The only way I found is to cd to /srv/obs/jobs/XXX and remove the job file. Is there a timeout or something similar which can be set? -- With best regards, Carsten Hoeger

11 years, 8 months

[opensuse-buildservice] not an osc working copy

by Greg Freemyer

All, I'm a newbie trying to follow the tutorial. http://en.opensuse.org/Build_Service_Tutorial#Step_Two_-_Create_.26_Upload_… I created my package via "osc meta pkg -e home:gregfreemyer open2300" And I can see the package at the website. I then try the next command "osc up" and I get the not a working copy error. > osc up Error: "/home/gaf/weather-station/src/open2300" is not an osc working copy. I get the same thing if I assume that worked and try to upload some files: > osc add *.c Error: "/home/gaf/weather-station/src/open2300" is not an osc working copy. Not surprisingly, the same for :osc commit" > osc commit Error: "/home/gaf/weather-station/src/open2300" is not an osc working copy. What step am I missing? Thanks Greg -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years, 8 months

[opensuse-buildservice] Error on server:eGroupware build for openSUSE11.1

by Ralf Becker

When I try to build the noarch rpm for openSUSE11.1, I get the following error, stoping the build: + /usr/lib/rpm/brp-rpath + /usr/lib/rpm/brp-pie + /usr/lib/rpm/brp-rootfs + /usr/lib/rpm/brp-tcl + /usr/lib/rpm/brp-check-python + /usr/lib/rpm/brp-check-bytecode-version ERROR: jar, fastjar, or unzip is not installed (trying file /tmp/eGroupware-buildroot/usr/share/egroupware/gallery/gallery2/modules/core/classes/GalleryStorage/g2_db2.jar) error: Bad exit status from /var/tmp/rpm-tmp.54764 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.54764 (%install) System halted. The same specfile works with a openSUSE11.0 target. The project is PHP based. The bundeled Gallery2 contains the jar-file causing the error. That jar is used on clientside, so I dont think it makes sense to require any java rpms for the server. Any ideas ... Ralf -- Ralf Becker Outdoor Unlimited Training GmbH [www.outdoor-training.de] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 (0)631 31657-0 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years, 8 months

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service March 2009