Bug#996507: trilinos-all-dev: No rule to make target '/usr/lib/x86_64-linux-gnu/libdl.so'

Package: trilinos-all-dev Version: 12.18.1-2 Severity: normal X-Debbugs-Cc: nico.schloe...@gmail.com Dear Maintainer, First of all, I need to say because I'm partly responsible for making this a "monster" package of packages. It really should have been a libtrilinos-dev with no subpackaging,

Bug#996336: pygalmesh: autopkgtest regression on i386

Yeah, that's a little weird. And it only occurs on i386? Sounds like a CGAL bug then. On Wed, Oct 13, 2021 at 3:24 PM Drew Parsons wrote: > > On 2021-10-13 13:42, Nico Schlömer wrote: > > Or PR upstream. I can merge and release any time. > > Thanks Nico. I'll check which t

Bug#996336: pygalmesh: autopkgtest regression on i386

Or PR upstream. I can merge and release any time. Cheers, Nico On Wed, Oct 13, 2021 at 1:39 PM Drew Parsons wrote: > > Not entirely unexpected. Upstream reorganized tests and tolerances, so > I wanted to check if we had a full pass or not. > Looks like we'll have to reinstate

Bug#961414:

FYI, I've added an Ubuntu PPA for it. Cheers, Nico [1] https://launchpad.net/~nschloe/+archive/ubuntu/waybar

Bug#964078: Error during setup, bad file location

Upstream dev here. The location is ``` share/paraview-5.8/plugins ``` now, that's already for 4.0.16. Cheers, Nico On Mon, Jul 20, 2020 at 9:03 AM Drew Parsons wrote: > > Package: meshio-tools > Followup-For: Bug #964078 > > Thanks for your report. Looks like the symlink might not be created >

Bug#951864: pygalmesh fails it's own autopkg tests

The test tolerance has already been relaxed for Debian in the latest release. On Sat, Feb 22, 2020 at 2:48 PM Matthias Klose wrote: > > Package: src:pygalmesh > Version: 0.5.0-4 > Severity: serious > Tags: sid bullseye > > pygalmesh fails it's own autopkg tests: > > [...] > autopkgtest

Bug#947058: pygalmesh: autopkgtest failure on arm64 (and ppc64el, s390x)

Just can just relax the relative tolerance to 2.0e-3 with a patch, I'll include in the next release. Cheers, Nico On Mon, Dec 30, 2019 at 3:27 PM Graham Inggs wrote: > > Control: reopen -1 > > Hi Drew > > The test gets a little further [1], and now fails at: > >

Bug#946590: python3-dolfin: cannot find -lmpi

Package: python3-dolfin Version: 2019.1.0-7 Severity: normal I don't know if this is a bug in the package or in my system. With the simplest of python dolfin projects, I'm getting ``` --- Start compiler output /usr/bin/ld: cannot find -lmpi collect2:

Bug#946234: [NMU] FTFBS with CGAL 5.0 (if cmake is absent)

It's fixed upstream, I released a new version and Drew is on it bumping the version in Debian. [1] [1] https://github.com/nschloe/pygalmesh/issues/56 On Fri, Dec 6, 2019 at 2:30 PM Joachim Reichel wrote: > > > Upstream 0.5.0 now builds against CGAL 5, so we only need an upload here. > > What do

Bug#946234:

Upstream 0.5.0 now builds against CGAL 5, so we only need an upload here.

Bug#946189: python-numpy: blas -> blis

Package: python-numpy Version: 1.16.0 Severity: wishlist Since version 1.17.0, numpy's own blas detection order is mkl,blis,openblas,atlas,accelerate,blas The first one available on Debian is BLIS, so perhaps it's time to think about replacingthe BLAS dependency with BLIS. Cheers, Nico --

Bug#944361: cgal: cgal 5.0 released

Alright, thanks for the update! (I didn't even know there was discussion about git atm.) On Fri, Nov 8, 2019, 5:40 PM Joachim Reichel wrote: > tag 944361 +pending > thanks > > Hi, > > I did not see any release announcement for CGAL 5.0 final yet, only for > Beta 2. > > Thanks for your offer to

Bug#944361: cgal: cgal 5.0 released

Package: libcgal-dev Version: 4.14-5 Severity: wishlist File: cgal CGAL 5.0 has been released this afternoon. I'd love to take a stab at it, but apparently the debian sources aren't on salsa yet. Any chance of moving them there? -- System Information: Debian Release: buster/sid APT prefers

Bug#942675: meshio not compatible with python 3.8, installation fails

I've fixed this upstream in 3.2.2, upload coming in soon. On Sat, Oct 19, 2019 at 11:51 PM Matthias Klose wrote: > > Package: src:python-meshio > Version: 3.1.6-1 > Severity; serious > Tags: sid bullseye > > Trying to setup the package with pytho3-defaults installed from experimental, > the

Bug#939326: [gmsh] Could you please restore MED support?

Upstream recommends against using MPI [1], so we should probably stick to that. You can always use meshio [2] to convert between mesh formats. Cheers, Nico [1] https://gitlab.onelab.info/gmsh/gmsh/issues/502#note_6582 [2] https://github.com/nschloe/meshio On Tue, Sep 3, 2019 at 1:51 PM

Bug#933995: ITP: Mmg

Package: mmg Version: 5.4.1-201908051833-1eoan1 Severity: wishlist I intent to package Mmg [1], a (scientific) mesh generator and optimizer. It produces pretty high-quality 3D meshes, is open-source and well-supported by its GitHub upstream [2]. I'm working on this in a salsa repo [3]. Cheers,

Bug#929390: VTK 8

Package: vtk7 Version: VTK 8 is now out for about two years (June 2017). Perhaps we should start supporting it?

Bug#928140: pygalmesh: FTBFS on 32-bit architectures: virtual memory exhausted

cf. https://stackoverflow.com/questions/55801777/set-compile-flags-when-installing-python-c-project On Fri, May 3, 2019 at 10:29 AM Drew Parsons wrote: > > On 2019-05-03 16:24, Nico Schlömer wrote: > >> Do you know how to control it? > > > > I'd been looking at this

Bug#928140: pygalmesh: FTBFS on 32-bit architectures: virtual memory exhausted

> Do you know how to control it? I'd been looking at this once, to no avail. Locally I just use CC=clang++ now. On Fri, May 3, 2019 at 10:11 AM Drew Parsons wrote: > > On 2019-04-29 15:49, Nico Schlömer wrote: > >> No easy way around it. > > > > Indeed. > &g

Bug#928140: pygalmesh: FTBFS on 32-bit architectures: virtual memory exhausted

> No easy way around it. Indeed. > Building with -g -O1 (or -O2 without -g) helps mshr, we can test if it helps > pygalmesh too. Removing `-g` almost certainly improves things. Using clang++ instead of c++ also helps. On Mon, Apr 29, 2019 at 9:06 AM Drew Parsons wrote: > > Source: pygalmesh

Bug#927808: gmsh: FTBFS in buster (c++: error: unrecognized command line option '-Wint-to-void-pointer-cast')

This could all be fixed in master (where we have Gmsh 4.3.0). Should perhaps be uploaded soon. On Wed, Apr 24, 2019 at 8:33 PM Juhani Numminen wrote: > > Control: retitle -1 gmsh: FTBFS in buster > ("/usr/include/occt/Standard_Version.hxx" cannot be read) > > > Hi, > > I believe the relevant

Bug#907844:

As a side note: Can we include the optional dependency on PETSc for the new Gmsh? I'm getting mesh generation errors without (see https://github.com/nschloe/pygmsh/pull/214). Cheers, Nico On Tue, 4 Sep 2018 07:29:46 +0200 =?UTF-8?Q?Nico_Schl=C3=B6mer?= < nico.schloe...@gmail.com> wrote: > Where

Bug#907920: use optional PETSc dependency

Package: hello Version: 3.0.6+dfsg1-3 When building some meshes, I'm getting ``` Error : Petsc is required (we do need complex in discreteFace::crossField()) ``` followed a double free or corruption. See, e.g., < https://github.com/nschloe/pygmsh/pull/214>. Please include the dependency on

Bug#907844:

Where can I find this work. (Need Gmsh 4 for another project.) Cheers, Nico

Bug#895419: Acknowledgement (python3-dolfin: JIT compilation fails as python3-instant tries to includes petsc4py from python2)

I've had that issue in the past, but never bothered looking into it. Me, I'll hold out for 2018.1 (which kills Python 2 support) to fix these kind of bugs. Cheers, Nico On Fri, Apr 13, 2018 at 4:54 PM Fabrice Silva wrote: > Additional information from Johannes Ring

Bug#890364:

I depend on this as well. As a stop-gap measure, I've set of a PPA [1]. Cheers, Nico [1] https://launchpad.net/~nschloe/+archive/ubuntu/pybind11-backports/

Bug#712485:

Perhaps it's useful to report which are the offending lines in the build log. For Trilinos [1], for example, a hidden flags are reported, but I have no idea why. Can you help me out? Cheers, Nico [1] https://buildd.debian.org/status/fetch.php?pkg=trilinos=amd64=12.12.1-5=1517856320=0

Bug#889682: openimageio: Provide Python 3 interface

Package: libopenimageio-dev Version: 1.6.17~dfsg0-1ubuntu5 Severity: normal File: openimageio OpenImageIO supports Python 3 for a while now. Please provide the respective package in Debian. -- System Information: Debian Release: stretch/sid APT prefers artful-updates APT policy: (500,

Bug#881881: libtrilinos-kokkos-kernels-dev: fails to upgrade from 'testing' - trying to overwrite /usr/include/trilinos/Kokkos_ArithTraits.hpp

Ah, yes, these files seem to have moved from Tpetra to Kokkos. These two upstream packages are tightly related, so no surprise there. I'll see if I can get this fixed. Cheers, Nico On Thu, Nov 16, 2017 at 2:15 AM Andreas Beckmann wrote: > Package:

Bug#881873: trilinos: FTBFS on sparc64: Bus errors in 11 tests

Chances are slim for to ever be resolved. Upstream only supports amd64, and PRs to fix building for other architectures are rejected. (See, e.g., [1].) I'd say we'll have to live with trilinos not running on sparc64. Cheers, Nico [1] https://github.com/kokkos/kokkos/pull/576 On Thu, Nov 16,

Bug#880964: closed by Guido Günther <a...@sigxcpu.org> (Re: Bug#880964: git-buildpackage: non-ascii character in d/changelog: UnicodeDecodeError)

com/a/42792413/353337 On Mon, Nov 6, 2017 at 4:03 PM Guido Günther <a...@sigxcpu.org> wrote: > Hi, > On Mon, Nov 06, 2017 at 02:53:11PM +, Nico Schlömer wrote: > > Thanks for following up on this. > > > > > But this is not Python2. > > > > This is th

Bug#880964: closed by Guido Günther <a...@sigxcpu.org> (Re: Bug#880964: git-buildpackage: non-ascii character in d/changelog: UnicodeDecodeError)

, 2017 at 02:21:16PM +, Nico Schlömer wrote: > > I've tried with 0.9.1 and I'm getting the same error. The error message > > makes sense too: In `_run_parsechangelog` one finds > > Then please provide steps to reproduce. > > > ``` > > self._contents.encod

Bug#880964:

Digging further, I found that the error can be fixed with ``` io.open(self.filename, mode='r', encoding='utf-8') ``` in `_read`, just as described in [1]. Note that ``` self._contents.encode() ``` needs to become ``` self._contents.encode('utf-8') ``` then, too. [1]

Bug#880964: closed by Guido Günther <a...@sigxcpu.org> (Re: Bug#880964: git-buildpackage: non-ascii character in d/changelog: UnicodeDecodeError)

Cc: > Bcc: > Date: Mon, 6 Nov 2017 14:27:19 +0100 > Subject: Re: Bug#880964: git-buildpackage: non-ascii character in > d/changelog: UnicodeDecodeError > Version: git-buildpackge/0.9.1 > > Hi, > On Mon, Nov 06, 2017 at 02:17:29PM +0100, Nico Schlömer wrote:

Bug#880964: git-buildpackage: non-ascii character in d/changelog: UnicodeDecodeError

Package: git-buildpackage Version: 0.8.18 Severity: important When running ``` gbp import-orig --uscan --pristine-tar ``` on the gmsh package, gbp bails out with the error message ``` UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 399: ordinal not in range(128) ``` referring

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

n 24/07/2017 10:40, Nico Schlömer wrote: > > Sounds more like a gAM bug then. Can this be closed? > > I intentionally didn't close this bug because the tests still fail if > they are enabled. > > If the problem is caused by another package, then this bug should be > r

Bug#853679:

With tbb 2017~U7-2 in experimental, this can probably be closed now. Cheers, Nico

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

> Still comes out corrupted in the gnome Archive Manager, but extracts fine on the command line. Sounds more like a gAM bug then. Can this be closed? Cheers, Nico On Mon, Jul 17, 2017 at 4:33 AM Drew Parsons wrote: > On Mon, 17 Jul 2017 10:21:03 +0800 Drew Parsons

Bug#868873: dependence on libmumps-4.10.0 _AND_ libmumps-5.1.1 breaks make

Thanks, Graham, for the analysis. It appears that with 12.10.1-4 we're on top of things, so I guess this can be closed. Cheers, Nico On Sun, Jul 23, 2017 at 9:51 PM Graham Inggs <gin...@debian.org> wrote: > On 23 July 2017 at 18:07, Nico Schlömer <nico.schloe...@gmail.com> wrote

Bug#868873: dependence on libmumps-4.10.0 _AND_ libmumps-5.1.1 breaks make

Hm, funny! I don't get how libtrilinos-amesos12 should depend on libmumps-4.10.0 when 5.1.1 is available. I've rebuild this on ubuntu artsy [1] and it selects all the right versions. Perhaps this got corrupted in the transition somehow? We've recently uploaded 12.10.1-4, perhaps this rebuild will

Bug#868894: find_package option COMPONENTS ineffective because of hard-coded includes in TrilinosConfig.cmake

Thanks, Joachim, for the report! This definitely sounds like an upstream bug. Would you mind reporting it on [1]? Together with the Trilinos devs, we'll be able to take it from there. That being said, at first glance the inclusion of the subpackage configs doesn't seem to override anything. I'd

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

I've disabled the phalanx tests in master, and also fixed two other things. Perhaps it's time for an upload? Cheers, Nico On Sun, Jul 16, 2017 at 2:16 PM Nico Schlömer <nico.schloe...@gmail.com> wrote: > The issue was reported to upstream in May [1]. I think until we get a fix, &g

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

The issue was reported to upstream in May [1]. I think until we get a fix, it's best to disable that specific test. Cheers, Nico [1] https://github.com/trilinos/Trilinos/issues/1332 On Sun, Jul 16, 2017 at 1:51 PM Graham Inggs wrote: > On 16 July 2017 at 13:12, Drew

Bug#866678: libtbb-dev: upstream on github

Package: libtbb-dev Version: 4.4~20160526-0ubuntu2 Severity: minor The watch file still points to https://www.threadingbuildingblocks.org/download https://www.threadingbuildingblocks.org/sites/default/files/software_releases/source/tbb([0-9_]+)oss_src\.tgz but upstream has moved to GitHub [1] a

Bug#864779: Epetra doc missing

Let me add also that Epetra isn't that important anymore. Trilinos devs try to get people to switch over to Tpetra, and in fact Epetra hasn't seen substantial development in many years now. Cheers, Nico On Thu, Jun 15, 2017 at 5:22 PM Nico Schlömer <nico.schloe...@gmail.com> wrote: &g

Bug#864779: Epetra doc missing

Thanks Joachim for report. This is more of an upstream issue, see [1]. Once that is done, the package will have the Epetra documentation shipped. Cheers, Nico [1] https://github.com/trilinos/Trilinos/issues/1431 On Wed, Jun 14, 2017 at 6:42 PM Joachim Wuttke wrote: >

Bug#863760: dput-ng: document return codes

Package: dput-ng Severity: minor dput-ng often fails to upload with output like ``` dput -c /path/to/dput.cf mypackage mypackage_1.0.0-1xenial1_source.changes Return code: 3 Output: None ``` The return code may differ, and it's always unclear what it actually means. Please document dput-ng's

Bug#863723: dput-ng: skip `please login: To accept ssh-rsa hostkey [...]`

Package: dput-ng Version: 1.8 Severity: wishlist I'm using dput-ng for submitting builds to launchpad via sftp. Every time I submit, I have to answer the question ``` please login: To accept ssh-rsa hostkey 6b03de9833252318a646b34722cd54f2 for ppa.launchpad.net type "yes": [yes, no]: ``` That

Bug#862111: python-slepc4py: Python 3 support

Package: python-slepc4py Version: 3.7.0-2build3 Severity: wishlist slepc4py is compatible with Python 3.2 and up (see [1]), and it'd be nice to this reflected in the package. [1] https://bitbucket.org/slepc/slepc4py -- System Information: Debian Release: stretch/sid APT prefers

Bug#862110: python-petsc4py: Python 3 support

Package: python-petsc4py Version: 3.7.0-2build1 Severity: wishlist petsc4py is compatible with Python 3.2 and up (see [1]) and it'd be nice to see this reflected in the package. [1] https://bitbucket.org/petsc/petsc4py -- System Information: Debian Release: stretch/sid APT prefers

Bug#810254:

Hi everyone, I did some work on this in the last few days and I got to something. As requested, it's all committed to the vtk6 repo (and also available from [1]). As far as I can tell, it's all in good order. I'm already running a bunch of applications against it with no nasty surprises so far.

Bug#860231: libxdmf-dev: update XDMF from Git

Package: libxdmf-dev Severity: wishlist Dear Maintainer, I'm currently in the process of packaging VTK7, and it depends on XDMF3. It does require a version newer than git20160803 however, so I'd be great if that could be updated from upstream. Cheers, Nico -- System Information: Debian

Bug#651527:

I've had the same error message and definitely isn't a space issue. Apparently, my input FLAC file was broken (?), but I could work around the problem by * converting the sound file to another lossless format, e.g., `ffmpeg -i input.flac input.wav` and * using shnsplit on the new input file.

Bug#854624: fenics: vcs information incorrect

Package: fenics Version: 1:2016.2.0.1~ppa1~yakkety Severity: minor Tags: newcomer Dear Maintainer, on [1], the VCS is still listed as SVN and has a dysfunctional link. This should be updated to the new Git repo (in debian/control). Cheers, Nico [1] https://tracker.debian.org/pkg/fenics --

Bug#810254:

gt; > thanks for your contribution! We will definitely upload VTK7 after > Stretch will be released. Feel free to commit into the alioth > into the vtk7-branch. > > Best regards > > > Anton > > 2017-02-04 10:54 GMT+01:00 Nico Schlömer <nico.schloe...@gmail.com>: >

Bug#810254:

Alright, so I've spend last night packaging VTK7 (nightly master) [1]. It's basically a clone of the vtk6 package with a bunch of fixes. Will have to be tested some more, but for certain it's already a better-than-nothing. Comments and PRs are more than welcome; the code is on GitHub [2].

Bug#851833: binary-or-shlib-defines-rpath too strict

Package: lintian Version: 2.5.48 Severity: normal Since recently, I'm seeing a lot of binary-or-shlib-defines-rpath [1] errors from lintinan on Trilinos [2]. It says in the description of the warning: ``` To fix this problem, look for link lines like: gcc test.o -o test

Bug#851787: exodusii: integrate exodusii into trilinos?

Package: exodusii Severity: minor Exodus is developed as part of SEACAS [1] for a while now. While separate releases are still being published [2], it might make more sense to use the Trilinos package [3] to provide SEACAS and Exodus. Thoughts? [1]

Bug#848770: trilinos: FTBFS: Test failures

Thanks Lucas for the report. A new version (12.10.1-2) has already been submitted to NEW, fixing the test failures. Cheers, Nico On Mon, Dec 19, 2016 at 10:43 PM Lucas Nussbaum wrote: > Source: trilinos > Version: 12.10.1-1 > Severity: serious > Tags: stretch sid > User:

Bug#835406: trilinos: FTBFS on 32-bit architectures

rg> wrote: > On 9 December 2016 at 09:49, Nico Schlömer <nico.schloe...@gmail.com> > wrote: > > The patch looks really simple. Great! Do you think it'd be worthwhile > > updating the PR [1] (or opening a new one)? Perhaps the kokkos devs can > > figure out why th

Bug#835406: trilinos: FTBFS on 32-bit architectures

The patch looks really simple. Great! Do you think it'd be worthwhile updating the PR [1] (or opening a new one)? Perhaps the kokkos devs can figure out why the remaining tests are failing. Cheers, Nico [1] https://github.com/kokkos/kokkos/pull/410 On Fri, Dec 9, 2016 at 8:18 AM Graham Inggs

Bug#835406: trilinos: FTBFS on 32-bit architectures

t 2016 at 21:55, Nico Schlömer <nico.schloe...@gmail.com> > wrote: > > When uploading, we could perhaps also include the point release 12.6.4. > > (Current Debian is 12.6.3.) > > Sure, let's do that. > > Do you have time now to prepare 12.6.4 for upload? I can reba

Bug#835406: trilinos: FTBFS on 32-bit architectures

> I have successfully built trilinos on i386 and armhf, This is amazing! We can certainly upstream those patches, too. When uploading, we could perhaps also include the point release 12.6.4. (Current Debian is 12.6.3.) Cheers, Nico On Mon, Aug 29, 2016 at 5:09 PM Graham Inggs

Bug#835857: swig3.0: SWIG version bump

Package: swig3.0 Version: 3.0.8-0ubuntu3 Severity: wishlist Dear Maintainer, SWIG 3.0.10 has been released (https://sourceforge.net/projects/swig/files/swig/). Please bump. Cheers, Nico -- System Information: Debian Release: stretch/sid APT prefers xenial-updates APT policy: (500,

Bug#831790: fenics: version bump (2016.1.0)

Package: fenics Version: version bump Severity: wishlist FEniCS 2016.1.0 has been released recently (cf. https://fenicsproject.org/download/); note that the versioning scheme has changed. Bump in Debian, please. -- System Information: Debian Release: stretch/sid APT prefers xenial-updates

Bug#831788: OSError: libmpi.so.1: cannot open shared object file: No such file or directory

Package: python-gmsh Version: 2.10.1+dfsg1-1ubuntu4 Severity: normal Dear Maintainer, The python-gmsh appears to be broken: ``` $ python -c "import gmshpy" Traceback (most recent call last): File "", line 1, in File "/usr/lib/python2.7/dist-packages/gmshpy/__init__.py", line 3, in mpi

Bug#830681: trilinos-all-dev: Updating binutils breaks trilinos

I've tested and pushed a build without binutils. @Graham, would you like to upload? Cheers, Nico On Mon, Jul 18, 2016 at 1:26 PM Felix Salfelder <fe...@salfelder.org> wrote: > On Mon, Jul 18, 2016 at 11:18:30AM +0000, Nico Schlömer wrote: > > [binutils] just turn it off > &

Bug#830681: trilinos-all-dev: Updating binutils breaks trilinos

The binutils support in trilinos is far from being critical, so I'd say for making things a little easier we just turn it off. @Felix Agreed? Cheers, Nico On Fri, Jul 15, 2016 at 12:15 AM Helmut Grohne wrote: > On Sun, Jul 10, 2016 at 01:04:13PM +0200, Felix Salfelder

Bug#825824: libmumps-dev: MUMPS 5.0.1 version bump

Package: libmumps-dev Version: 4.10.0.dfsg-4 Severity: wishlist MUMPS 5.0.1 has been released a while ago. Please bump. -- System Information: Debian Release: stretch/sid APT prefers xenial-updates APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 'xenial'), (100,

Bug#815725:

Trilinos, specifically Kokkos, only support 64bit-architectures. The build failure on i386 is therefore expected. I've compiled trilinos on ppc64el and could no reproduce the error [1]. Perhaps that's something that's accidentally been fixed in the meantime? Cheers, Nico [1]

Bug#558777:

I got bitten by this as well with SuperLU, the upstream tarball being named `superlu_5.2.0.tar.gz`. Mathieu Parent's hint of using ``` git-import-orig --uscan --upstream-version=$version+dfsg ``` helped me out.

Bug#823213: superlu: major version bump

Source: superlu Severity: wishlist Dear Maintainer, SuperLU 5.0 has been released on July 26, 2015, and version 5.2.0 on April 8, 2016. Please bump. -- System Information: Debian Release: stretch/sid APT prefers xenial-updates APT policy: (500, 'xenial-updates'), (500, 'xenial-security'),

Bug#822972: audioread: version bump

Package: python-audioread Version: version bump (2.1.2) Severity: wishlist The audioread version shipped with Debian is rather old now (1.0.2). The latest release (from Jan 2016) is 2.1.2. Please bump. -- System Information: Debian Release: stretch/sid APT prefers xenial-updates APT

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

Package: python-dolfin Severity: normal Dear Maintainer, python-dolfin depends on the unmaintained python-netcdf. Keeping the dependency has serious implications. For example, since python-netcdf is no longer included in Ubuntu 16.04, so isn't FEniCS. For this reason, please consider removing

Bug#822057: gl2ps 1.3.9 released

Source: gl2ps Severity: wishlist GL2PS 1.3.9 has been released on Oct 17, 2015 [1]. The new VTK 7 (not yet in Debian) will require it, so it'd be great if we could bump the version here. [1] http://www.geuz.org/pipermail/gl2ps-announce/2015/22.html -- System Information: Debian Release:

Bug#810254: VTK 7

VTK 7 has meanwhile been released (Feb 2, 2016, [1]). Particularly interesting: Support for Python 3 has finally landed. [1] https://blog.kitware.com/vtk-7-0-0/

Bug#748490: MongoDB 2.4 EOL

As a heads-up, Mongo 2.4's life cycle ends in March 2016 [1], i.e., three months. Cheers, Nico [1] https://www.mongodb.com/support-policy

Bug#805010: VTK 6.3.0 released

Source: vtk6 Severity: wishlist Dear Maintainer, VTK 6.3.0 has been released on Sep 10, 2015 [1]. Please bump. Cheers, Nico [1] http://www.kitware.com/blog/home/post/963 -- System Information: Debian Release: jessie/sid APT prefers wily-updates APT policy: (500, 'wily-updates'), (500,

Bug#704782: trilinos: new package for Trilinos 11.x

Hi everyone! I indeed still maintain the PPA [1]. These builds are nightlies of the Trilinos repo (a clone is [2], but their plan is to entirely switch to GitHub by the end of the year) with the debian folder of [3] (branch: debian). Most of the work for this was done by Felix and me, but as

Bug#796985: libopenmpi-dev: invalid suffix on literal; C++11 requires a space between literal and string macro

Package: libopenmpi-dev Version: 1.6.5-9.2 Severity: normal Tags: patch When using Open MPI 1.6 with `-std=c++11`, one gets flooded with warnings of the kind ``` /usr/lib/openmpi/include/mpi_portable_platform.h:374:63: warning: invalid suffix on literal; C++11 requires a space between literal and

Bug#796982: openmpi-bin: openmpi 1.10 released

Package: openmpi-bin Version: 1.6.5-9.2 Severity: normal Tags: newcomer Open MPI 1.10.0 has been released yesterday, meaning that the version 1.6 currently in Debian is now prior-prior-stable and won't be maintained upstream for much longer (if at all). The upgrade to 1.8 or 1.10 should hence be

Bug#792280:

GCC-XML has been deprecated [1], it's developers recommend CastXML. Since this is already in Debian [2], we might think about dropping GCC-XML from Debian altogether. Cheers, Nico [1] https://gccxml.github.io/HTML/Index.html [2] https://packages.debian.org/sid/castxml -- To UNSUBSCRIBE,

Bug#789169: libvtk6-dev: fix upstream Xdmf3 build bug

-source was dropped from Debian for vtk6_6.2.0, so I am not able to apply the patch. But it looks like release candidate of vtk6 is already available. So your patch will be there. Thus I am reducing the bug`s severity. Thanks Anton 2015-06-18 7:30 GMT-07:00 Nico Schlömer nico.schloe

Bug#753001: openmpi: New upstream version 1.8 available

Package: libopenmpi-dev Version: 1.6.5-9.2 Followup-For: Bug #753001 Is anyone still on this? -- System Information: Debian Release: jessie/sid APT prefers vivid-updates APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), (100, 'vivid-backports') Architecture:

Bug#789168: libvtk6.1: provide MPI capabilities

Package: libvtk6.1 Severity: normal Tags: patch Dear Maintainer, VTK currently builds in serial mode. To unlock the capabilities offered by MPI (like parallel I/O), we need to depend on hdf5-mpi-dev (instead of hdf5-dev) and use the MPI compilers to build VTK. (We already depend on MPI for

Bug#789169: libvtk6-dev: fix upstream Xdmf3 build bug

(x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.0-18-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) commit a98527dfe9ce23beebf386fab07caef99b911ede Author: Nico Schlömer

Bug#746805: transition: gfortran module version changing from 10 to 12

I'd be happy to push the netcdfc package to alioth tomorrow. Do cdftools and flexpart require the Fortran or C++ bindings as well? (Those are now separate packages.) Cheers, Nico On Wed, May 7, 2014 at 9:16 PM, Alastair McKinstry alastair.mckins...@sceal.ie wrote: On 03/05/2014 21:18, Matthias

Bug#354463:

This is definitely a bug in Debian's LAPACK. $ nm /usr/lib/libblas/libblas.a | grep xerbla_ T xerbla_ shows that the symbol xerbla_ is defined the static BLAS library. Additionally, $ nm /usr/lib/liblapack.a | grep xerbla_ [...] T xerbla_ it is defined in

Bug#703729:

As discussed on IRC, neither of HYPRE and Trilinos should install files in /usr/include directly. The homework here would be to make sure that the headers are installed into /usr/include/hypre/.

Bug#704782: trilinos: new package for Trilinos 11.x

Source: trilinos Severity: wishlist Dear Maintainer, I'm working on a package for Trilinos 11.x, and things are shaping up nicely: I and a bunch of other people have been using the package at https://launchpad.net/~nschloe/+archive/trilinos-nightly

Bug#703729: libhypre-dev: bundled header fei_defs.h prevents orginal software from being packaged

Package: libhypre-dev Version: 2.8.0b-1 Severity: normal Tags: upstream Dear Maintainer, I'm currently packaging the Trilinos numerical solver package and just bumped into a filename conflict with the package libhypre-dev about the file fei_defs.h. Apparently, Hypre (upstream) just copied this