- clo-devel - mailman3.common-lisp.net

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

Re: Discourse Requirements
by Mark Evenson 19 Nov '24

19 Nov '24

> On Jun 18, 2022, at 18:11, Chris Moore <moore.christopher515(a)gmail.com> wrote: > > Hey Mark! > > If it makes it easier for the foundation, I can get the host together myself (paying for w/e architecture) and get a proof of concept out for the board to review prior to attaching any kind of DNS record. Not necessary for you to get the host yourself. Sorry to have been a little recalcitrant over the last week, but I have just started a new job with <https://status.im> which has been occupying my time. Erik Hülsmann, a CLF board member, rents <https://hetzner.de/> instances for his CRM company which he essentially donates to the CLF at less than costs, so spinning up a host is no problem. We have standardized on Debian over Ubuntu as it makes the licensing situation clearer when we need a “special case”. Is there any reason you couldn’t install Discourse in the manner you wish under Debian? > > This includes me setting up whatever mail server, getting our daily backups together, and adding necessary plugins (GitHub/Gmail OAuth). If necessary, we would federate the `USER(a)common-lisp.net` domain. Currently we are running exim as the main MTA due to legacy concerns with mailman2 databases, but we wish to transition to a toplevel `postfix` that will work with the legacy `exim` for the `mailman2` app. > > I apologize for trying to rush this - I've got a lot of free time currently due to a lull in work going on at my current company. So I and the dev team are currently not doing much. I want to take advantage of the time while I can. Cool. Let’s take advantage of it. > > Let me know and I'll get this out the door ASAP. Can you please provide me with the public half of a contemporary-strength SSH keypair. We’ll set up a host, and communicate root@HOST via ip4/6 under separate cover. yours, Mark P.S. if you wanna find me online, let’s figure out a Discord rendezvous. I’m <discord:347061732705042435> aka <discord:easye#8466>. -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."

2 1

btrfs on future host (UFW is gone), gitlab switchover imminent
by David Cooper 14 Nov '24

14 Nov '24

Hi Philipp, Do I recall correctly that UFW was getting in your way of installing btrfs? Well, we've uninstalled ufw and installed nftables now (with iptables compatibility layer). Assuming ufw was the main problem, would you be able to look at the btrfs conversion process again? By the way, SAL9000 and I are in a new room on libera.chat - ##clnet-futurehost and aiming to switch over the gitlab during an upcoming weekend. Dave Cooper

2 1

Problem with new Docker images and GitLab actions at cl.net
by Robert Goldman 19 Sep '24

19 Sep '24

When trying to run new CL docker images based on Debian bookworm, I'm getting errors like this: ``` Executing "step_script" stage of the job script 00:03 Using docker image sha256:09d35b13e5a86639aa00b12c2f57561e55a6126c78f654df463f3c914e2eff31 for rpgoldman/ccl:latest with digest rpgoldman/ccl@sha256:746098f1e5c7e82a4f1605817af3137a966b50b7d935caeb5b313f7d20841556 ... shell not found ``` Googling reveals [this gitlab discussion](https://forum.gitlab.com/t/jobs-fails-shell-not-found-version-p… following, which suggests a possible work-around, but that also contains the following note: > In my case gitlab-runner’s shell detection script was failing to > stat the available shell executables due to an incompatibility between > the container and the host, thus returning failure for every check and > giving up with the “shell not found” error. > This sometimes happens when running bleeding edge images on older > hosts, but typically it’s more obvious and often presents itself as > a filesystem permissions error or some other system call failure. > Essentially, the binaries/libraries in the container are using > new/modified system calls that the dockerd/containerd’s seccomp > layer doesn’t understand yet. *Updating the host kernel and > container runtime tends to fix this.* [italics added] Is there any chance that the GitLab host needs a refresh? Thanks, R

2 1

Now that mail transfer is encrypted: stricter DMARC?
by Erik Huelsmann 27 Aug '24

27 Aug '24

Hi, Since a few weeks now, we're running DMARC for the mailing lists. So far, we've run with the loosest policy possible ("none"). The other options are "quarantine" and "reject". I'm thinking we'll want mail sent using our domain (common-lisp.net) failing the DMARC checks (failing SPF and/or DKIM), to be quarantined (moved to SPAM) at the very least. I noticed that fastmail is using an even stricter policy ("reject"), but moving straight from "none" to "reject" seems too much (because "reject" prevents delivery; not just moving to SPAM). This will affect everybody using an @common-lisp.net mail address with their own mail server. Does this affect anybody on this mailing list? Any comments with respect to the stricter policy? Regards, Erik.

3 2

Exim changes: encrypted mail outflow
by Erik Huelsmann 26 Aug '24

26 Aug '24

Hi all, Finally, I've been able to configure outgoing mail on common-lisp.net using TLS on outbound connections. As it turns out, I had to resort to ACLs (setfacl/getfacl) to assign Exim's primary group (Debian-exim) read access to /etc/letsencrypt/{live,archive}. For some reason, being granted read access through the secondary group, doesn't work for Exim and leads to "Error reading file" messages in the logs. On my test messages, GMail now reports that common-lisp.net used encryption to send the mails.) (Consider this mail to be a test-case for mails sent through the mailing list software.) Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0