>>> Reply on 22-11-2006 12:08:02 <<<
> Hi,
>
> I*ve the package R-base successfully built in home:dsteuer.
> Now I want to add a project named "littler", which has
BuildRequires:
> R-base.
> R-base naturally is not in any of the repositories I want to build
> littler for.
>
> How can I do that? Is it possible? I guess yes, but I can*t figure
it
> out.
>
The two pakcages have to be in the same project, and then you can
easily give BuildRequires: r-base to the 2nd package.
While r-type is not ready, you should see status 'blocked' on the other
package.
I have the same with some games, depending on SDL_net, that needed a
fix and another depended on cmake in a newer version (that is now
luckily gone).
Dominique
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
i packed zhu3d - which is viewer of mathematical functions.
See: http://kde-apps.org/content/show.php?content=43071
I have package in my home directory
home:pnemec
for SL10.0 10.1 and factory
I`d like to move it to
science
zhu3d need qt4 (libqt4 - KDE:Qt)
I am not sure how to add resources only for one package if this is possible?
Please add me as maintainer to science project if you want me add zhu3d to it.
Thanks
Pavel
--
Pavel Nemec
Software Engineer
https://wiki.innerweb.novell.com/index.php/SLEPOS
---------------------------------------------------------------------
SuSE CR, s.r.o. e-mail: pnemec(a)suse.cz
Lihovarska 1060/12 tel:+420 2 9654 2373
190 00 Praha 9 fax:+420 2 9654 2374
Ceska republika http://www.suse.cz
Hi and hopefully I want anger too many people with my question.
I am trying to build Hula, and so far I am only able to build for SUSE 10.1 i586. x86_64 is failing due to a missing entry in %files, which I am aware of. My question is this: How do I specify the requirement in %files for x86_64 so that I can build both i586 and x86_64 architectures from the same spec file.
Many thanks,
Andy
--
Andrew Wafaa, RHCT
Tel: +44 (0)7974 074546
e-Mail: andrew(a)forcev.net
http://www.forcev.net
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Thanks to Michael and Daniel, I am now able to build on x86_64 but this has now thrown up an issue. I am now getting the following error from the build service which is what I get on my own box:
configure: error: Dragonfly requires python-devel, or python built with shared library support (--enable-shared)
I have specified python-devel already, so what else do I need to do? Prior to changing my spec to show the different architecture %files I didn't get this error.
Regards,
Andy
--
Andrew Wafaa
Tel: +44 (0)7974 074546
e-Mail: andrew(a)forcev.net
http://www.forcev.net
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
I have strange problem with my package Reveal (home:pnemec Reveal)
package use qmake to build himself and it compile libraries together in
install phase !!!
In local build (osc build) everything is ok.
But in build service it faild with this message:
+ make install
g++ -o /var/tmp/reveal-1.2.-build/usr/bin/Reveal tmp/config.o tmp/reveal.o
...
[snip]
....
-lpthread
mkdir: cannot create directory `/usr/share/Reveal/': Permission denied
make: *** [install_credits] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.25280 (%install)
As i stated in local build everything is writed and installed into right
directory under /var/tmp/reveal-1.2.-build/
why not in build in BS ???
Pavel
--
Pavel Nemec
Software Engineer
https://wiki.innerweb.novell.com/index.php/SLEPOS
---------------------------------------------------------------------
SuSE CR, s.r.o. e-mail: pnemec(a)suse.cz
Lihovarska 1060/12 tel:+420 2 9654 2373
190 00 Praha 9 fax:+420 2 9654 2374
Ceska republika http://www.suse.cz
Hi,
how are projects and packages structured?
is it a fixed "one name for the project and then one for the package"
system, or are further subdirs possible?
I wonder about this: recent discussions with rpm experts have shown me
that merging several spec files into one only creates a horrible
maintainence hell. also they have compelling arguments, that one rpm for
all distributions was something they tried for years with lots of work,
and it never worked well.
so I see as best solution to have codenames (e.g. fc3,fc4,fc5, sles9,
sles10, oss10.0, dapper, edgy, etch, sarge, ...) and for each
distribution *.spec.$codename or *.diff.gz.$codename. but this would
require work on the build system side, and I get the impression noone
wants that.
the alternative from my side would be per distro packages.
e.g. instead of "openct" I could have packages "openct.fc" and
"openct.os" and "openct.sles" and "openct.sarge" and so on,
upload spec files for each. this wouldn't require changes in the code
base, and give me the flexibility I need, so I can simply build new
packages for my open source projects, with minimal changes to the last
spec file the distribution provides.
but that way the list of packages might grow very long. is it possible
to structure projects/packages a different way (i.e. path mechanism,
no flat one project, one package subdir structure)?
Regards, Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
It seems there is sort of a translation table to replace the
BuildRequires from openSUSE to Mandriva.
At least, when entering BuildRequires, many -mdk.rpms get installed
with similiar names, but not exactly what I typed (or the get stripped
off)
An example for the latter case:
I have a .spec file with BuildRequires: libvorbis-devel
This one does not get a failure in Mandriva_2006 build (so probably got
stripped out). Unfortunately, it did not get replaced with
libvorbis0-devel (the Mandriva name of the lib)
Is this translation table visible? Can there work be done on it?
And another thing: How could I get support for Mandriva 2007 inside the
BS? Is this somehow possible? Planned for the future?
Regards,
Dominique
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Dne Monday 20 November 2006 08:57 jste napsal(a):
> Dne Monday 20 November 2006 04:09 John Meyer napsal(a):
> > I'd like to know what you guys favorite e-mail client is. I've tried
I think this is very interesting topic. I create wiki page, feel free to add
your remakrs.
http://en.opensuse.org/Mail
Pavel
--
Pavel Nemec
Software Engineer
https://wiki.innerweb.novell.com/index.php/SLEPOS
---------------------------------------------------------------------
SuSE CR, s.r.o. e-mail: pnemec(a)suse.cz
Lihovarska 1060/12 tel:+420 2 9654 2373
190 00 Praha 9 fax:+420 2 9654 2374
Ceska republika http://www.suse.cz
Hi Guys
The i586 buildhosts still appear to be passed out from a weekend of partying..
(The passed out sometime Saturday evening as far as I can tell)
Any chance of kicking them awake and giving them an asprin?
Cheers
--
Peter Nixon
http://www.peternixon.net/
PGP Key: http://www.peternixon.net/public.asc
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
>>> Reply on 17-11-2006 17:13:04 <<<
> On 11/17/06, Dominique Leuenberger
<Dominique.Leuenberger(a)tmf-group.com>
> wrote:
>
> > something like
> >
> > %if %suse
> > BuildRequires: alsa-devel
> > %else if %mandriva
> > buildRequires: libalsa-devel
> > %endif
> >
>
> We are using the following in our repository, you can check those
specs
> out.
>
> %if "%_repository" == "SUSE_Linux_10.1" || "%_repository" ==
"SLE_10"
> BuildRequires: xorg-x11-compat70-devel
> %endif
> %if "%_repository" != "SUSE_Linux_10.0"
> BuildRequires: libdrm-devel
> %endif
>
> http://build.opensuse.org/project/show?project=X11%3AXGL
>
> Cheers
>
Thank you very much... I'll have a look into this.
Are the set variables somewhere documented or are they just a good
guess? (ok: _repository IS guessable)
Dominiue
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org