Bug#672952: FTBFS: compile errors

2012-05-21 Thread Johannes Ring
On Wed, May 16, 2012 at 5:02 PM, Scott Kitterman wrote: > On Wednesday, May 16, 2012 12:04:05 PM Johannes Ring wrote: >> [Cc'ing debian-python] > ... >> @debian-python: Since DOLFIN does not work with Python 3 (yet) maybe a >> Build-Conflicts should be added? And what about X-Python-Version? This

Bug#672952: FTBFS: compile errors

2012-05-16 Thread Scott Kitterman
On Wednesday, May 16, 2012 12:04:05 PM Johannes Ring wrote: > [Cc'ing debian-python] ... > @debian-python: Since DOLFIN does not work with Python 3 (yet) maybe a > Build-Conflicts should be added? And what about X-Python-Version? This > is currently set to ">= 2.5". Should it be ">= 2.5, << 3.0" or

Bug#672952: FTBFS: compile errors

2012-05-16 Thread Johannes Ring
[Cc'ing debian-python] Hi LaMont, Thanks for the report but I'm wondering why python3.2 is installed on this build machine? From looking at the build log [1], it seems that it has been pre-installed? Is that intentional? DOLFIN Build-Depends on python-all-dev (>= 2.6.6-3~) and FWICT only python2.

Bug#672952: FTBFS: compile errors

2012-05-14 Thread LaMont Jones
Package: dolfin Version: 1.0.0-5 -- cd /build/buildd-dolfin_1.0.0-5-ia64-LDjTpK/dolfin-1.0.0/obj-ia64-linux-gnu/dolfin/swig && /usr/bin/g++ -D_cpp_EXPORTS -DBOOST_UBLAS_NDEBUG -DHAS_SLEPC -DHAS_PETSC -DHAS_UMFPACK -DHAS_CHOLMOD -DHAS_SCOTCH -DHAS_ZLIB -DHAS_MPI -DMPICH_IGNORE_CXX_SEEK -DHAS_