Thanks, Dave --

I'm trying to get into gitlab-future.common-lisp.net, and having a problem. I don't have the 2FA device I had configured on gitlab.common-lisp.net, which isn't a problem there, because I have a passkey set up. But the passkey does not seem to have migrated to gitlab-future.common-lisp.net, so I am unable to log in.

Could you perhaps disable the 2FA on g-f.cl.net so that I can reset it? Sorry about the nuisance,

Thanks, R

On 17 Dec 2024, at 11:12, David Cooper wrote:

Hi Robert,

We are in the process of migrating gitlab.common-lisp.net to the new host, currently gitlab-future.common-lisp.net.

https://gitlab-future.common-lisp.net%C2%A0is up and running and it's been restored from a recent backup of the production host - so if you'd like, you can test the pipeline in question on gitlab-future.common-lisp.net -- it may or may not work completely but at least you can see if it hits a different issue from what you are seeing on the legacy host.

We're hoping to do the cutover to the new gitlab host possibly by the end of the year, and it will be great if we can confirm that the docker pipeline issue you were hitting is indeed not an issue on the upgraded host.

Dave Cooper

---- On Tue, 17 Dec 2024 11:39:33 -0500 Robert Goldman rpgoldman@sift.info wrote ---

Sorry to bother you, but wondering -- did the CI issue with the Gitlab runner not being able to run newer docker images get fixed? That's the one where the Gitlab runner claims it can't find the shell when running some newer docker images.

I was going to fix up some issues in the ASDF pipelines, but I think that's a blocker.