I assume unintended, since it was updated in both the unattended install script and the buildbot script.
I've done the commit -- https://github.com/OP2/PyOP2/commit/e06ecaf41c8eea7803850e1085c0bd80e6005a4c -- but I think someone else needs to rebuild the website manually.
On 19 October 2014 10:44, Eike Mueller <e.mueller@bath.ac.uk> wrote:
Hi Lawrence,
this fixes it and it runs fine again on my laptop.
As far as I can see the petsc4py installation instructions onhttp://www.firedrakeproject.org/obtaining_pyop2.html#petsc
still point to https://bitbucket.org/petsc/petsc4py.git, is this intended, or does the firedrake trunk indeed work with this setup?
Thanks a lot,
Eike
--Dr Eike Hermann Mueller
Research Associate (PostDoc)
Department of Mathematical Sciences
University of Bath
Bath BA2 7AY, United Kingdom
+44 1225 38 5803
e.mueller@bath.ac.uk
http://people.bath.ac.uk/em459/
On 17 Oct 2014, at 15:26, David Ham <David.Ham@imperial.ac.uk> wrote:
_______________________________________________Dear Firedrakers,
Some of you have recently had problems with installing PETSc recently. There is now a fix for this, and also new install URLs for PETSc and petsc4py which will hopefully reduce the number of ongoing PETSc install issues that people have.
The short version is that the instructions for installing PETSc and petsc4py on our websites have been updated, so if you are installing or upgrading PETSc you should follow the new instructions:
The ever so slightly longer version is that we now point to our own fork of PETSc rather than the upstream master. We will update our forks as necessary and only after checking that the version we update to appears to work. This should hopefully reduce the number of random breakages users encounter in PETSc.
Cheers,
David
--
Dr David Ham
Departments of Mathematics and Computing
Imperial College London
http://www.imperial.ac.uk/people/david.ham
firedrake mailing list
firedrake@imperial.ac.uk
https://mailman.ic.ac.uk/mailman/listinfo/firedrake