hi,
i look for a project for aqsis atm. aqsis is a renderman compliant
renderer. i think yafray and blender could live in the same project.
(cc'ed maintainers)
now the question is: how to name the new child.
"graphics:3d" sounds reasonable. any objections? we have this
multimedia:photo atm ... which could be moved to graphics:pixel or
graphics:photo ...
i would like to create the project this evening. so ... complain early.
:) sorry for the late mail about it ...
darix
--
openSUSE - SUSE Linux is my linux
openSUSE is good for you
www.opensuse.org
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi buildservice users,
I managed to break the build process for an hour. If you see
"build did not create a logfile" errors, please retrigger the
builds.
There actually is a self-test to catch such errors, but the test
did not check the helper program used. (The plan is to get rid of
the helper anyway...)
Sorry,
Michael.
--
Michael Schroeder mls(a)suse.de
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
Hey guys,
could one of the admins clear home:jasujt
I was experimenting and need to start over
James
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Dear BS Maintainers,
I just saw that now, in the WebGui of BS, it's possible to enable /
disable the targets to build against!
Thank you very much for this new feature in the webgui!
Dominique
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
There's a small problem with the linear algebra library BLAS and LAPACK in
opensuse. These are Fortran libraries. I (and others) have trouble using
the libraries with SciPy (python scientific computing package). The problem
seems to be that different Fortran compilers use different symbol names for
some output routines. When one compiles scipy, there are some Fortran
routines that get compiled, I think with g77 by default (maybe not). You
can compile and install scipy, but when you try importing it in python you
get an error of undefined symbol _gfortran_st_write in the LAPACK library.
I have the most recent blas and lapack opensuse builds (940). The official
suse-type webpage I got these from say they were compiled with egcs, which
is a. wrong (egcs merged back into gcc a long time ago) and b. ill-defined
(since g77 and gfortran are both part of gcc).
As you search the web, you see that it's part of the lore that "Suse's BLAS
is buggy, you have to compile yourself." Not good for Suse!
While I'm on it, it's not clear what implementation of BLAS opensuse uses.
My guess is it's the reference implementation from lapack's page on netlib,
which is not optimized. Better ones exist, like gotoBLAS. Maybe that can
be made a suse package?
At the least it would help if it were spelled out exactly which Fortran
compiler was used to make opensuse's blas. If they can be compiled to allow
multiple Fortran compilers to play nicely with them, even better.
Cheers,
David
Hey guys,
I have begun reading the build-service tutorial and feel I should take a
moment to get on track with "Good Form". so let me introduce myself.
I am James Tremblay , I work as the District Technology Director for the
Newmarket NH School District. I have been installing Novell Networks for
13 years. I started by getting a Certificate in Networking form our
local Voc-ED college with a primary focus on Netware CNE training.
My experience with Linux is shallow, I basically looked up SUSE when
Novell announced it's acquisition of it and downloaded 8.? I didn't
really start working on more than getting familiar with user space until
9.1 and NLD9. I am good with Novell's command-line architecture and I
hope that it will translate quickly to Linux.
I use the nick "fxrsliberty" because that is the kind of Harley-Davidson
I ride and it helps remind me of good times.
James
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
I get this output, after starting the build for wireshark:
Putting files in AC_CONFIG_AUX_DIR, `..'.
Error: can't
get 'https://api.opensuse.org/result/home:rbos/SL-10.0_i586/wireshark/i586/log?n…'
HTTP Error 500: Internal Server Error
Debugging output follows.
url:
https://api.opensuse.org/result/home:rbos/SL-10.0_i586/wireshark/i586/log?n…
response:
[left out the debug output]
And this for 10.1
Requires: wireshark = 0.99.4
Obsoletes: ethereal-devel
Checking for unpackaged
file(s): /usr/lib/rpm/check-files /var/tmp/wireshark-0.99.4-build
warning: Could not canonicalize hostname: build08
Wrote: /usr/src/packages/SRPMS/wireshark-0.99.4-7.1.src.rpm
Wrote: /usr/src/packages/RPMS/x86_64/wireshark-0.99.4-7.1.x86_64.rpm
Error: can't
get 'https://api.opensuse.org/result/home:rbos/SL-10.1_x86_64/wireshark/x86_64/l…'
HTTP Error 500: Internal Server Error
[left out the debug output]
# osc results
wireshark> osc results
SL-10.0_i586 i586 failed:
https://api.opensuse.org/result/home:rbos/SL-10.0_i586/wireshark/i586/log
SL-10.0_x86_64 x86_64 failed:
https://api.opensuse.org/result/home:rbos/SL-10.0_x86_64/wireshark/x86_64/l…
SL-10.1_i586 i586 succeeded
SL-10.1_x86_64 x86_64 building
SL-9.3_i586 i586 disabled
SL-9.3_x86_64 x86_64 disabled
SLES_9 x86_64 disabled
SLES_9 i586 disabled
SLE_10 x86_64 expansion error: nothing provides libadns-devel
SLE_10 i586 expansion error: nothing provides libadns-devel
Server problem?
--
Richard Bos
Without a home the journey is endless
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I have the build script (2006-10-05 I think) installed but I found some
very obscure config files:
the ones for 10.1 and 10.2 both define a %suse_version of 1001, which
caused me some trouble.
Somehow, for 10.1 I didn't see it, but as I created a package that
should behave differentlz on 10.2, I ran into it.
simply changing %suse_version 1020 inside the SL10.2 config file of
build helped me.
Did I destroy something else with this action?
Or did I just fix a bug on my system which is still spread in the
world?
Any information is welcome...
Dominique
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Am I correct to assume that the BS currently doesn't have any
fedora/debian/ubuntu/mandriva repos for x86_64?
Releasing spec files that haven't been tested on x86_64 is hardly
acceptable these days.
Can fedora/debian/ubuntu/mandriva repos (ordered according to my
priorities) for x86_64 be added soon, please?
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Doing a local "osc build Fedora_Extras_5 i586 my.spec" currently fails with:
- --- snip ---
The following package could not be verified:
/var/tmp/osbuild-packagecache/Fedora:Core5/standard/i386/SysVinit-2.86-2.2.2.i386.rpm:
(SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#4f2a6fd2)
- If the key is missing, install it first.
For example, do the following as root:
gpg --keyserver pgp.mit.edu --recv-keys 4f2a6fd2
gpg --armor --export 4f2a6fd2 > /root/keyfile-4f2a6fd2
rpm --import /root/keyfile-4f2a6fd2
Then, just start the build again.
- --- snap ---
Isn't this something that "osc build" should take care of for me? Otherwise, am
I expected to run the mentioned commands manually in the chroot? Or am I missing
something else?
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
