Last night's builds for the net-snmp project show a number of build failures for
the various repos, all of them happening on build03 and all of them ending in
md: stopping all md devices.
System halted.
Is build03 broken?
+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
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
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
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
Hi all
Could there be some sort of system in place which informs if the
package being deleted is linked by someone else?
This way we can move the package from one project to another if the
original packager does not want to maintain it.
With many more packages and project cross linking might get quite
complex, so if the package is linked by say 5 projects those links
should also be preserved if the package is moved.
I had linked intltool 0.35 from project jarpack, which is now deleted,
that is why this suggestion.
Cheers
-J
--
CyberOrg Info
Novell & IBM Partner
7 FF Unad Deep, Tower A
Susen Tarsali Road
Vadodara 390 009
T. +91 265 3042956 M +91 9898092956
Web. http://www.cyberorg.info
---------------------------------------------------------------------
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
expansion error have choice for ghostscript_any needed by
ghostscript-library: ghostscript-serv ghostscript-x11
Can this be solved on the BS or should I just add another "if" to my spec
file?
Regards
--
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
(sorry for the lame reply, I'm not on os-bs and replying to a forward
with attached body does not work for me - so, top-posting)
First, for problems please file bugreports. Now, packages are
always compiled with the system (fortran) compiler, which is
gfortran since 10.0 (where do you get the impression from that
it is built with g77? what is 'The official suse-type webpage' here?).
The undefined symbol is because you need
to link against libgfortran, so this looks like a scipy bug.
"Suse's BLAS is buggy, you have to compile yourself."
This is a very unspecific statement, I cannot help here.
Yes, the lapack/blas is from netlib, not some optimized version.
Hope this helps,
Richard.
----
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
--
Richard Guenther <rguenther(a)suse.de>
Novell / SUSE Labs
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org