<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Mar 17, 2022, at 10:04 AM, Robert Helling wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Dirk,<br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On 17. Mar 2022, at 16:46, Dirk Hohndel via subsurface <<a href="mailto:subsurface@subsurface-divelog.org" class="">subsurface@subsurface-divelog.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Ok, so admittedly, this is my fault. I wasn't paying attention to GitHub's announcements.</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Actually, I don't recall ever really noticing the announcement.</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">But whatever - two days ago they turned off the git:// protocol for accessing their servers. And we used that in our submodule and in a few other places in our build scripts. Which means anyone trying to build 5.0.6 will see that build fail. Not a big deal as most people (like 99.9+% of our users) are using the binaries I make anyway. But still... we should make a new release.</span></div></blockquote></div><br class=""><div class="">I am fine with a new release (have done the German translation this morning), but how does a new release help the problem?</div></div></div></blockquote><div><br class=""></div><div>Yes, for anyone who clones the current sources (or, 5.0.7 once it's released), things will work.</div><div><br class=""></div><div>The problem happens when you already have an older version checked out. </div><div>Then it depends on a number of things.</div><div>- if you checked out Subsurface via '<a href="git://github.com" class="">git://github.com</a>...' then you need to edit your subsurface/.git/config and replace the git:// with https://</div><div>- if you checked out Subsurface via '<a href="mailto:git@github.com" class="">git@github.com</a>:...' or '<a href="https://github...' you should be fine and should be able to do a 'git pull origin master" class="">https://github...' you should be fine and should be able to do a 'git pull origin master</a>'</div><div>- if you instead do a 'git fetch', that will fail because it will try to access the submodule via 'git://...'</div><div><br class=""></div><div>It's all a bit of a mess, really.</div><div>Manually editing '.git/config' and '.gitmodules' should allow you to replace all references to '<a href="git://' with 'https://" class="">git://' with 'https://</a>' and that should be sufficient.</div><div><br class=""></div><div>/D</div><div><br class=""></div><div><br class=""></div></div></body></html>