[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ongoing slepc/petsc transition

On Tue, 2012-01-24 at 00:51 +0100, Cyril Brulebois wrote:
> Adam C Powell IV <hazelsct@debian.org> (23/01/2012):
> > deal.II detects the PETSc version and acts accordingly, I believe 7.1.0
> > will work through 3.2.  I need to work on upgrading from 7.0.0 to 7.1.0.
> […]
> > Illuminator has major problems -- the PETSc object on which all of
> > illuminator is based has changed drastically.  This will require major
> > upstream surgery, and the new version will not be data-compatible with
> > the old.
> > 
> > Since upstream is me, I can tell you I will not have time for the
> > foreseeable future (couple of months at least) to port illuminator to
> > PETSc 3.2.  It will need to come out of testing when PETSc
> > transitions. :-(
> […]
> > Can't speak for the others (dolfin, feel++, gmsh).
> That means one “OK-able” package, one “oops-broken-for-a-long-while”
> package, and several “unknown-status” packages. To keep everyone as
> testing candidates until this transition is ready, maybe re-uploading
> petsc 3.1 would do the trick? (Either with an epoch or with the
> 3.2-is-really-3.1-like dirty version.) This way, all packages can stay
> in testing and be updated through unstable w/o having to be entangled?

I think we're closer than that, we've been active for the past couple of
weeks to make this happen.  The only unknown at this point is feel++.
Stuff to do looks like:
      * Upload a new petsc to fix some bugs (me, probably today)
      * Upload a new slepc with a tiny patch to add a header file (me,
        probably today)
      * Upload mpich2 from alioth to fix an RC bug (me, today or
      * Update to deal.II 7.1.0 (me, within a week)
      * Patch gmsh to work with petsc/slepc 3.2 (Christophe Trophime
        with my help, probably within a week)
      * Update DOLFIN (Johannes Ring, within a week)
      * Test/update feel++ (?? If nobody else I'll take a stab at it)
      * Remove illuminator from testing (release team)
      * Close the RC bug against mpi-defaults (which is pointless anyway
        because it transitioned just before I filed it, I'll do this

It looks like there's a clear path to success, and this can all happen
within a week or two, then we can transition a bunch of stuff at once
including HDF5.  Otherwise we're stuck trying to do two transitions
which will take at least 4 weeks...

Makes sense?

GPG fingerprint: D54D 1AEE B11C CE9B A02B  C5DD 526F 01E8 564E E4B6

Engineering consulting with open source tools

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: