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
The upstream ace submodule fixed this: ajaxorg/ace@69edbf9. This is released a few patch versions higher than the current version. We're now somewhere between 1.1.3 and 1.1.4, this is released as part of 1.1.7.
I am trying to locally clone this app so I can locally deploy a very old ExistDB app (currently on 5.2.0). I will remove the usage of shared-resources, but as a later step to prevent any rabbit holes.
I dont expect a fix. But I'm filing this issue to suggest a workaround to future code archeologists running into the same issue:
Workaround:
# Replace `git://` with `https://` for all clones
git config --global url."https://".insteadOf git://
The text was updated successfully, but these errors were encountered:
Describe the bug
This repo uses the deprecated git:// protocol in the README and in the git submodules (and the submodules of the submodules).
Expected behavior
To Reproduce
git clone git://github.com/eXist-db/shared-resources.git /tmp/shared-resources --recursive
Context (please always complete the following information):
Not relevant
Additional context
The
git://
protocol is deprecated and removed. In 2022. https://github.blog/security/application-security/improving-git-protocol-security-github/#no-more-unauthenticated-git.The upstream ace submodule fixed this: ajaxorg/ace@69edbf9. This is released a few patch versions higher than the current version. We're now somewhere between 1.1.3 and 1.1.4, this is released as part of 1.1.7.
I am trying to locally clone this app so I can locally deploy a very old ExistDB app (currently on 5.2.0). I will remove the usage of shared-resources, but as a later step to prevent any rabbit holes.
I dont expect a fix. But I'm filing this issue to suggest a workaround to future code archeologists running into the same issue:
Workaround:
The text was updated successfully, but these errors were encountered: