Bug#842821: transition: hypre
Control: tags -1 confirmed
On 01/11/16 15:07, Drew Parsons wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: transition
>
> I've worked to get an updated dolfin (python-dolfin) in the
> archive. I've been upgrading the libraries it uses one by one. petsc
> is the important one.
>
> But hypre (used by petsc) was quite old. It seemed dissonant to have
> the other libraries updated while hypre was still old.
>
> I've prepared an update for hypre 2.11.1, now uploaded to experimental
> (i.e. currently in the NEW queue).
>
> I've confirmed petsc will build (and run) with the new hypre. i.e. I
> have the patch for it ready.
>
> elmer is the only other client with Build-Depends: libhypre-dev, but
> it's failing to build anyway, regardless of any hypre upgrade. A new
> version of elmer has been stuck in experimental for 3 years. The elmer
> build configuration will need to recognise the new location of the
> hypre headers in /usr/include/hypre.
>
> code-aster-mpi-engine gets an indirect dependency on the hypre library
> binary via petsc, so should not cause a problem.
>
> Given the time needed to get through NEW, it may not be able to hit
> unstable before 5 November, but I hope we can authorise this transition.
Yes, this is fine. elmer is not in testing anyway, so there's basically one rdep
and you maintain it. You can go ahead (after it clears NEW).
Cheers,
Emilio
Reply to: