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

TeX missing?
by Raymond Toy 31 Mar '25

31 Mar '25

I’m a bit confused here. According to this pipeline that was run on a branch <https://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/jobs/82062>, TeX is installed because I could build the cmucl docs which uses TeX to generate the pdf version. However, the pipeline on the master branch <https://gitlab.common-lisp.net/cmucl/cmucl.common-lisp.dev/-/jobs/82068> says TeX isn’t installed. And indeed when I ssh to gitlab.common-lisp.net, I can’t find latex, texi2dvi or any of the usual TeX binaries anywhere. Could I have TeX installed, please, if it’s not actually installed somewhere? -- Ray

2 2

GraphQL error: Field 'troubleshootJobWithAi' doesn't exist on type 'Pipeline'
by Raymond Toy 17 Feb '25

17 Feb '25

Look at this pipeline <https://gitlab.common-lisp.net/cmucl/cmucl/-/merge_requests/265/pipelines>. Part way down, there appears an expand button with the label "Failed jobs". This seems new. Anyway, I clicked the button and I get the GraphQL error in the subject line. I guess this new thing (?) isn't working quite right. But I probably don't need AI to tell me what I screwed up in the CI job. :-) At least in this pipeline. 

1 0

Fwd: asdf-devel@common-lisp.net post from monacoandrea94@gmail.com requires approval
by Robert Goldman 01 Feb '25

01 Feb '25

I received the following overnight. However, when I logged into the Postorious site, there were no held messages for me to release. Not only were there no messages to release, this message seems to have been discarded, since I never received a copy of it from the mailing list. Any chance this is related to the recent discussion of spam filtering? Forwarded message: > From: asdf-devel-owner(a)common-lisp.net > To: asdf-devel-owner(a)common-lisp.net > Subject: asdf-devel(a)common-lisp.net post from monacoandrea94(a)gmail.com > requires approval > Date: Sat, 01 Feb 2025 11:10:25 +0000 > > As list administrator, your authorization is requested for the > following mailing list posting: > > List: asdf-devel(a)common-lisp.net > From: monacoandrea94(a)gmail.com > Subject: Edge case of TIMESTAMP<= > > The message is being held because: > > The message is not from a list member > > At your convenience, visit your dashboard to approve or deny the > request.

2 2

How to deal with mailing list ownership & moderators & spam to the lists?
by Erik Huelsmann 01 Feb '25

01 Feb '25

Hi, Daily, my mailbox is bombarded with mails reminding me to moderate mailing list traffic on common-lisp.net. On occasion I have acted on these messages, if I saw one come by where genuine traffic was held. Most of the time, they are mails trying to sell eBikes and other junk, though. While I haven't acted much on them, they do present distraction, both of genuine mail traffic as well as in my mind. I want to remove that distraction. Out of curiosity, I picked the last reminder I received this morning. It was from cells-devel@ . There are no moderators, which means that reminders go to the owners: Kenny Tilton and cl-net root@ (that is: Mark Evenson, Dave Cooper, Philipp Marek and me). There is a list of 333 moderations waiting. Accumulated between August 2024 and today. Actual list traffic: 1 mail in 2020 (without response!) and the last one before that was from 2012. The before-last reminder was to cffi-devel@. There 113 moderations are waiting. Last and before-last active mail threads (including replies) are from 2023 and 2021 respectively. Owner of the list are Luis Oliveira and root@; again, no moderators. Conclusion: Although not as bad as with cells, nobody is acting on these reminders for cffi-devel either. The one before that: cl-opengl-devel@. Same story: 95 waiting moderations, most recent mail threads from 2022 and 2020. So, I see the following options (other than adding mail filters which simply delete these things on my side): 1. Remove root@ from the list of owners -- which presumably means root@ can't help with admin tasks for these mailing lists anymore 2. Copy the owners - excluding root@ - to the moderators so the flow to root@ stops 3. Forcibly set mailing lists to drop non-member posts - the current default seems to be to hold for moderation Additionally, we could archive (remove submission possibility) for mailing lists which haven't received a single post for more than 5(?) or 7(?) or ... years. I'm looking for the best way forward for common-lisp.net here, not for my personal mailbox. What do you say? -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

3 3