Re: Problem with project link
Jon Boone <[email protected]> Fri, 27 Dec 2024 17:50:41 -0500
| Newsgroups | gmane.lisp.common-lisp-net.devel |
|---|---|
| Message-ID | <CACdCdGhGP57a5tkReB4mD3wowx3oBx1g1FF5MAQrcSV7+D48wg@mail.gmail.com> |
David, I'm wondering if this is perhaps also related: I tried to pull the latest updates from the cmucl/cmucl repo and received this message: remote: You (@jboone) must accept the Terms of Service in order to perform this action. To accept these terms, please access GitLab from a web browser at https://gitlab.common-lisp.net. But, when I navigate to https://gitlab.common-lisp.net in my web browser and login, I don't see any prompts to accept the Terms of Service as outstanding.... --jon —jon On Fri, Dec 27, 2024 at 5:30 PM David Cooper <[email protected]> wrote: > Hi Raymond, > > You might need to add your ed25519 public key to here: SSH Keys · User > Settings · GitLab > <https://gitlab.common-lisp.net/-/user_settings/ssh_keys> > > Make sure the same one which is in your .ssh/authorized_keys and which > you know is the one letting you ssh in, is also added to that list in the > gitlab UI. I think your "rtoy" gitlab user and your "rtoy" shell login > account are treated as two different things so the requisite public key has > to be in both places. > > The stronger key (ed25519) may be a requirement which came into play with > a recent gitlab update. I also had to add an ed25519 key for my > pushes/pulls to start working. A recent gitlab update, or a setting we have > somehow imposed upon this new instance. In either case, I don't mind > pushing for everyone to review their keys and add new stronger ones if > needed. > > Please advise, Thanks, > > Dave > > > ---- On Fri, 27 Dec 2024 16:30:32 -0500 *Jon Boone > <[email protected] <[email protected]>>* wrote ---... > > How do we figure out the repo being read-only (which I'm guessing has to > do with some ownership issues in the gitlab config)? > > > > >