Control: forwarded -1 https://release.debian.org/transitions/html/auto-petsc.html Control: tags -1 pending Hi Drew, On 01-08-2019 05:45, Drew Parsons wrote: > The hypre 2.16.0 upgrade revealed an incompatibility between petsc 3.10 > and hypre 2.16.0. PETSc upstream has dealt with the issue with a > couple of recent patches. The best way to stabilise hypre and petsc > is to proceed with the petsc 3.11 transition. > > The slepc 3.11 transition should be considered part of this > transition. I'm also upgrading dolfin to 2019.1.0 (which is really a > just a fenics upgrade rather than a library transition). > > A mumps 5.2.0 transition is waiting, but I'll wait for this one to > clear before starting that. > > Ben file: > > title = "petsc"; > is_affected = .depends ~ /\b(libpetsc\-complex3\.11|libpetsc\-complex3\.11\-dbg|libpetsc\-complex3\.11\-dev|libpetsc\-real3\.11|libpetsc\-real3\.11\-dbg|libpetsc\-real3\.11\-dev|libpetsc3\.11\-dev\-common|libpetsc3\.11\-dev\-examples|petsc3\.11\-doc|libpetsc\-complex3\.10|libpetsc\-complex3\.10\-dbg|libpetsc\-complex3\.10\-dev|libpetsc\-real3\.10|libpetsc\-real3\.10\-dbg|libpetsc\-real3\.10\-dev|libpetsc3\.10\-dev\-common|libpetsc3\.10\-dev\-examples|petsc3\.10\-doc)\b/; > is_good = .depends ~ /\b(libpetsc\-complex3\.11|libpetsc\-complex3\.11\-dbg|libpetsc\-complex3\.11\-dev|libpetsc\-real3\.11|libpetsc\-real3\.11\-dbg|libpetsc\-real3\.11\-dev|libpetsc3\.11\-dev\-common|libpetsc3\.11\-dev\-examples|petsc3\.11\-doc)\b/; > is_bad = .depends ~ /\b(libpetsc\-complex3\.10|libpetsc\-complex3\.10\-dbg|libpetsc\-complex3\.10\-dev|libpetsc\-real3\.10|libpetsc\-real3\.10\-dbg|libpetsc\-real3\.10\-dev|libpetsc3\.10\-dev\-common|libpetsc3\.10\-dev\-examples|petsc3\.10\-doc)\b/; This looks like (haven't checked 100%) the auto-generated one, so I set the forwarded tag. I'll trigger the two remaining binNMU's shortly. Paul
Attachment:
signature.asc
Description: OpenPGP digital signature