git-pull path not specified in fenics-pull script

[Richard Lai]

Hi there,

I tried to initiate update using fenics-update, but got the following message

FENICS-BUILDER: Pulling fiat...
fatal: No path specified. See 'man git-pull' for valid url syntax

I think it's because in the fenics-pull script, no branch was specified for git-pull

[Anders Logg]

The script only uses `git pull` if there is already a directory named `fiat` in the default source directory. It otherwise uses `git clone`. It's likely that you have run the script twice and it failed the first time (or created the directory yourself somehow). Check whether the directory exists, remove it and then try again.

--

Anders

--
You received this message because you are subscribed to the Google Groups "fenics-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fenics-suppor...@googlegroups.com.
To post to this group, send email to fenics-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fenics-support/61c1bf6f-8861-4cbd-9e34-ab3dbeaee499%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Johannes Ring]

Which docker image are you using? Are you using
`quay.io/fenicsproject_dev/dolfin:master` or any of the other images
on `quay.io/fenicsproject_dev`? They are generated by our CI system
and the projects in `~/local/src` are shallow clones and does not have
a proper git remote set, and therefore `git pull` does not work.
However, instead of running `fenics-update` inside the docker
container, you can run `docker pull
`quay.io/fenicsproject_dev/dolfin:master` or similar for your docker
image to get the latest updates.

Note that the docker images on `quay.io/fenicsproject_dev` are
primarily meant for the CI system and for debugging. That said, I will
see if I can set a proper git remote such that `fenics-update` will
work in the future.

Johannes

[Richard Lai]

Thanks Johannes this works :)

 I'm using the py3-master image as I was testing some codes written in python 3.

Richard