Ondrej Certik writes: > On Dec 5, 2007 8:10 PM, Lucas Nussbaum <[EMAIL PROTECTED]> wrote: > > On 05/12/07 at 13:37 +0100, Bernd Zeimetz wrote: > > > >> 1. Why is there the build-conflict in the first place? This is the > > > >> question to original maintainers (Marco, Alexandre, Jose, Matthias) > > > > > > > > I added the build-conflict because without it, dpkg-shlibdeps would > > > > make them depend exclusively on blas and lapack, instead of depending > > > > on the virtual package (because all other packages provide blas and > > > > lapack) > > > > > > The packages should not be installed on the buildds anyway, so I think > > > ti shoudl work without build-conflicts. > > > > There's no garantee about which packages are *not* installed on the > > buildds, since packages are not uninstalled after builds. > > Build-conflicts is the good way to solve that. > > So would do you suggest? Just to wait until python-numpy gets build on > buildbots? Or do you suggest to take some action (which)? :)
help getting refblas3, lapack3 and atlas getting built with gfortran, fix the shlibs lines in these packages and then rebuild the python-numpy package. If you're interested, please join the debian-toolchain list or have a look at the archives. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
