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

Moving mailing lists to *@lists.common-lisp.net
by Erik Huelsmann 31 Dec '25

31 Dec '25

Hi, To simplify maintenance of common-lisp.net services - by way of being able to migrate components from one server to another in parts rather than in a big bang - we need to move the mailing lists which are currently hosted on <list>@common-lisp.net to <list>@lists.common-lisp.net. Not sure when this will happen and when it happens, we'll run a forwarding service from common-lisp.net to lists.common-lisp.net (if/when we can). Any comments, remarks or things you need us to take into account? -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

4 3

https://common-lisp.net/libraries
by Orm Finnendahl 23 Dec '25

23 Dec '25

Hi, hope this is the right address for this (otherwise just let me know). This is a mail concerning the page in the subject line (https://common-lisp.net/libraries) I'm the maintainer of the cm-incudine and Common Music repositories listed in the Audio section of the page. I would like to make some suggestions for changes and additions on that page: 1. I've moved all my repositories from GitHub to Codeberg: Common Music: https://codeberg.org/ormf/cm cm-incudine: https://codeberg.org/ormf/cm.incudine 2. cm-incudine is deprecated as it is now included in a much larger system called Clamps. It is located here: https://codeberg.org/ormf/clamps the description: CLAMPS Common Lisp Aided Music Production System Clamps, short for "Common Lisp Aided Music Production System", is a software system for realtime and non-realtime music production written in Common Lisp. It enables a seamless workflow between high-level structures to define musical processes all the way down to low level dsp definitions for sound creation including browser based interfaces for interactive work and control useable for live performances. In that respect it combines features of systems like OpenMusic, SuperCollider or the Pure Data/Max family of software. -------------------------------------------------------------------- I would suggest to get rid of cm-incudine on the common-lisp.net page and replace it with clamps. There is also extensive documentation of Clamps here: https://www.selma.hfmdk-frankfurt.de/finnendahl/clamps-doc/overview/ 3. There is also FOMUS: https://codeberg.org/ormf/clamps OVERVIEW fomus is a software application for formatting musical output written by David Psenicka (see: http://fomus.sourceforge.net) This repository is a package derived from the common lisp port of fomus with some small modifications due to lilypond api changes and some enhancements for my personal use. 4. And there is ATS-CUDA: https://codeberg.org/ormf/ats-cuda ATS incudine version 2022 This is an incudine port of the original Common Lisp (CLM) ATS version 1.0 by Juan Pampin (see the original README in the paragraph "A T S" below), available here. The incudine port was made to facilitate realtime synthesis. All dependencies to clm have been removed to simplify installation. Wish you the best for the Holidays and a Happy New Year! -- Orm

1 0

common-lisp.net Mailing List Services in Need of Migration
by David Cooper 17 Dec '25

17 Dec '25

Dear All, The maintainers of common-lisp.net including these mailing lists are seeking a volunteer or volunteers to help migrate these @common-lisp.net mailing lists from the legacy host (legacy.common-lisp.net) to a relatively new Hetzner host that we have established (64GB RAM, 12 CPU threads, AMD Ryzen 5 3600 model 113, hosted at Hetzner's Helsinki-1 data center). With the increased capacity we are able to provide more self-contained services such as local CI runners which can be made available to projects (the recent revival of http://gitlab.common-lisp.net/cl-docker-images/ is an example of a project that can benefit from local runners as opposed to a far-flung network of runner machines in someone's house or in a closet at MIT etc. which may or may not be maintained consistently over the years). With help from a few individuals, notably Georgiy Tsukai, we have already migrated most other common-lisp.net services, including gitlab.common-lisp.net (that's been done almost a year now), as well as the common-lisp.net main website, the *.common-lisp.dev project sites, and others. cliki.net migration is currently being worked on by Vladmir Sedach (it's apparently affected by some recent issues with a Linux xml library, not connected with CL directly, but that clike was depending on, that Vladimir has to update cliki to work around). The major remaining task is to migrate mail services and update corresponding MX records so that incoming @common-lisp.net mail will land at the new server, to be handled for individuals by their ~/.forward (we still want to support that for folks with shell accounts on the host), as well as fanning out to these mailing lists @common.lisp.net. So if anyone with experience in such matters would be willing to spend a bit of time & attention, maybe over the holidays, to look into our mail setup and help with migration, that opportunity remains. When completed, this will allow Erik Huelsmann finally to let go of the legacy host, which some time ago lost its ability to update the OS in-place (over the years, a hodgepodge of different OS versions got cobbled together on that host by a string of different admins, to where it's no longer amenable to normal debian apt update/upgrade). So it's become a burden on Erik to keep that machine running at all. The current common-lisp.net is running on a consistent fully updated Debian GNU/Linux 13 (trixie) and, knock wood, remains update/upgradable including its installed gitlab service stack, which we also keep updated every few weeks. Incidentally we are also running a jitsi instance on there at meet.common-lisp.net, which any of you in the community is welcome to use for CL related online meetings. Anyone interested in giving some attention to this mailing list setup, please advise. You can respond to this list, to me directly, or join IRC at libera.chat #common-lisp.net channel. And in any case, Happy Holidays and Happy Common Lisping to all! Thanks, Dave Cooper P.S. Genworks has been paying the Hetzner fees for the future host (booked as donations to the Common Lisp Foundation, about $40/month). And Erik H is still paying from his own pocket (or his company's coffers) for the legacy one, which is a VM slice of a bigger Hetzner host that he maintains (our new host is a physical machine, I believe). Anyway, at some point we do plan to enable donations and offer sponsored links again, to decouple the future viability of common-lisp.net services from the ongoing enthusiasm and solvency of any particular individual or entity (this will be done on principle, and not because I personally do not plan and hope to keep Genworks solvent and enthusiastic indefinitely into the future!). Anyway just a heads up that such donation opportunities will be upcoming as well.

1 2

Correction of Georgiy's name, contact info for him
by David Cooper 17 Dec '25

17 Dec '25

Apologies to Georgiy for working from my (apparently failing) memory and neglecting to take a few seconds to look up his last name, which is Tugai, not Tsukai. I wanted to make sure he gets recognized for all his work. Anyone wishing to contact him, let me know and I'll put you in touch, he's active on IRC, I won't presume to dox him any more on these lists, but anyone wishing to contact him let me know and I'll put you in touch (he is on mailto:clo-devel@common-lisp.net as well). Dave

1 0

Re: cl-docker-images
by Anton Vodonosov 25 Nov '25

25 Nov '25

I am using the clfoundation/cl-devel:2022-02-09 docker image to test cl+ssl on various lisp implementations with Github Actions (https://github.com/cl-plus-ssl/cl-plus-ssl/tree/master/.github/workflows) What I am missing is CMUCL - it's absent in that image, and I even introduced an unnoticed regression for CMUCL. So, if there is work on refreshing the docker images, let me express a wish for CMUCL to be included in the cl-devel image. Best regards, - Anton

3 3

cl-docker-images
by David Cooper 24 Nov '25

24 Nov '25

Hi Robert, I'm trying to resurrect some of the cl-docker-images pipeline. Just thought I would check with you because I think you have bypassed these for asdf? In case I get them working again I'd like to compare notes and avoid too much duplication of work, and I'd like to make whatever images I come up with be compatible for retro-fitting into asdf at some point in case you'd like to relieve yourself of the need to keep your own ones maintained (or we could adopt your ones as the clnet-hosted ones). Did you understand all of Timmons's bashbrew runners? I'm replacing those with a single shell runner on our future host but I'd like to get it to docker-in-docker after that... and maybe support multiarch using emulation (I think Timmons had actual hardware running each of his platform-specific runners). Dave Cooper

2 3

Question about downloads
by Robert Goldman 18 Nov '25

18 Nov '25

I just got [an issue in the ASDF repo](https://gitlab.common-lisp.net/asdf/asdf/-/issues/171) where a user reports that the Anubis prevents software from downloading ASDF tarballs. In our documentation for the project, we tell the users to grab https://gitlab.common-lisp.net/asdf/asdf/-/archive/3.3.7/asdf-3.3.7.tar.gz But if you do that with `curl` or `wget`, you get an HTML page instead of the desired tarball. Is it possible to put a tarball somewhere that it can be automatically retrieved? Or is this impossible with the new flooding protection? In which case we would need to figure out some other way to provide tarballs and other binary blobs. Thanks, R

2 1

ASDF project CI/CD failure
by Robert Goldman 13 Nov '25

13 Nov '25

I was looking at a merge request for ASDF, and it failed all the CI/CD tests. See, for example, https://gitlab.common-lisp.net/rbrown/asdf/-/jobs/103352 What's odd is that it looks like this failure isn't about anything failing, it's about CI/CD not being able to clone the git repo. ``` Getting source from Git repository 00:00 Gitaly correlation ID: 01K9DE5HXE6N8KDGC4YQ4ERFSV Fetching changes... Initialized empty Git repository in /builds/rbrown/asdf/.git/ Created fresh repository. fatal: unable to access 'https://gitlab.common-lisp.net/rbrown/asdf.git/': The requested URL returned error: 500 ``` Any idea what is going haywire here? Thanks! R

3 3

Cliki Maintenance
by David Cooper 09 Nov '25

09 Nov '25

Hi Vladimir, Long time no talk, i hope this finds you well. Hey would you be able to spare a bit of attention to see what it would take to make cliki.net run robustly on our new common-lisp.net host? The instance officially behind cliki.net is currently installed on the legacy host but often falls over (apparently on bad input data) and does not restart automatically. In the process of migrating the live cliki.net instance to our new host, and maybe wrapping with auto restarts, I'd like to make sure it's upgraded to a latest host CL engine, as well as a recent supported Cliki version. But I need some hand-holding to start even with the first part of what I just said. If it would be most convenient, I could give you needed access on both hosts so you can get the lay of the land. Or we can do a real time shared screen session and poke around together to see what builds need to be replicated and ensure the CI behind those. Thanks for Cliki so far and please reply as per your convenience, Dave Cooper dcooper or gendl on libera.chat in #common-lisp.net

1 0

rsync for clnet
by David Cooper 09 Nov '25

09 Nov '25

Hi Carl, Long time no talk.I hope you're doing well. Would you care to help me to install rsync on common-lisp.net and configure it in such a manner to mimic its old configuration on legacy.common-lisp.net ( if you remember that or could reconstruct it or we could dredge it up since the machine is still up and running but apparently the rsync service is no longer working there either? Anyhoo, hope this found you well, please reply as per your convenience. Dave Cooper dcooper or gendl on libera.chat in #common-lisp.net

1 0