- openSUSE Build Service

Re: [opensuse-buildservice] Java devel macros for all platforms??
by John Calcote 26 Apr '07

26 Apr '07

Excellent! Thanks - that get's me half way there. The remaining problem is what to put INSIDE the if clauses for Java packages on various platforms. John >>> On Thu, Apr 26, 2007 at 12:19 AM, in message <Pine.LNX.4.64.0704260812090.24504(a)mudge.stoecker.eu>, Dirk Stoecker <opensuse(a)dstoecker.de> wrote: On Wed, 25 Apr 2007, John Calcote wrote: > My project (openxdas) requires java - either 1.4.2 or 1.5 - but I'm > having a hard time trying to decide which macros to use that will expand > into something that works on every platform - I'd even be happy with an You mean this? http://en.opensuse.org/Build_Service/cross_distribution_package_how_to 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 --------------------------------------------------------------------- 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] OBS installation problem
by Leo Eraly 26 Apr '07

26 Apr '07

Hi, 1) I'm currently installing OBS on top of SLES10 for our internal development project. The installation went fine but the moment I try to add a repository to the the project and I select a distibution + release I get a Errorcode: uncaught_exception Message: unable to walk on path 'SUSE:SLE-10:SDK/standard' error message. This error is raised in /srv/www/obs/frontend/app/models/db_project.rb link_repo = Repository.find_by_project_and_repo_name( path.project, path.repository ) if link_repo.nil? raise RuntimeError, "unable to walk on path '#{path.project}/#{path.repository}'" THe find_by_project_and_repo_name function does an sql query on the repositories table which seems to contain information. What can cause this error? If I create a 'standard' repository like on the wiki suggested I don't get this error. 2) I'm following the instructions on http://en.opensuse.org/Build_Service/Build_Service_Installation_Tutorial/op… Near the bottom of the page there is a line which says to 'to copy the rpms from the base distribution to /srv/obs/build/openSUSE:10.2/standard/i586/:full/ ' Is there an easy way to copy all these rpms from the cdroms to this location? Or even from a http/ftp source? Thanks in advance, Kind regards Leo -- Leo Eraly <leo at unstable dot be> --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 6

[opensuse-buildservice] problem with macro stop_on_removal
by Axel Braun 26 Apr '07

26 Apr '07

Hi all, I'm currently trying to migrate the hylafax-spec file to the suse macros. I have a problem with the macro stop_on_removal in the %preun In case you want to uninstall the package, and the service is not running, the macro causes an error. The rpm remains in the database: z60m:/usr/src/packages/SPECS # rpm -e hylafax-5.1.2 hylafax 0:off 1:off 2:off 3:off 4:off 5:off 6:off FIFO: open: No such device or address error: %preun(hylafax-5.1.2-1suse102.i586) scriptlet failed, exit status 1 How can I resolve this? TIA Axel --------------------------------------------------------------------- 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] Java devel macros for all platforms??
by John Calcote 26 Apr '07

26 Apr '07

Congratulations on an excellent piece of work. My project was so simple to set up - I just copied my last successful (build.net) spec file into the project and the associated tar.bz2 file, and added the platforms I was interested in. The rest was automatic. But the least documented aspect (and thus the most difficult to get right) of the system is how to write the spec file so it works on all target platforms/systems/architectures. My project (openxdas) requires java - either 1.4.2 or 1.5 - but I'm having a hard time trying to decide which macros to use that will expand into something that works on every platform - I'd even be happy with an ifdef, if I could determine what to put inside of it. I understand that this issue is probably more related to Java than anything else. The interesting thing is that openxdas is mostly straight C - it has a server/daemon part (in C) with a client library (both in C and in Java). The Java client library is being compiled with gcj. The autotools scripts seem to work very well, but I can't find a combination of macros that will get my project to build on more than one or two systems. Any ideas where I might look for examples that work? John ----- John Calcote (jcalcote(a)novell.com) Sr. Software Engineer Novell, Inc. --------------------------------------------------------------------- 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] zope project
by Martin Kudlvasr 25 Apr '07

25 Apr '07

