clo-devel December 2024

clo-devel@common-lisp.net

9 participants
15 discussions

Fwd: Re: Problem with project link
by David Cooper 26 Dec '24

26 Dec '24

Dave Cooper ============ Forwarded Message ============ From : david.cooper(a)genworks.com To : toy.raymond(a)gmail.com Date : Thu, 26 Dec 2024 18:57:06 -0500 Subject : Re: Problem with project link ============ Forwarded Message ============ I see three rsa and one dsa in your authorized_hosts, no ed25519. I'll put your ed25519 one in if you can send it. Also, maybe you need to update your .ssh/config with the name gitlab.common-lisp.net because previously you were logging in to the toplevel name (that will work for the new host as well when migration is complete, but in the interim you'll have to ssh to it as gitlab.common-lisp.net or its IP address). Dave Cooper ---- On Thu, 26 Dec 2024 18:34:32 -0500 toy.raymond(a)gmail.com wrote ---- On Thu, Dec 26, 2024 at 3:19 PM David Cooper <david.cooper(a)genworks.com> wrote: Dave Cooper ---- On Thu, 26 Dec 2024 17:41:05 -0500 toy.raymond(a)gmail.com wrote ---- Can you ssh to gitlab.common-lisp.net ? It might not accept older rsa keys, i.e.you might need to generate new stronger e.g. ed25519 keys (I'm not gonna go snooping around your .ssh directory unless I need to). If so, send me your new public key and I'll add it to your .ssh/authorized_keys on the new host. Hmm. I can't ssh to gitlab.common-lisp.net. I don't think I've ever tried that before. I still have my old rsa key, but I also switched to ed25519 keys quite a while ago and that's what I use for ssh now. On Thu, Dec 26, 2024 at 12:53 PM David Cooper <david.cooper(a)genworks.com> wrote: Note that the DNS for gitlab.common-lisp.net switched over to a new IP address (a new Hetzner host) Christmas eve. What is the correct IP address? Clearing the OS and browser DNS cache didn't seem to make a difference. I can ping gitlab.common-lisp.net just fine: ``` 64 bytes from future.common-lisp.net (65.108.13.229) ``` So you may need to clear your DNS caches (browsers and OS). The toplevel common-lisp.net still resolves to the old host for now, so ssh'ing there will get you to the legacy host. But the plan is to move that to the new host in due course as well. I assume you'll need a shell login for the new host? The new host is reachable via future.common-lisp.net or gitlab.common-lisp.net, and i believe your shell login account has been replicated on the new host Yes, I'd like a shell login. I still need to access it to upload cmucl release tarballs and such. Thanks for your help. I think I should reboot my modem and wifi once again. I think that's the only way to clear the DNS cache on my wifi router connected to my cable modem. already. Dave Cooper P.S. these mailing lists are still going through the legacy host. ---- On Thu, 26 Dec 2024 13:45:50 -0500 toy.raymond(a)gmail.com wrote ---- On Thu, Dec 26, 2024 at 8:54 AM Jon Boone <ipmonger(a)delamancha.org> wrote: I have no problems reaching it via Safari (Version 18.2 (20620.1.16.11.8)) or Chrome (Version 131.0.6778.205 (Official Build) (arm64)) on macOS 15.2 (24C101) as of 2024-12-26 11:55 EST. Ok, it must be me. I can't reach it on any of my computers, even after rebooting my modem and wifi point. But I can over cellular with my phone. But every other site I try works fine over my home wifi. I can even ssh into common-lisp.net. Not sure what's going on. I didn't update anything or add a proxy or anything like that. —jon On Thu, Dec 26, 2024 at 11:26 AM Raymond Toy <toy.raymond(a)gmail.com> wrote: On 12/25/24 12:28 PM, Georgiy Tugai wrote: I believe that the links should be working again now. FWIW, I can’t reach gitlab.common-lisp.net at all. Firefox says it’s unable to connect. Chrome says it can’t be reached. I think this started a couple of days ago, maybe? Regards, Georgiy On 25/12/2024 21:02, Robert Goldman wrote: I was trying to follow a link from the projects hub, https://common-lisp.net/phub for usocket, and got a 404. I've tried clicking some other links and they all 404 also, so maybe there's some rewrite or redirect logic that's busted? Happy Holidays, R ...

1 0

Re: Problem with project link
by Robert P. Goldman 25 Dec '24

25 Dec '24

Hi David, Will do! Thanks, -Robert Sent from my iPhone On Dec 25, 2024 at 14:50:15 CST, David Cooper <david.cooper(a)genworks.com> wrote: Hi Robert, gitlab-future.common-lisp.net should now resolve identically as gitlab.common-lisp.net, such that the former should no longer be needed. If you test, please go ahead and test the latter. Dave Cooper ---- On Wed, 25 Dec 2024 15:37:55 -0500 rpgoldman(a)sift.net wrote ---- Hi David, Sure. Should I try on cl.net, cl-future.net, or both? Thanks, -Robert Sent from my iPhone On Dec 25, 2024 at 14:24:56 CST, David Cooper < david.cooper(a)genworks.com > wrote: Hi Robert, If you are still looking at this stuff, could you try some of your pipelines. Thanks, Dave Cooper ---- On Wed, 25 Dec 2024 15:02:19 -0500 rpgoldman(a)sift.info wrote ---- I was trying to follow a link from the projects hub, https://common-lisp.net/phub for usocket, and got a 404. I've tried clicking some other links and they all 404 also, so maybe there's some rewrite or redirect logic that's busted? Happy Holidays, R

1 0

Re: Problem with project link
by Robert P. Goldman 25 Dec '24

25 Dec '24

Hi David, Sure. Should I try on cl.net, cl-future.net, or both? Thanks, -Robert Sent from my iPhone On Dec 25, 2024 at 14:24:56 CST, David Cooper <david.cooper(a)genworks.com> wrote: Hi Robert, If you are still looking at this stuff, could you try some of your pipelines. Thanks, Dave Cooper ---- On Wed, 25 Dec 2024 15:02:19 -0500 rpgoldman(a)sift.info wrote ---- I was trying to follow a link from the projects hub, https://common-lisp.net/phub for usocket, and got a 404. I've tried clicking some other links and they all 404 also, so maybe there's some rewrite or redirect logic that's busted? Happy Holidays, R

1 0

Quick question about cl.net github actions
by Robert Goldman 17 Dec '24

17 Dec '24

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.

2 1

Please stop mails
by Elias Pipping 11 Dec '24

11 Dec '24

My son Elias died in 2017. I’m still caring for his accounts. In case of any questions concerning projects please contact his brother Sebastian.pipping.org Thank you! Heike Pipping Sent from my iPhone

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

clo-devel December 2024