Bug#985228: unblock: petsc/3.14.5+dfsg1-2

[Ivo De Decker <ivodd@debian.org>]

Control: tags -1 moreinfo

Hi,

On Sun, Mar 14, 2021 at 09:01:26PM +0100, Drew Parsons wrote:
> upstream released petsc 3.14.5 with bug fixes only.
> This will help improve the stability of the package over the lifetime
> of the bullseye release.

I'm not convinced this complies with the freeze policy (but see below).

> This update also fixes Bug#983892, fixing orphaned alternatives after
> removal of libpetsc64-complex3.14-dev,
> 
> [ Impact ]
> 
> If this release is not permitted into stable then some users may
> encounter the issues addressed by the patch, especially when running
> under MPI parallelization.  A range of bugs have been addressed:
> - MatBAIJ: Fix specialization for size 9
> - Do not use MPI_Bcast() on a single rank.
> - PCHPDDM: fix for KSPLSQR
> - DMPlexVTKWriteAll_VTU: a couple of bugfixes
> - handling error conditions in PetscOptions
> - handling NULL objects in Fortran interface
> - bugfix for MatMatMultSymbolic_MPIAIJ_MPIDense() 
> - CPARDISO: stick to OpenMPI BLACS when needed
> - minor Documentation fixes

> If the release is not allowed into stable then
> libpetsc64-complex3.14-dev will leave dangling alternatives links when
> removed.

This specific issue could be fixed without switching to a new upstream version
(as was done initially in 3.14.4+dfsg1-2).


> [ Tests ]
> 
> debian/tests autopkgtest is enabled.
> petsc debci tests have passed in unstable.
> 
> debci tests in client packages are also passing successfully in unstable
> (petsc4py, slepc, slep4py, deal.ii, dolfin, mshr, dolfinx)
> 
> sundials continues to build successfully.
> 
> [ Risks ]
> 
> The patch fixes a range of bugs, it is not a simple one-line patch.

> [ Checklist ]
>   [-] all changes are documented in the d/changelog
>       - documented as "New upstream release (bugfixes)"
>   [x] I reviewed all changes and I approve them
>   [ ] attach debdiff against the package in testing

We ask these this for a reason. The current diff between the version in
testing and unstable is very large and unreviewable. It certainly isn't going
to get unblocked like this. If you can provide a filtered diff, with only the
'real' changes, and not the noise generated by the new upstream release,
there's at least a chance we could look at them. Note that this doesn't
guarantee it will be unblocked. There's still a decent chance that the changes
will be too big.

Thanks,

Ivo