Fwd: python-numpy has problems on buildbots
On Dec 5, 2007 1:03 PM, José Fonseca [EMAIL PROTECTED] wrote: 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 amd64, so that one is fine. Crucial are the following lines from debian/control: 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 Build-Conflicts: lapack-dev [!arm !m68k], blas-dev [!arm !m68k], atlas2-base, atlas2-base-dev, atlas3-base, atlas3-base-dev As you can see, arm and m68k are exceptions and indeed python-numpy builds on them just fine (see the link above). (It's still building on m68k, but last revision built there fine). It doesn't build on other architectures. If we look for example why it failed on the most important architecture i386: [...] So as you can see, the problem is that buildbots install atlas3-base for some reason and because we build-conflict with it, we fail. Three questions: 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) So instead of getting the desired: Depends: atlas3-base | lapack3 | liblapack.so.3, atlas3-base | refblas3 | libblas.so.3, ... dpkg-shlibdeps would produce: Depends: atlas2-base Or Depends: atlas3-base 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. Ondrej
RFP: python-py-bcrypt -- implementation of OpenBSD's Blowfish password hash algorithm
Package: wnpp Severity: wishlist * Package name: python-py-bcrypt Version : 0.1 Upstream Author : Damien Miller [EMAIL PROTECTED] * URL : http://www.mindrot.org/projects/py-bcrypt/ * License : ISC/BSD (advertising clause--see below) Programming Lang: C, Python Description : implementation of OpenBSD's Blowfish password hash algorithm py-bcrypt is a Python module implementating the OpenBSD Blowfish password hashing algorithm, as described in A Future-Adaptable Password Scheme by Niels Provos and David Mazieres: http://www.openbsd.org/papers/bcrypt-paper.ps This system hashes passwords using a version of Bruce Schneier's Blowfish block cipher with modifications designed to raise the cost of off-line password cracking. The computation cost of the algorithm is parametised, so it can be increased as computers get faster. I have Cc'd the debian-python list on this, since it's a pretty straightforward Python (=2.4) module with a standard distutils setup.py included. If there's no interest, I'll retitle it to an ITP in a week or two, but this seemed like a good first step since I've not packaged a public Python module previously. The LICENSE file quotes a four-clause BSD (advertising) license for code taken from OpenBSD circa 1997, which could be easily changed to a modern BSD license, though the py-bcrypt author should probably be asked to do this upstream. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: python-numpy has problems on buildbots
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. So it indeed seems to work: http://buildd.debian.org/pkg.cgi?pkg=python-numpy numpy built on i386, alpha, amd64, mips, mipsel, powerpc and probably on all the others. The i386 is in incoming, so tomorrow expect working python-numpy on your system. And if it isn't working, file a bug. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