Hi, some time ago zope stopped working with recent python (2.5 currently) and is stuck with python-2.4 . If you want to know more about this problem, please read bug #221256 . To solve this, I've created zope packages that can live with python-2.5 installed. It'd be fine to have a project for them: python-2.4 - modified, so that it does not collide with python (currently 2.5) zope-python-2.4 - zope that explicitely uses python-2.4 zope3-python-2.4 - zope3 that explicitely uses python-2.4 I suggest a name "zope" for the project since this is purely zope issue. I don't know of any other python program which has stopped working on python-2.5. Thanks for your suggestions, Martin -- Best Regards, Martin Kudlvasr Zope Portal Developer --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: mkudlvasr(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 12

[opensuse-buildservice] serious architecture problems with python packages
by Mathias Homann 25 Apr '07

25 Apr '07

Hi, I'm trying to build a few python packages (http://build.opensuse.org/package/show?package=python-extattr&project=home%… for example), and they get build as noarch, but inside they are either x86_64 (python files in /usr/lib64) or i586 (python files in /usr/lib), depending on which packafe got built last. of course, that way they are not usable. How can i fix that, and have the packages built as their proper architecture instead of "noarch"? bye, MH --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] osc: handling of conflicts
by Christian Boltz 23 Apr '07

23 Apr '07

Hello, I have a question regarding conflict handling in osc. I have checked out kdepim3 from KDE:KDE3 some time ago and did some modifications in the spec file. Now I wanted to update to the latest version (osc up) and got a conflict notice for the specfile. Since I have saved my changes as patch, I simply deleted the specfile and called osc up again, hoping that it would download the specfile. Unfortunately, osc only prints "at revision 146", but does not download the missing file. osc stat still shows C kdepim3.spec How can I force osc to remove the conflicts flag and download the file? Sidenote for all who wonder what I'm doing: I have added a patch to KMail so that it displays several bugzilla headers in fancy view. If you are interested, you can find the packages and the patch in home:cboltz. Regards, Christian Boltz -- Herzlich willkommen, kann ich nur sagen. In der linken Ecke der Herausforderer Timo "Newbie" Nentwig, in der rechten Ecke der Weltmeister /usr/bin/"MailCruncher"/procmail, mit satten 70 Kilobyte Lebendgewicht klarer Favorit... Soll ich gongen? [Ratti in suse-linux] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 4

[opensuse-buildservice] Bash completion for osc
by Christian Boltz 23 Apr '07

23 Apr '07

Hello, I just thought that bash completion for osc would be a nice idea ;-) Basically the following works: complete -W "`osc help | sed -n '/^ *[a-z]*/ s/^ *$[a-z]*$.*$/\1/p'`" -f osc (to be put into a script in /etc/bash_completion.d/ or ~/.bashrc) Disadvantage: it needs some time at login because it always runs osc help. The better way is to run osc help only when needed - see /etc/bash_completion.d/yast2-completion.sh for a template. (Any volunteers? ;-) Regards, Christian Boltz -- Jedes meiner Postings ist alt genug, um für sich selbst zu sprechen. Ich übernehme keinerlei Verantwortung für das Verhalten meiner Mails. --------------------------------------------------------------------- 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 for the weekend
by Adrian Schröter 20 Apr '07

20 Apr '07

Hi, we fixed a number of bugs on the build hosts, unfortunately there is still one bug which let's the 64bit build hosts crash rather soon. Therefore all systems run 32bit OS only for the next two days. This means no 64bit builds will start. Additionally, we have reduced number of build hosts, because the systems can not access all their memory. Our kernel people do work on the remaining issue with high priority, so it get hopefully fixed quite soon. happy and sunny weekend 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] Perhaps noarch packages should not be built twice
by Truth 20 Apr '07

20 Apr '07

Hi all, I built a yast translation package on our build service and found that every noarch package is built twice under both arch categories- i586 and x86_64. So, 1st-born noarch packages would be overwriten by its later-born brother. So would corresponding src.rpms. The point is that those twin noarch packages are exactly the same- same name, same version, same release, same size, same content... Personally, I don't think it is necessary but a waste of building power. Can we fix that? Should I file a bug on the novell bugzilla, or it is just a necessary procedure? Regards, Thruth --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1