So the problem still persists on amd64 as reported by Jose.
> > >
> > > Apparently the problem still persists on amd64:
> > >
> > > $ apt-cache show python-numpy
> > > Package: python-numpy
> > > Priority: optional
> > > Section: python
> > > Installed-Size: 6092
> > > Maintainer: Debian Python M
> I tried that - i.e. installed atlas3-base on my system, commented out
> build-conflicts, built python-numpy and got these dependencies:
>
> Depends: atlas3-base | lapack3 | liblapack.so.3, atlas3-base |
> refblas3 | libblas.so.3, ...
>
> which is imho correct, right? We are going to upload now.
"José Fonseca" <[EMAIL PROTECTED]> writes:
> Or find someway to override dpkg-shlibdeps behavior so that it
> produces the right dependency list.
Supplying a suitable shlibs.local should achieve this.
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ |
> > >> 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.
>
> > if you look into a random log you'll see that the build chroot is
> > cleaned up after a build. The
On Wed, Dec 05, 2007 at 10:07:15PM +0100, Bernd Zeimetz wrote:
> >> 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.
> if you look into a random log you'll see tha
>> 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.
if you look into a random log you'll see that the build chroot is
cleaned up after a build. There're only packages
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)
> >
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-con
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 exclusi
Build-Conflicts: lapack-dev [!arm !m68k], blas-dev [!arm !m68k],
atlas2-base, atlas2-base-dev, atlas3-base, atlas3-base-dev
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 buil
>> Build-Depends: cdbs (>= 0.4.43), python-all-dev, python-all-dbg,
>> python-central (>= 0.5.6), refblas3-dev [!arm !m68k], lapack3-dev
>> [!arm !m68k], debhelper (>= 5.0.38), g77, patchutils, python-docutils,
>> fftw3-dev
lapack3-dev and refblas3-dev should exist on all architectures now.
>>
Hi,
On 12/5/07, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> Hi,
>
> we with Kumar made a progress and had python-numpy uploaded (thanks Fabio).
>
> It builds nicely in pbuilder, but fails to build on buildbots. See:
>
> http://buildd.debian.org/pkg.cgi?pkg=python-numpy
>
> Fabio uploaded it on amd6
12 matches
Mail list logo
