You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to build the Docker image, but coming to this error:
Submodule path 'CloudCompare/plugins/core/Standard/qTreeIso': checked out '25a9ca397d9fe2c02afd2740cbbc82df747a2b8a' fatal: failed to unpack tree object ad41baa8e4bbb8fcd599769400e2a3b04128352c error: Submodule 'CloudCompare' could not be updated. error: Cannot update submodule: CloudCompare
Any clues why? Seems like it has more to do with the Git repo it's getting this submodule from.
The text was updated successfully, but these errors were encountered:
Hello,
I reproduce the bug. I don't check and update the docker script regularly, and something is broken in the git submodules repositories starting from the git tag used in the docker file.
If I replace the git tag CloudComPy_docker-20230216 by CloudComPy_master_2023_10_26 in Dockerfile_CloudComPy310_build, line 16, it's OK.
I also have the same issue.
Last month (22.12.2023) your git tag changed worked for me when I replaced "CloudComPy_docker-20230216" with "CloudComPy_master_2023_10_26".
However, as of today I cannot create the docker image anymore and I am getting the "error: Cannot update submodule" error again.
Is there a new tag, I have to exchange it with?
Hello Eric,
Sorry, my mistake... The chain of submodules is broken on my repository with the tag CloudComPy_master_2023_10_26
It works for me with the latest tag CloudComPy_master_2023_12_19.
Trying to build the Docker image, but coming to this error:
Submodule path 'CloudCompare/plugins/core/Standard/qTreeIso': checked out '25a9ca397d9fe2c02afd2740cbbc82df747a2b8a'
fatal: failed to unpack tree object ad41baa8e4bbb8fcd599769400e2a3b04128352c
error: Submodule 'CloudCompare' could not be updated.
error: Cannot update submodule:
CloudCompare
Any clues why? Seems like it has more to do with the Git repo it's getting this submodule from.
The text was updated successfully, but these errors were encountered: