clo-devel November 2023

clo-devel@common-lisp.net

5 participants
4 discussions

Mailman3 migration, next step: mailman2 web-ui disabled
by Erik Huelsmann 13 Jul '24

13 Jul '24

All, Now that the 50 most active projects have been migrated to Mailman3 (available through https://mailman3.common-lisp.net/), I've disabled the web-ui for Mailman2. This means that the page listing the available mailing lists (https://mailman.common-lisp.net/listinfo) now forwards to mailman3's list management page (https://mailman3.common-lisp.net/postorius). All related entry-points for managing lists also have been disabled (meaning: /admin, /admindb, /create, etc.). The old archives are still available. They're listed at https://mailman.common-lisp.net/pipermail/ (which is where they've always been). I have no intention to remove these archives at this point, although we may want to point users to the fact that mailman3 is where new archives are being accumulated, especially on the thread/date index pages. Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

2 3

Re: Gitlab registration on #common-lisp.net via minion restored (was Re: common-lisp.net http stopped running)
by Mark Evenson 20 Nov '23

20 Nov '23

> On Nov 20, 2023, at 13:54, Dave.Cooper <dave.cooper(a)genworks.com> wrote: […] > > > I may have missed it in the thread leading up to this, but was it necessary to clear something with the Libera chat authorities in order to get our bot authorized to run on their network again? No, it is not necessary to get authorization from libera.chat to run bots. It turns out that one of the major problems with the lisp-bots code was that libera.chat seems to have installed some sort of request rate limiting setting that freenode never had which interprets connecting to many channels simultaneously as a network flood, and terminates the connections. I worked around that by placing a 200ms pause between JOIN events. I suspect that whoever was trying to diagnose connecting to libera.chat interpreted this as a ban or something, which led to the confusion. -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."

1 0

common-lisp.net http stopped running
by Mark Evenson 20 Nov '23

20 Nov '23

The apache2 instance seems to have stopped at 0010 this evening. Seems to be something about a bad SSL configuration due to a package containing empty certs being deleted Looking into it on the machine; sending email in case their are others working on this as well. -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."

6 17

Re: common-lisp.net http stopped running
by Mark Evenson 16 Nov '23

16 Nov '23

> On Nov 16, 2023, at 08:37, Philipp Marek <philipp(a)marek.priv.at> wrote: > >> It seems that mevenson has access to gitlab-future.common-lisp.net <http://gitlab-future.common-lisp.net/>. Is that the host we’re configuring? It will have more than just gitlab running on it, correct? > > yeah. more or less everything, apart from backup (& perhaps monitoring). > > > Do you have shell access to future- already? Yes, and I even have sudo for user `mevenson`, so I am all set. > > >> I’ve been a little out of the loop on the move. Did anyone keep any notes on what needs to be done? > > https://cryptpad.fr/pad/#/2/pad/edit/j4kE6fs3czXQq4t9EF-vgUuf/ (un)fortunately, that document seems to outline plans for centralizing Common Lisp outreach in Vienna next year for SBCL25/ELS24. Try again when you have a chance? yours, Mark -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

clo-devel November 2023