-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've got a package that uses some java in the build process (openxdas).
Java is optional, and if javac (gcj -C), jar or javadoc utilities are
not found, then the java build is skipped. I'm currently using gcc-java
in BuildRequires. That get's me gcj -C in my JAVA env var, but I don't
know what to use that gets me corresponding jar and javadoc utilities.
Recently, I've discovered the java-1_5_0-gcj-compat-devel package, and
added it to my BuildRequires line. That get's me there for opensuse
platforms, but it apparently doesn't exist on any others.
Isn't there an all-in-one solution for Java?
Thanks,
John
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAkh7gjIACgkQdcgqmRY/OH/oOQCfbITbqdV3/h4RrcTL3MxR2lfY
5g4AnifeoXZKwm6BLLEG6PSdvBIP28gG
=Q2N9
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Can anyone tell me what the compatible package is for libexpat-devel on
CentOS 5 and Fedora 8? I'm getting expansion errors on this package for
these platforms. Also, since I probably have to use a conditional for
these packages on these platforms, can someone tell me how to tell them
from the others in my spec file?
Thanks,
John
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAkh7gO4ACgkQdcgqmRY/OH/KpQCfa3I9x2D9A2xYe3feeiwAHWlH
Hd0Aniv43834GxYwWai+sikqiYyz12mh
=lmyk
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
after a lot of inspiring conversations with co-workers at SUSE and
friends from the open source community I finally published a first
abstract draft how we could add some metrics to openSUSE build service
to create a trust system.
http://en.opensuse.org/Build_Service/Concepts/Trust
This article does not go much into particular neither explains concrete
implementation details. Main target of this proposal is to have a basis
for discussion. The article even goes beyond the focus on trust and
proposes some additional metrics to support openSUSE users in their
decision from which repositories they should obtain their software packages.
Within the next weeks I would like to discuss this with you. So if you
are interested in this topic please contact me. Any suggestions,
feedback or critics are highly appreciated.
Cheers!
Marko
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi all,
I'm still pretty new to the build service, so I was looking around the
wiki documentation for some kind of best practice on managing source
code - it's not a problem yet as noone is using my package, but I'm
trying to find out now how to deal with stable versus unstable somewhere
down the line - so if I have version 1.3 as a stable version, and then
working on 1.4 which may or may not build.. Should I only do local
builds of the 1.4 until it's released, then upload to the build service?
I'm also trying to figure out how to deal with a source code repository
- currently I have a shell script which tars up my source directory and
then commits it through osc, but I found this page on the wiki:
http://en.opensuse.org/Build_Service/Workflows
under "Edit Packages" near the bottom, it says
add sources (http source, svn/cvs source)
Does this mean I can get the build service to grab the source straight
from my svn server?
Cheers,
KEv.
--
Kevin James
Applied Technology Senior Strategist
Novell Global Enablement
------------------------
Novell, Inc.
http://www.novell.com
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello,
could the webinterface please be fixed, so this warning comes no longer
when repositories have been removed.
Every year the webinterface gets unusable to change configuration, because
a repository has been removed.
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
Hi Group,
Using the OBS web client, when I try to: Add Repository>> Mandriva 2006
I get the following error:
Error Details:
Errorcode: package_save_error
Message: error saving project: unable to walk on path 'Mandriva:2006/standard'
Should I report this sort fo error via bugzilla or is this list OK?
Regards
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I know it's friday evening...but could someone add the opensuse11
repository to the project filesystems ?
I've been already personally asked by mail where the openafs-client for
the new version is ;-)
Cheers,
Christof
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi Group,
I raised this on the IRC channel so apologies if you've seen this.
I have a project's src.rpm that I'd like to move onto the OBS, and
this has raised some issues....
The current src.rpm uses lots of --build "option n" switches. Some of
these are accommodated by OBS since they are distro specific builds.
Others however relate to building different components.
My Question is how to 'map' this to OBS?
Do I setup one package per 'component', and so have many duplicates of
the src.spec file?
Or, is it possible for several projects to share a common spec file
and build specific components by passing in some parameters?
Appreciate any suggestions or better yet if you can point to a project
that uses such a 'shared-spec' setup :)
Regards
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hallo list,
several weeks ago, I had problems getting a package built because
rpmlint crashed. I asked for that on IRC and was told that it was a
bug that the team was working on.
I just tried again and noticed that the build still fails at the same
point, rendering me unable to get the package compiled. On IRC, I was
told that the rpmlint bug was fixed some time ago.
The project in question is pidgin-lastfm in Home::Natureshadow (linked
in GNOME::Community).
Any ideas?
Regards,
Nik
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
could we stop moaning about old %suse_version checks as long as SLES9 is
still supported? Please stop the warnings for stuff down to 910 since
I'm not going to rewrite my working specfiles just for SLES9.
Wolfgang
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org