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
Processing commands for cont...@bugs.debian.org:
> tags 822971 + fixed pending
Bug #822971 [src:dolfin] dolfin: FTBFS on kfreebsd
Added tag(s) fixed and pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
822971: http://bugs.debian.org/cgi-bin/bugreport.cgi?b
On Thu, Oct 06, 2016 at 04:52:04PM +0800, Drew Parsons wrote:
> On Sat, 17 Sep 2016 11:29:54 +0800 Drew Parsons
> 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
> kfreeb
On Sat, 17 Sep 2016 11:29:54 +0800 Drew Parsons
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 mailing list
debian-science-maintainers@
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
other build-dependenci
Source: dolfin
Version: 1.6.0-4
Control: block 822321 by -1
Since this version, with the switch to vtk6 and whatnot, dolfin FTBFS on
kfreebsd.
This unfortunately jeopardize our quest to remove vtk5 from the archive,
as the old binaries there still depends on it.
Please try to see what causes suc
