Good catch. The remotes need to be git@git.common-lisp.net or git@gitlab.common-lisp.net. There may never again be a guarantee that these will resolve to the same host as toplevel common-lisp.net

Any remotes which reference @common-lisp.net are wrong and need to be updated, even though they may have worked accidentally with the old setup ( they will not work for pushing now, because the old setup is permanently in read only mode until someday it will disappear completely..)

 Apparently, the read-only setting is  a good thing too, or we would already be looking at synchronization hell.


Dave Cooper


---- On Fri, 27 Dec 2024 20:24:11 -0500 ipmonger@delamancha.org wrote ----

Here's the problem for people who have already created clones - their remote url is leveraging git@common-lisp.net instead of git@gitlab.common-lisp.net.  I used this in my cmucl/cmucl repo and problem is resolved for that repo.  How to fix it more generally, though?

git remote set-url origin git@gitlab.common-lisp.net:cmucl/cmucl.git

Also, for cmucl/cmucl, the runners that existed before no longer seem to be defined, so my recent push to a branch has the check jobs stalled due to no eligible runners.

—jon


On Fri, Dec 27, 2024 at 7:58 PM Raymond Toy <toy.raymond@gmail.com> wrote:


On Fri, Dec 27, 2024 at 4:49 PM Dave Cooper <dcooper8@gmail.com> wrote:



I can pull, but can't push.  And now I can't reach gitlab.c-l.net anymore; I'm unable to connect again.

Well, the website is definitely up.
Not for me.  And adding an entry in my /etc/hosts file doesn't work; it did before.

What happens when you try to push? 
It says it's read-only.  And check my access rights.

Superstition, but try logging out and back in. 
No joy. :-(

Am I the only one having trouble?  Lucky me!


--
Ray