clo-devel

clo-devel@common-lisp.net

608 discussions

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

Need Volunteers for Website Working Committee
by David Cooper 15 Oct '23

15 Oct '23

Hi all, We have a big opportunity for a few volunteers to help move clnet services to a new host. You will become part of our Website Working Committee. Our old host has proven resistant to doing an in-place OS upgrade, so we have determined the way forward is to provision a fresh host (funding for that is another open matter, for a Fundraising committee – volunteers welcome for that as well). This (standing up the new host) should be a fun project with a lot of learning and networking opportunities. Please write to me directly if interested. Dave Cooper

4 14

Mailman3 web interface
by Erik Huelsmann 04 Oct '23

04 Oct '23

All, The web interface for the new mailman version is at https://mailman3.common-lisp.net/postorius/ for mailing list administration and https://mailman3.common-lisp.net/hyperkitty/ for the archives. Let me know if you find irregularities or have other remarks. Regards, Erik

5 9

Locked out of payments host
by Dave Cooper 09 Aug '23

09 Aug '23

Hi Erik H, if you're out there, I managed to lock myself out of payments.common-lisp.net by the firewall. Is it possible to get into it with a Hetzner console and temporarily disable the nftables firewall? Thanks, Dave

1 0

Mailman3 migration, next step: 50 most recently active projects
by Erik Huelsmann 15 Jul '23

15 Jul '23

All, Yesterday and today I've migrated mailing lists named by our community which need to be retained for future use. I will keep taking names, but I'll now start mass migration of the 50 mailing lists which have had activity over the last 5 years. In the mean time, we can discuss whether we need to extend these 5 years to 8 years - or any other limit. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 1

Migration of mailing lists to mailman3 started
by Erik Huelsmann 14 Jul '23

14 Jul '23

All, Over the past years (as early as 2014, I think), there have been many times we've seen the need to move off Mailman2: it's implemented in python2.7 which has long seen the end of its life. The alternative has always been Mailman3, which is the technological successor of Mailman3, but a complete rewrite. As early as its initial release in 2015, I've been eyeballing moving to it. Back then, there was no migration path from 2 to 3, but it was on the roadmap, which made the choice to move or stay easy: wait for the release which makes it possible. A lot of time has gone by since. The situation gradually worsened, because the migration to Mailman3 became a blocker to upgrade the operating system on common-lisp.net: python2.7 was phased out, which means the mailman2 list software wouldn't run on it anymore (that is, without significant maintenance burden to maintain our own python2.7 install). Long story short: Yesterday, I installed the containers which allow us to run mailman3 in an isolated environment. There's a lot of tweaking to be done, but I've been able to configure mailman3 to run alongside of mailman2, which is a good start. As of right now, I've started migrating to mailman3, which I'm doing in steps: - basic validations - archives of defunct lists - active mailman2 lists with configuration and archives Before going the route of migrating active lists, I may do an assessment of the activity of mailing lists, asking owners of mailing lists which have gone without activity for 5 years, whether there's still an active interest. Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

[Feedback request] Decommissioning of unused mailing lists (>5yrs no postings)
by Erik Huelsmann 14 Jul '23

14 Jul '23

All, As part of the migration from Mailman2 to Mailman3, I have checked which lists are actively used. The outcome allows for some rigorous cleanup. Out of 236 mailing lists, 180 have not had a mail added to their archives *over the last 5 years(!)*. My proposal is to decommission these mailing lists, meaning that only the archives will be migrated to Mailman3. These mailing lists can always be re-instated at a later time. Rationale for this clean-up is that some owners of the mailing lists have fallen out of contact, causing additional work to fall on the shoulders of the site maintainers: mailing lists require moderation of non-member posts, where those moderation requests which can't be delivered to the list owner, are sent to the site admins. Additionally, unused mailing lists may accrue spam mail in their archives, lowering the value of the archive. (Temporarily) Closing mailing lists can prevent this. What do you think? It concerns these lists: alexandria-cvs anaphora-cvs anaphora-devel ansi-test-cvs ansi-test-devel armedbear-announce armedbear-cvs asdf-install-devel asdf-packaging-announce aspiwork-pdm-cvs aspiwork-pdm-devel bese-devel bordeaux-threads-announce bordeaux-threads-ticket boston-lisp-announce boston-lisp-organizers cello-devel cells-gtk-devel cffi-objects-cvs cl-berkeley-db-devel cl-bzip2-devel cl-containers-devel cl-dbf-cvs cl-dwim-devel cl-ec2-devel cl-emb-devel cl-facebook-devel cl-fuse-devel cl-glpk-devel cl-graph-devel cl-gsl-devel cl-gtk2-devel cl-heap-announce cl-jpeg-devel cl-json-announce cl-kanren-trs-cvs cl-kanren-trs-devel cl-l10n-devel cl-monad-macros-cvs cl-mpi-devel cl-muproc-devel cl-ncurses-devel cl-neo4j-cvs cl-neo4j-devel cl-openid-devel cl-openid-ticket cl-org-mode-devel cl-pdf-announce cl-pdf-devel cl-perec-devel cl-plus-j-announce cl-plus-j-devel cl-plus-ssl-cvs cl-plus-ssl-devel cl-pop-devel cl-proc-devel cl-sbml-cvs cl-selenium-devel cl-smtp-devel cl-soap-devel cl-sqlite-announce cl-sqlite-devel cl-store-devel cl-table-cvs cl-twitter-devel cl-typesetting-announce cl-typesetting-devel cl-unification-devel cl-utilities-devel cl-walker-devel cl-xmlspam-devel cl-xmpp-devel cl-yacc-ebnf-devel clbuild-devel cldoc-devel cleric-announce cleric-devel clfswm-announce clfswm-cvs clfswm-devel climacs-devel climplayer-devel clonsigna-announce clonsigna-devel closer-announce closer-devel clouchdb-cvs clouchdb-devel clsql-fluid-devel clx-devel cmucl-ticket common-lisp-beginner-cvs de-setf-amqp-cvs definer-announce docudown-devel eager-future-devel ecl-readline-devel eclipse-devel editor-hints-devel elephant-devel elephant-ticket f2cl-ticket fetter-devel fiveam-announce fset-devel gecol-devel ginseng-cvs gsharp-devel gtk-cffi-cvs gtk-cffi-devel heresy-devel implementation-hackers iolib-announce iolib-devel ip-interfaces-devel isidorus-devel kpax-devel l-math-announce l-math-devel langutils-devel lgtk-devel lift-devel linedit-cvs linedit-devel lisp-interface-library-devel lisp-machine lispbox-cvs lispbox-devel lisplab-cvs lisplab-devel lisppaste-devel lisppaste-requests lispy-devel lmud-devel local-time-devel mel-base-devel metabang-bind-devel metacopy-devel metatilities-base-devel mit-cadr-cvs mod-lisp-devel movitz-devel names-and-paths-devel nixies-devel noctool-cvs oct-cvs oct-ticket pal-devel parenscript-announce pg-devel plexippus-xpath-devel protobuf-devel python-on-lisp-devel rfc2388-cvs rucksack-cvs rucksack-devel s-xml-devel sicl-announce sicl-devel slime-cvs snow-announce snow-cvs snow-devel spray-devel teepeedee2-devel the-feebs-war-devel tinaa-devel travisci trivial-backtrace-devel trivial-gray-streams-devel trivial-utf-8-devel uri-template-devel usocket-announce usocket-ticket vivace-graph-devel web4r-devel web4r-devel-ja xcvb-devel xuriella-devel zip-devel -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

6 11

clo-devel migrated to Mailman3
by Erik Huelsmann 13 Jul '23

13 Jul '23

All, The clo-devel mailing list has been migrated to mailman3. For the moment it's the only list and this message serves as a test-email to see that the setup works. Migration of the archives of dead lists (lists that have existed in the past, but don't exist anymore) is on-going. While that's continuing, I'm waiting with further migrations of active lists a bit to see whether the new system functions properly. Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

4 3

Locked myself out of Payments host
by Dave Cooper 12 Jul '23

12 Jul '23

Erik et al, I have managed to lock myself out of the payments host. I attempted to install ufw as a simpler interface on top of iptables and/or nftables, but after a failed attempt at the ufw installation, I'm not able to get in at all. Erik: Sorry to have to ask you this especially in the middle of mailman migration, but I think you're the only one who maybe has access to a virtual console to the VM through hetzner. Could you have a look at the machine (payments.common-lisp.net) and see about opening up firewall for ssh on the standard port (I think i'm still running sshd on 22 on there) If the VM needs to be wiped and reinstalled (hopefully not) then it won't be the end of the world - i can certainly reinstall the payments application -- but there are some log files on there which I would very much like to get off the machine if possible (all under ~dcooper8/ -- transaction logs for donations and print sales etc). Sorry again.. Dave -- My Best, Dave Cooper, david.cooper(a)genworks.com genworks.com, gendl.org +1 248-330-2979

1 1

Deliverability via admin@common-lisp.net and request for a new GitLab group
by Vladimir Sedach 21 Jun '23

21 Jun '23

Hello, I tried sending a request for a new GitLab group for CLiki2 to admin(a)common-lisp.net on May 31, and again on June 4. I have not received a reply to either message. I did get DMARC reports from several mail hosts, except philipp(a)marek.priv.at, for whom the following delivery failure message was returned: Mail Delivery System <Mailer-Daemon(a)common-lisp.net> writes: > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > philipp(a)marek.priv.at > (generated from pmarek(a)common-lisp.net) > host nc.hitco.at [2a03:4000:6:71ec::cafe] > SMTP error from remote mail server after RCPT TO:<philipp(a)marek.priv.at>: > 550 5.7.23 <philipp(a)marek.priv.at>: Recipient address rejected: > Message rejected due to: SPF fail - not authorized. Please see http://www.openspf.net/Why?s=mfrom;id=vas@oneofus.la;ip=2a01:4f8:160:83c4::…<UNKNOWN> I believe this is due to a configuration error on Philipp's SMTP server, and have corresponded with him about this separately. The DMARC policy for my mail domain has a "none" policy, so SPF failures should not be rejected. I set up DKIM, SPF, and DMARC on this domain in 2015, have a 10/10 deliverability score from https://www.mail-tester.com/ and have not had any problems with mailing lists. So, 2 things: 1. Can everyone who is being forwarded mail from admin(a)common-lisp.net please check their spam folders for any messages sent via admin(a)common-lisp.net to them since May 30th? 2. Can someone please make a new GitLab group for CLiki2 with my account (vsedach) as an owner? If no one finds emails from me sent to admin(a)common-lisp.net in their Spam folders, there might be a configuration issue with how those mails are forwarded. I receive mail forwarded via vsedach(a)common-lisp.net, so it might be something involving forwarding to multiple people. Thank you. -- Vladimir Sedach

2 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

clo-devel