Forum Message

 

 

We have moved the forum to https://forum.ngsolve.org . This is an archived version of the topics until 05/05/23. All the topics were moved to the new forum and conversations can be continued there. This forum is just kept as legacy to not invalidate old links. If you want to continue a conversation just look for the topic in the new forum.

Notice

The forum is in read only mode.

Error updating submodules

More
5 years 6 months ago #1185 by ddrake
Hi, I don't recall seeing this error before.

$ git pull
$ git submodule update --init --recursive

error: Server does not allow request for unadvertised object 2a150736601bb3113877bb673fb934bb60d46ec5
Fetched in submodule path 'external_dependencies/netgen/external_dependencies/pybind11', but it did not contain 2a150736601bb3113877bb673fb934bb60d46ec5. Direct fetching of that commit failed.
Failed to recurse into submodule path 'external_dependencies/netgen'

When it failed, I tried git submodule sync, then retried the command, but got the same error. Should I just clone the repo again?

Best,
Dow
More
5 years 6 months ago #1186 by ddrake
Replied by ddrake on topic Error updating submodules
I just cloned the repository again and did not have any trouble updating submodules after that.

Best,
Dow
More
5 years 6 months ago #1187 by matthiash
Replied by matthiash on topic Error updating submodules
Hi Dow,

The reason for this error is that we changed the upstream url for the pybind submodule. This is necessary to apply patches to pybind11 which are not (yet) upstream. This update is not done automatically with 'git pull', so you have to do:
Code:
git submodule update --init --recursive git submodule sync --recursive git submodule update --init --recursive

The first update will fetch the latest Netgen, but fails at updating pybind11 inside Netgen. 'submodule sync' will update the upstream urls of all submodules (including pybind11). Afterwards the second update checks out the correct version.

Note that you have to do this only once (we will update the documentation). Checking out the latest version from scratch also works around this as you experienced.

Best,
Matthias
The following user(s) said Thank You: ddrake
Time to create page: 0.112 seconds