Bug#739396: libdune-pdelab-doc: please register docs with doc-base

Package: libdune-pdelab-doc Version: 2.0~20140111g795acb4-1 Severity: normal Debian has the doc-base register (managed by the doc-base package) which allows documentation files such the set provided by libdune-pdelab-doc to be conveniently accessed from a central point, e.g. accessible from

Bug#786857: python-dolfin: fails to import

Package: python-dolfin Version: 1.5.0-2 Severity: grave Justification: renders package unusable The dolfin python package fails to import: $ python Python 2.7.10rc1 (default, May 11 2015, 04:32:37) [GCC 4.9.2] on linux2 Type help, copyright, credits or license for more information. from dolfin

Bug#802706: slepc: FTBFS: Unable to link with PETSc

On Fri, 23 Oct 2015 10:21:35 +0800 Drew Parsons <dpars...@debian.org> wrote: > This one's a mystery ... "works for me"   > i.e. my upload was built successfully with sbuild. > We diagnosed the problem on irc (i.e. why it was "working for me"): the default sb

Bug#802706: slepc: FTBFS: Unable to link with PETSc

This one's a mystery ... "works for me"   i.e. my upload was built successfully with sbuild. Drew -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#791238: petsc: library transition is needed now GCC 5 is the default

On Wed, 5 Aug 2015 16:17:54 +0200 Martin Pitt wrote: > tag 791238 patch > user release.debian@packages.debian.org > usertag 791238 + transition > block 791238 by 790756 > > Hello, > > this is a debdiff which we uploaded to Ubuntu (aside from some formal > debian/changelog

Bug#803477: petsc: FTBFS against mpich

block 803477 807318 thanks Testing the petsc build on s390x yields this error  #  error 'Please use the same version of GCC and g++ for compiling MPICH and user MPI programs' The error comes from /usr/include/mpich/mpicxx.h: #ifdef __GNUC__ # if __GNUC__ >= 5 #  if __GNUC_MINOR__ > 2 && 2

Bug#807318: libmpich-dev: should add Depends: to match hard-wired gcc dependency in mpicxx.h

Package: libmpich-dev Version: 3.1-6 Severity: grave Justification: renders package unusable /usr/include/mpich/mpicxx.h has a hardwired dependency on the gcc used to build mpich (gcc 5.2): #ifdef __GNUC__ # if __GNUC__ >= 5 # if __GNUC_MINOR__ > 2 && 2 == 2 # error 'Please use the same

Bug#816101: petsc: FTBFS on mipsel - broken openmpi breaks petsc build

On Wed, 13 Apr 2016 18:59:22 +0800 Drew Parsons <dpars...@debian.org> wrote: >  > Any ideas what to do next?  The openmpi bug (#818909) still has some > unfinished business with chrpath for mips architectures to remove the > workaround applied in 1.10.2-12. Could this generate

Bug#814149: add alternative for /usr/bin/dx

I agree with Graham, this is a plain and simple naming clash.  The only reasonable resolution is to rename one (or both) of the binaries.   You could workaround the clash with Conflicts:, but that's not reasonable either since there's no reason both binaries shouldn't coexists. A possible

Bug#816101: petsc: FTBFS on mipsel - try rebuild again

On Sun, 2016-03-13 at 17:35 +0100, Emilio Pozuelo Monfort wrote: > On 13/03/16 16:34, Drew Parsons wrote: > > > > Source: petsc > > Followup-For: Bug #816101 > > > > The petsc build failure on mipsel appears to be a transient problem > > on > > t

Bug#816101: petsc: FTBFS on mipsel - try rebuild again

Source: petsc Followup-For: Bug #816101 The petsc build failure on mipsel appears to be a transient problem on the build machine. Please try the mipsel build again. gb petsc_3.6.2.dfsg1-3+b3 . mipsel -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#816101: petsc: FTBFS on mipsel - try rebuild again

On Sun, 2016-03-13 at 19:59 +0100, Emilio Pozuelo Monfort wrote: > [Adding debian-wb-team back to Cc] > > On 13/03/16 17:56, Drew Parsons wrote: > > > > On Sun, 2016-03-13 at 17:35 +0100, Emilio Pozuelo Monfort wrote: > > > > > > On 13/03/16 16:34, Drew

Bug#816101: petsc: FTBFS on mipsel - try rebuild again

On Mon, 14 Mar 2016 09:39:04 +0800 Drew Parsons <dpars...@debian.org> wrote: > > Did you read the MOTD? See https://dsa.debian.org/doc/schroot/ >  > I missed that. I'll add it to my bookmarks. >  >  > > Anyway given the build queue is currently empty on mipsel, I've

Bug#816101: petsc: FTBFS on mipsel - timeout while running the test suite

As far as I can tell this build failure is just some ephemeral problem on the build machine.  The same code built before, and builds now on mips and other architectures. Trigger a rebuild, maybe it will work now. The orte/plm warning is a red herring.  All architectures have the same problem.

Bug#816101: petsc: FTBFS on mipsel - broken openmpi breaks petsc build

reopen 816101 found 816101 3.6.3.dfsg2-4 thanks A workaround for openmpi has now been applied (1.10.2-12+b1) enabling petsc to build on mips64el (and mips). But the petsc build still fails on mipsel. The log does not reveal any failure mode.  The build completes successfully.  The test for 

Bug#816101: petsc: FTBFS on mipsel - broken openmpi breaks petsc build

block 816101 by 818909 severity 816101 important retitle 816101 FTBFS on mipsel - broken openmpi breaks petsc build thanks openmpi on mips seems to be in a sorry state at the moment. Indeed, even though the petsc builds halts on the fortran test, there is an mpicc segfault earlier in the log at

Bug#820080: libpetsc{-, complex-}3.6.3-dev: leaves alternatives after purge: /etc/alternatives/libpetsc_{real, complex}.so

You're quick :) Thanks for the tips.  I'm intending to remove the links in /usr/lib, converting alternative petsc.so to petsc.so.multiarch (i.e. use only pure multiarch links with no legacy links.)  Hopefully your discussions can help sort that out. Drew -- debian-science-maintainers mailing

Bug#816101: petsc: FTBFS on mipsel - broken openmpi breaks petsc build

On Fri, 22 Apr 2016 18:25:41 +0200 Graham Inggs wrote: >  > Your luck ran out, the build failed on powerpc [1]. Well dang. I've prepared a patch (test_mpi_conditional) to skip the 2 MPI test. I'm making it conditional to skip only on mipsel and powerpc, on the grounds that

Bug#822539: RM: ufc -- ROM; superseded by ffc

Package: ftp.debian.org Severity: normal ufc is now obsolete, superseded by ffc -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#822542: RM: ferari -- ROM; obsolete

Package: ftp.debian.org Severity: normal ferari is obsolete, no longer used in the FENiCS suite -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#822543: RM: viper -- ROM; obsolete

Package: ftp.debian.org Severity: normal viper is no longer used in the FENiCS suite -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#822541: RM: syfi -- ROM; obsolete

Package: ftp.debian.org Severity: normal syfi is obsolete, no longer used in the FENiCS suite -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#822255: #822255 python-dolfin: remove dependency on python-netcdf

forcemerge 821215 822255 thanks 822255 was mistitled, it refers to python-netcdf not python-numpy -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#825096: dolfin: FTBFS: No rule to make target '/usr/lib/libgl2ps.so',

> make[4]: *** No rule to make target '/usr/lib/libgl2ps.so', needed by > 'dolfin/libdolfin.so.1.6.0'.  Stop. I suspect this is transient and arises from a dependent package (vtk6 I think).  A new version of gl2ps is flushing through, upgrading to multiarch. Drew -- debian-science-maintainers

Bug#782029: dolfin-bin: FEniCS/DOLFIN fails to compile Python dolfin.Expression()

reassign 782029 libsuitesparse-metis-dev retitle 782029 build multiarch installation of suitesparse-metis  severity 782029 serious thanks On Mon, 06 Apr 2015 10:57:40 -0700 Jan Medlock wrote: >  > Removing '/x86_64-linux-gnu' from the paths to the libsuitesparse

Bug#346182: Bug#822321: crashes when importing VRML file (containing PROTO)

reopen 346182  reassign 346182 libvtk6.2 thanks This bug is still present for the same test file.  A gdb backtrace pins it on vtkVRMLImporter::exitField() from /usr/lib/x86_64-linux-gnu/libvtkIOImport-6.2.so.6.2,  which is in package libvtk6.2. It's essentially the same backtrace as before, only

Bug#827740: Re #827740: isympy start fails: No module named sympy.interactive

On Mon, 20 Jun 2016 14:06:11 +0200 Alberto Luaces wrote: > Maybe another binary package could be added (named isympy3), > including > an appropriate isympy3 script... > At that point isympy would depend on python-sympy (without > python3-sympy as an alternative dependency) and

Bug#754390: #754390: [src:slepc] any chance to backport more current version to wheezy-backports?

Hi Giacomo, which version of stable are you currently using? Not wheezy at the moment? The current petsc in unstable/testing is 3.6.4 (soon to be updated to 3.7). slepc is closely bound to petsc of course (also v3.6 moving soon to 3.7) wheezy fails on these petsc build-depends:   mpi-default-dev

Bug#852514: libpetsc3.7-dev: leaves alternatives after purge: /usr/lib/petscdir/{3.7, 3.7-real}

On Wed, 25 Jan 2017 02:42:20 +0100 Andreas Beckmann wrote: > Package: libpetsc3.7-dev > Version: 3.7.5+dfsg1-3 ... >  > >From the attached log (scroll to the bottom...): >  > 2m18.4s INFO: Warning: Package purging left files on system: >   /etc/alternatives/petsc3.7 ->

Bug#852514: libpetsc3.7-dev: leaves alternatives after purge: /usr/lib/petscdir/{3.7, 3.7-real}

>  > 2m18.4s INFO: Warning: Package purging left files on system: >   /etc/alternatives/petsc3.7 -> /usr/lib/petscdir/3.7.4/x86_64-linux- gnu-real not owned >   /etc/alternatives/petsc3.7-real -> /usr/lib/petscdir/3.7.4/x86_64- linux-gnu-real  not owned >   /usr/lib/petscdir/  owned by:

Bug#853029: mpi-default-dev: update mpi defaults for m68k and sh4 to openmpi?

On Mon, 2017-01-30 at 10:20 +0100, Mattia Rizzolo wrote: > > Such change really needs to be ACK by a porter, therefore I'm CCing > the > 68k and sh lists. > Thanks Mattia. J.P. Adrian Glaubitz also replied via the port lists, and said he'll check to confirm the change won't break anything.

Bug#852011: petsc (libpetsc3.7.4-dev) depends on libgfortran-5-dev

On Fri, 20 Jan 2017 18:22:01 +0100 Matthias Klose wrote: >  > The severity of this report is likely to be raised before the release, > so that the gcc-5 package can be removed for the release. >  "Likely to be raised..." ?? The severity is already serious! Drew --

Bug#853029: mpi-default-dev: update mpi defaults for m68k and sh4 to openmpi?

Package: mpi-default-dev Version: 1.8 Severity: normal This bug report follows on from #833425 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833425 openmpi now builds on m68k and sh4. For various reasons it could be convenient if the Debian default mpi on these architectures could be

Bug#836677: FTBFS: superlu not needed for superlu 5.2

retitle 836677 FTBFS: superlu patch needs updating for superlu 5.2 thanks On Sun, 04 Sep 2016 23:59:19 +0800 Drew Parsons <dpars...@debian.org> wrote: >  > pysparse FTBFS against libsuperlu-dev 5.2, with the error: >  >   In file included from Src/superlu3module.c:12:0: >  

Bug#836677: FTBFS: superlu not needed for superlu 5.2

Source: pysparse Version: 1.1-1.3 Severity: important superlu 5.2 is currently in experimental but will soon be released to unstable. pysparse FTBFS against libsuperlu-dev 5.2, with the error: In file included from Src/superlu3module.c:12:0: /usr/include/superlu/slu_ddefs.h:151:16: note:

Re: dolfin_2016.1.0-4_source.changes ACCEPTED into unstable

On Wed, 2016-09-14 at 09:56 +0200, Johannes Ring wrote: > Hi Drew, > Changes: > >  dolfin (2016.1.0-4) unstable; urgency=medium > >  . > >    * Disable HDF5 support. > >  > Can you give more details about the error? I think this might be a > bug > in the FindHDF5.cmake file in CMake. Did you see

Bug#822971: dolfin: FTBFS on kfreebsd

On Sat, 17 Sep 2016 11:29:54 +0800 Drew Parsons <dpars...@debian.org> wrote: > ... It's not yet built at the moment due to > other build-dependencies higher up the chain. Specifically, mpi4py (python-mpi4py) is not currently building on kfreebsd. -- debian-science-maintainers

Bug#822971: dolfin: FTBFS on kfreebsd

On Fri, 29 Apr 2016 13:46:07 + Mattia Rizzolo wrote: >  > Since this version, with the switch to vtk6 and whatnot, dolfin FTBFS on > kfreebsd. Looks like this was a transient failure.  dolfin later built successfully in kfreebsd.  It's not yet built at the moment due to

Bug#842405: paraview: can't load hdf5 file: vtkSISourceProxy: Failed to create vtkXdmfReader

Package: paraview Version: 5.1.2+dfsg1-1+b1 Severity: normal I'm trying to load a 1D HDF5 dataset (attached) into paraview, but it's crashing with ERROR: In /build/paraview-MvSREd/paraview-5.1.2+dfsg1/ParaViewCore/ServerImplementation/Core/vtkSIProxy.cxx, line 310 vtkSISourceProxy

Bug#726775: libslepc3.4.2-dev: CMake script location

SLEPcConfig.cmake is no longer provided by SLEPc (3.7). There is a internal script at /usr/lib/slepcdir/3.7.3/x86_64-linux-gnu-real/lib/slepc/conf/SLEPcBuildInternal.cmake But it is used only for the internal build, it's not intended to be used by client programs. slepc4py uses the SLEPC_DIR

Bug#802303: #802303: libpetsc3.6.2-dev: arch-dependent file in "Multi-Arch: same" package

I see what's going on a little better. The filepatch /usr/share/python/runtime.d/libpetsc3.6.2-dev.rtupdate is common to all arches, but its contents are architecture specific, which breaks Multi- Arch:same. Since that file was generated by dh_python2, it indicates that dh_python2 is not

Bug#843010: elmerfem: hypre headers in /usr/include/hypre

Source: elmerfem Version: 6.1.0.svn.5396.dfsg2-4 Severity: normal hypre is now updated to 2.11.1. The main impact that effects elmer is that the hypre header files have been moved from the common directory to /usr/include/hypre. Depending on how the elmer build scripts search for hypre, it's

Bug#846512: ITP: dijitso -- distributed just-in-time building of shared libraries

Johannes Ring wrote: > > I have packaged dijitso locally but when I try to create a repository > at https://anonscm.debian.org/git/debian-science/packages/fenics/diji > tso.git > I get a permission denied error. I am trying to use `gbp > create-remote-repo`: > > I guess I don't have permissions

Re: Bug#846512: ITP: dijitso -- distributed just-in-time building of shared libraries

On Thu, 2016-12-08 at 14:43 +0100, Mattia Rizzolo wrote: > On Thu, Dec 08, 2016 at 01:20:53AM +0800, Drew Parsons wrote: > > > > looks like group members are locked out of the fenics subdir: > > > > Can you provide group write access, chmod g+w /git/debian-

Bug#847045: libtrilinos-zoltan-dev

On Mon, 5 Dec 2016 06:30:26 +0100 1...@gmx.us wrote: >  > Please compile PETSc with libtrilinos-zoltan-dev. At least > as a recommended package. Like, libsuperlu-dev is now. >  trilinos has build pains at the moment. We'll need that to settle out first. If we'll be supporting zoltan then

Bug#802706: slepc: FTBFS: Unable to link with PETSc

On Thu, 2017-01-05 at 14:10 +0100, Santiago Vila wrote: > found 802706 3.7.3+dfsg1-3 > thanks > > Hi. > > Sorry for the reopening but this is happening again in stretch. > (I built this package 200 times, and it failed 200 times). > > Build logs available here: > >

Bug#826960: mumps: Please package with metis and parmetis

On Wed, 29 Mar 2017 17:13:13 +0800 Drew Parsons <dpars...@debian.org> wrote: > > Hi Pierre, I'm preparing an update to mumps 5.1.  I'm following > upstream's new debian template, which builds both scotch and metis at > the same time.  This means libmumps-scotch-dev wil

Bug#826960: mumps: Please package with metis and parmetis

On Fri, 10 Jun 2016 18:36:52 +0200 (CEST) Pierre Saramito wrote: > Source: mumps > Severity: wishlist >  > Dear Adam, >  > It would be nice to have libmumps-metis-dev and libmumps-parmetis-dev > as alternatives to and libmumps-ptscotch-dev packages: > please, could you package mumps with

Bug#858228: dolfin: PETSc and SCOTCH support disabled on kfreebsd

Source: dolfin Version: 2016.2.0-3 Severity: normal petsc and slepc are available on kfreebsd. But dolfin configuration is unable to activate their support due to a linking error during configuration tests. SCOTCH support also fails. A snippet from the log gives: -- Checking for package

Bug#857692: petsc: FTBFS in !linux

On Tue, 14 Mar 2017 00:55:39 +0100 Mattia Rizzolo wrote: >  > petsc fails to build in hurd-i386, kfreebsd-i386 and kfreebsd-amd64. The hurd failure looks like the common problem arising from the changes in PIE handling, see bugs #848129, #854061, same as the FTBFS on other

Bug#857692: petsc: FTBFS in !linux

On Thu, 16 Mar 2017 10:28:09 +0100 Mattia Rizzolo <mat...@debian.org> wrote: > On Thu, Mar 16, 2017 at 11:01:10AM +0800, Drew Parsons wrote: > > The hurd failure looks like the common problem arising from the changes > > in PIE handling, see bugs #848129, #854061, same

Bug#857507: mesh generation module 'mshr' missing

Package: python-dolfin Version: 2016.2.0-2 Followup-For: Bug #857507 reassign 857507 fenics forcemerge 851183 857507 thanks Hi Stephen, mshr is another fenics component alongside dolfin. It's not required for general dolfin usage, though of course your tutorial example uses it. The ftp-masters

Bug#851183: fenics: Misses important 'mshr' module

On Fri, 13 Jan 2017 16:48:22 +0100 Hagen Fuchs wrote: >  > > mshr needs a patched version of CGAL. >  > Ouf.  Anything I can do or is it simply a matter of just waiting for the > maintainers? >  Johannes has prepared a de-CGALed version in his  

Bug#857507: mesh generation module 'mshr' missing

On Fri, 17 Mar 2017 10:47:26 +0800 Drew Parsons <dpars...@debian.org> wrote: >  > Hi Stephen My apologies, your name is Steve not Stephen! D. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mail

Bug#822971: dolfin: FTBFS on kfreebsd

tags 822971 + fixed pending thanks A fix to build dolfin on kfreebsd is in git 2016.2.0-3, pending upload. Drew -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#859492: mumps: Incomplete debian/copyright?

tags 859492 + fixed pending thanks On Tue, 2017-04-04 at 10:03 +0100, Chris Lamb wrote: > > I just ACCEPTed mumps from NEW but noticed it was missing > attribution  > in debian/copyright for at least src/ana_orderings.F. > > (This is not exhaustive so please check over the entire package  >

Bug#860599: libmpich-dev: provide alternative mpi-fort.pc

Package: libmpich-dev Version: 3.2-7+b1 Severity: normal The mpi alternatives provide several pkg-config files: mpi-c.pc, mpi-cxx.pc, mpi-fort.pc, mpi.pc, all provided by openmpi. But mpich only provides mpi.pc This somewhat breaks usage of mpi-defaults, since it means we can't rely on these

Bug#870054: freefem++: scalapack and blacs not found at build time

Source: freefem++ Version: 3.47+dfsg1-1 Severity: normal blacs is about to be removed from the Debian archives, replaced by scalapack2.0 (now in experimental). So the configuration for the freefem++ build will need to be updated to match. configure will need to point the blacs library at

Bug#868523: FTBFS: test failed 617 ML_MLP_NonSym_MPI_4, 668 Phalanx_dag_manager_MPI_1

On Mon, 17 Jul 2017 10:21:03 +0800 Drew Parsons <dpars...@debian.org> wrote: >  > For whatever reason, the build does not fail on the buildd (odd, my > test ran 842 tests, buildd only runs 830).  Ah I see, you uploaded -4 while we were testing :)   The bugserver didn't send me

Bug#854228: Libraries not linked with their deps

On Tue, 21 Mar 2017 11:03:07 +0800 Drew Parsons <dpars...@debian.org> wrote: > On Tue, 21 Mar 2017 10:50:29 +0800 Drew Parsons <dpars...@debian.org> > wrote: > >  > > That document is from 1997 though.  The MPI standard has moved > through > > 2 major

Bug#863291: libscalapack-openmpi1: memory leak in pXgemr2d

Hi Grigory, scalapack 2.0 is now available in experimental. Could you test if your pXgemr2d problem persists when built against scalapack 2.0 with openmpi 2.1.1 ? Thanks, Drew -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#863291: libscalapack-openmpi1: memory leak in pXgemr2d

On Tue, 25 Jul 2017 23:03:23 +0800 Drew Parsons <dpars...@debian.org> wrote: > Hi Grigory, >  > scalapack 2.0 is now available in experimental. >  > Could you test if your pXgemr2d problem persists when built against > scalapack 2.0 with openmpi 2.1.1 ? Note that scalapac

Bug#865526: PETSc has strict dependency on MPI version

reopen 865526 retitle 865526 PETSc has strict dependency on MPI version severity 865526 normal forwarded 865526 https://bitbucket.org/petsc/petsc/commits/ca70f86ee9db8e69523e0e69f12289c6cab9b4cb?at=jed/mpi-semver thanks Reopening to help track upstream handling of PETSc's MPI dependency logic.

Bug#865526: libpetsc3.7.5-dev: uninstallable on current sid

On Fri, 30 Jun 2017 05:56:30 +0300 Adrian Bunk wrote: >  > This is a release critical bug that should stay open until it is fixed  > in sid. nmu has been filed in #866582 which will fix the bug in this instance. The strict dependency of PETSc on the MPI version (that requires

Bug#871279: libdolfin2016.2: requires rebuild against GCC 7 and symbols/shlibs bump

On Mon, 2017-08-07 at 17:44 +, Mattia Rizzolo wrote: > > > dolfin 2017.1 is in the NEW queue, so that upgrade will handle this > > bug. > > Is the binary you uploaded built with gcc-7?  Otherwise that would > not fix this bug. It's been sitting in NEW for a month, so it would have been

Bug#871279: libdolfin2016.2: requires rebuild against GCC 7 and symbols/shlibs bump

On Mon, 07 Aug 2017 15:47:15 +0100 jcowg...@debian.org wrote: > Package: libdolfin2016.2 > Version: 2016.2.0-5 >  > It appears that your package provides an external symbol that is > affected by the recent name mangling changes in GCC 7. See: >

Bug#863829: python2: dolfin 'module' object has no attribute 'cpp'

Package: python-dolfin Version: 2016.2.0-3 Severity: grave Justification: renders package unusable Weird, the new python3 module seems to have broken the python2 dolfin module. That's not good. Importing dolfin gives the error: AttributeError: 'module' object has no attribute 'cpp' Importing

Bug#863828: python3-instant: undefined symbol: PyClass_Type during interpolate

On Thu, 1 Jun 2017 10:39:37 +0200 Johannes Ring <joha...@simula.no> wrote: > On Thu, Jun 1, 2017 at 10:24 AM, Drew Parsons <dpars...@debian.org> wrote: > > Should the vtk section in UseDOLFIN.cmake be controlled with some > > python3 test, so VTK is still pulled in for p

Bug#863828: python3-instant: undefined symbol: PyClass_Type during interpolate

reassign 863828 libdolfin-dev 2016.2.0-3 thanks On Thu, 2017-06-01 at 10:01 +0200, Johannes Ring wrote: > > The problem here is that Python 2 header files are used. This comes > from VTK, which is built against Python 2 only. The solution is to > not > call `find_package(VTK)` and

Bug#863828: python3-instant: undefined symbol: PyClass_Type during interpolate

Package: python3-instant Version: 2016.2.0-2 Severity: normal Testing the new python3 dolfin. It works fine on my own scripts. But seems to fail when instant is invoked by interpolate. $ instant-clean-3 $ ipython3 Python 3.5.3 (default, Jan 19 2017, 14:11:04) In [1]: from fenics import * #

Bug#874712: python-h5py: all arches FTBFS

Package: python-h5py Version: 2.7.0-1+b1 Severity: serious Justification: FTBFS Your new version of h5py fails to build from source. All arches. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64

Bug#876890: scalapack FTBFS on arm64: test failures

On Tue, 26 Sep 2017 21:09:03 +0300 Adrian Bunk wrote: > Source: scalapack > Version: 2.0.2-3 > Severity: serious > > Some recent change in unstable makes scalapack FTBFS on arm64: > > https://tests.reproducible-builds.org/debian/history/scalapack.html >

Bug#876890: scalapack FTBFS on arm64: test failures

On Thu, 28 Sep 2017 15:28:11 +0800 Drew Parsons <dpars...@debian.org> wrote: > > The actual FTBFS is from the openmpi test: > > OpenMPI tests failed: >20 - dpb2tim (Failed) > A test build on the porterbox succeeded. The failure in your test must have been a tr

Bug#872911: mpi-default-dev: m68k not listed in OPENMPI_AVAILABLE_ARCHITECTURES

Package: mpi-default-dev Version: 1.8 Severity: normal OPENMPI_AVAILABLE_ARCHITECTURES in /usr/share/mpi-default-dev/debian_defaults does not include m68k. But openmpi is built on m68k (since 2.1.1-1), so it should now be added. Similarly, powerpcspe is not listed in

Re: dolfin_2017.1.0-1_amd64.changes REJECTED

On Sun, 2017-08-27 at 12:00 +, Luca Falavigna wrote: > Hi, > > libdolfin2017.1 gained a dependency on libparmetis4.0, which is in > non-free. Weird. parmetis support is explicitly switched off at configure time. Drew -- debian-science-maintainers mailing list

Bug#877054: #877054: hypre FTBFS with multiarch blas

Waiting for 2.11.2-1 to get through the NEW queue. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#882667: hypre: CUDA support: hacks impeded by -W flags

On Sat, 25 Nov 2017 20:24:50 +0800 Drew Parsons <dpars...@debian.org> wrote: > > Again, the problem is that -W is not recognised by nvcc. Would have > to hack the soname patch to encapsulate it inside --compiler-options Can get further using nvcc --linker-options to carry -Wl op

Re: Comments regarding slepc_3.8.1+dfsg1-1_amd64.changes

On Sun, 2017-11-26 at 15:36 +, Thorsten Alteholz wrote: > Hi Drew, > > I marked your package for accept, but there are some issues found by > one of our trainees: > * all html files include , which > is reported by lintian > * html files for sources are not regenerated > * a lot of

Bug#700087: libmumps-dev: Please package the Scilab module

Hi Sylvestre, both scilab and mumps are recently updated (latest versions in experimental). Are you still able to work on the scilab module for mumps? Drew -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#882667: hypre: CUDA support: hacks impeded by -W flags

Source: hypre Version: 2.13.0-1exp1 Severity: normal With some hacking, we can start attempting to build hypre with CUDA support (private build, or perhaps a separate hypre package in contrib). Brief notes: - The version of nvcc (nvidia-cuda-toolkit) in debian non-free is 8.0.61-3 nvcc does not

Bug#883842: superlu: Source includes "SRC/mc64ad.c" listed in Files-Excluded header

On Fri, 08 Dec 2017 09:58:34 + Chris Lamb wrote: > > So, I would add an override for the "source-includes-file-in-files- excluded" > Lintian tag and include an explanation there. That should cover it I think. > I think that's a bug in lintian, if it's judging source files

Bug#884121: Build-Depends: libhypre-dev, but does not build against HYPRE

Package: freefem++ Version: 3.47+dfsg1-2 Severity: normal freefem++ Build-Depends: libhypre-dev, and checks for hypre during configure. But in the rest of the build HYPRE is not actually used. There are files that include hypre headers in src/solver and in examples++-mpi, but the examples

Bug#865671: scotch hides build failures

tags 865671 moreinfo thanks On Fri, 23 Jun 2017 18:07:46 +0200 Helmut Grohne wrote: > Source: scotch > Version: 5.1.12b.dfsg-2 > > When some part of scotch's build fails (e.g. mpicc), the build continues > and may produce a broken package. This violates Debian Policy section

Bug#884939: mumps: FTBFS on m68k: mpi-fort.pc not found, mpi_* undefined

affects 860599 mumps thanks On Thu, 21 Dec 2017 14:00:36 -0500 "Aaron M. Ucko" wrote: > Source: mumps > Version: 5.1.1-3+b1 > Severity: important > Tags: upstream > Justification: fails to build from source > User: debian-...@lists.debian.org > Usertags: m68k > > Builds of

Re: sasview_4.2.0~git20171031-1_amd64.changes REJECTED

On Sat, 2017-12-23 at 19:00 +, Thorsten Alteholz wrote: > Hi Drew, > > I am sorry, but as CC-Attribution-ShareAlike is not yet listed > in /usr/share/common-licenses/ the full text should be in your > debian/copyright. It's bloody long... -- debian-science-maintainers mailing list

Bug#886715: sasview-doc: unified_power_Rg docs point at _rg not _Rg

Package: sasview-doc Version: 4.2.0~git20171031-3 Severity: normal When clicking on the Help button for the unified_power_Rg model (Shape Independent), sasview looks for unified_power_rg.html (more precisely /usr/lib/python2.7/dist-packages/sas/sasview/doc/user/models/unified_power_rg.html )

Accepted ffc 2017.2.0.post0-1exp1 (source all) into experimental

nce-maintainers@lists.alioth.debian.org> Changed-By: Drew Parsons <dpars...@debian.org> Description: python-ffc - compiler for finite element variational forms (Python 2) python3-ffc - compiler for finite element variational forms (Python 3) Changes: ffc (2017.2.0.post0-1exp1) experimental; ur

Accepted superlu-dist 5.3.0+dfsg1-1 (source amd64) into unstable

<debian-science-maintainers@lists.alioth.debian.org> Changed-By: Drew Parsons <dpars...@debian.org> Description: libsuperlu-dist-dev - Highly distributed solution of sparse linear equations libsuperlu-dist5 - Highly distributed solution of sparse linear equations Changes: superlu-dist (5

Re: dolfin_2017.2.0.post0-1exp1_amd64.changes REJECTED

On Tue, 2018-02-13 at 22:00 +, Thorsten Alteholz wrote: > Hi Drew, > > one of our trainees had a look at your package and found: > * copyright file, while autogenerated and unreadable, incomplete. > missing for example: > test/unit/cpp/mesh/MeshColoring.cpp:// Copyright (C) 2016 Garth >

Re: dolfin_2017.2.0.post0-1exp1_amd64.changes REJECTED

On Wed, 2018-02-14 at 10:47 +0800, Drew Parsons wrote: > On Tue, 2018-02-13 at 22:00 +, Thorsten Alteholz wrote: > > Hi Drew, > > > > one of our trainees had a look at your package and found: > > * copyright file, while autogenerated and unreadable, incomple

Re: dolfin_2017.2.0.post0-1exp1_amd64.changes REJECTED

On Wed, 2018-02-14 at 11:04 +0800, Drew Parsons wrote: > On Wed, 2018-02-14 at 10:47 +0800, Drew Parsons wrote: > > On Tue, 2018-02-13 at 22:00 +, Thorsten Alteholz wrote: > > > Hi Drew, > > > > > > one of our trainees had a look at your package and f

Accepted dolfin 2017.2.0.post0-1exp2 (source all amd64) into experimental, experimental

Urgency: medium Maintainer: Debian Science Team <debian-science-maintainers@lists.alioth.debian.org> Changed-By: Drew Parsons <dpars...@debian.org> Description: dolfin-bin - Executable scripts for DOLFIN dolfin-doc - Documentation and demo programs for DOLFIN libdolfin-dev - Shared link

Accepted dolfin 2017.2.0.post0-2 (source) into unstable

Maintainer: Debian Science Team <debian-science-maintainers@lists.alioth.debian.org> Changed-By: Drew Parsons <dpars...@debian.org> Description: dolfin-bin - Executable scripts for DOLFIN dolfin-doc - Documentation and demo programs for DOLFIN libdolfin-dev - Shared links and header file

Re: Comments regarding petsc_3.8.0+dfsg1-1exp1_amd64.changes

On Sat, 2018-02-24 at 16:07 +, Thorsten Alteholz wrote: > Hi Drew, > > one of our trainess had a look at your package and found the > following > stuff. He is nice and doesn't want to reject the package but just > have > your comments :-). > > Thanks! > Thorsten > Thanks Thorsten. > >

Accepted dijitso 2017.2.0.0-2 (source) into unstable

ers@lists.alioth.debian.org> Changed-By: Drew Parsons <dpars...@debian.org> Description: python-dijitso - distributed just-in-time building of shared libraries (Python 2) python3-dijitso - distributed just-in-time building of shared libraries (Python 3) Changes: dijitso (2017.2.0.0

Accepted ufl 2017.2.0.0-2 (source) into unstable

nce-maintainers@lists.alioth.debian.org> Changed-By: Drew Parsons <dpars...@debian.org> Description: python-ufl - unified language for form-compilers (Python 2) python-ufl-doc - documentation and demos for UFL python3-ufl - unified language for form-compilers (Python 3) Changes: ufl (2017.2.0.0

Accepted instant 2017.2.0.0-2 (source) into unstable

ers@lists.alioth.debian.org> Changed-By: Drew Parsons <dpars...@debian.org> Description: python-instant - simple inlining of C/C++ code in Python 2 python3-instant - simple inlining of C/C++ code in Python 3 Changes: instant (2017.2.0.0-2) unstable; urgency=medium . * debian/control

Accepted fiat 2017.2.0.0-2 (source) into unstable

ers@lists.alioth.debian.org> Changed-By: Drew Parsons <dpars...@debian.org> Description: python-fiat - tabulation of finite element function spaces (Python 2) python3-fiat - tabulation of finite element function spaces (Python 3) Changes: fiat (2017.2.0.0-2) unstable; urgency=medium . * de

Accepted ffc 2017.2.0.post0-2 (source) into unstable

ers@lists.alioth.debian.org> Changed-By: Drew Parsons <dpars...@debian.org> Description: python-ffc - compiler for finite element variational forms (Python 2) python3-ffc - compiler for finite element variational forms (Python 3) Changes: ffc (2017.2.0.post0-2) unstable; urgency=medium . * Up

Accepted petsc 3.8.0+dfsg1-1exp1 (source amd64 all) into experimental, experimental

all Version: 3.8.0+dfsg1-1exp1 Distribution: experimental Urgency: medium Maintainer: Debian Science Maintainers <debian-science-maintainers@lists.alioth.debian.org> Changed-By: Drew Parsons <dpars...@debian.org> Description: libpetsc-complex3.8 - Shared libraries for version

  1   2   >