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

Re: Clo-devel Problem?
by Mark Evenson 16 Jan '21

16 Jan '21

> On Jan 16, 2021, at 11:11, Philipp Marek <philipp(a)marek.priv.at> wrote: > > Hi, > > both Mark and I answered the plea for resetting a mailing list moderator password; as I didn't see his reply, I guess he didn't see mine either. > > The logical conclusion is that the mailing list is broken in some way. > > It's not that urgent, I guess; perhaps I can find time to take a look later on. > If someone beats me to it, please reply here ;) > I restarted the mailman service, but there were what looked like defunct processes: mevenson@common-lisp:~$ ps -auxww | grep mailman list 1528 0.0 0.0 41624 4872 ? Ss Jan03 0:00 /usr/bin/python /usr/lib/mailman/bin/mailmanctl -s -q \ start list 1529 0.0 0.1 45368 18404 ? D Jan03 3:20 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=\ ArchRunner:0:1 -s list 1530 0.0 0.1 43908 15740 ? D Jan03 3:24 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=\ BounceRunner:0:1 -s list 1531 0.0 0.1 41912 13676 ? D Jan03 3:08 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=\ CommandRunner:0:1 -s list 1532 0.0 0>.1 47392 18432 ? D Jan03 3:21 /usr/bin/python /var/lib/mailman/bin/qrunner --runner\ =IncomingRunner:0:1 -s list 1533 0.0 0.1 41512 14180 ? D Jan03 3:06 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=\ NewsRunner:0:1 -s list 1534 0.0 0.1 47796 18936 ? D Jan03 3:43 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=\ OutgoingRunner:0:1 -s list 1535 0.0 0.1 46840 16496 ? D Jan03 3:23 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=\ VirginRunner:0:1 -s list 1536 0.0 0.1 41492 14164 ? D Jan03 0:00 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=\ RetryRunner:0:1 -s mevenson 1916862 0.0 0.0 8168 828 pts/6 S+ 12:00 0:00 grep mailman So, I stopped the mailman service, killed all these processes, and restarted. We’ll see if that fixes anything. -- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."

2 2

Fwd: 1 usocket-devel moderator request(s) waiting
by Chun Tian 16 Jan '21

16 Jan '21

Hi, happy new year. I lost my moderator password of the usocket mailing list after changing to a new laptop. Could you reset my password? (a random one would be fine). Regards, Chun Tian > Begin forwarded message: > > From: usocket-devel-bounces(a)common-lisp.net > Subject: 1 usocket-devel moderator request(s) waiting > Date: January 15, 2021 at 09:00:13 GMT+1 > To: usocket-devel-owner(a)common-lisp.net > > The usocket-devel(a)common-lisp.net mailing list has 1 request(s) > waiting for your consideration at: > > https://mailman.common-lisp.net/admindb/usocket-devel > > Please attend to this at your earliest convenience. This notice of > pending requests, if any, will be sent out daily. > > > Pending posts: > From: frodevf(a)gmail.com on Tue Jan 12 08:16:15 2021 > Subject: Bug in vector-quad-to-dotted-quad etc. > Cause: Post by non-member to a members-only list

3 3

Testing
by Raymond Toy 17 Dec '20

17 Dec '20

Testing to see if I can send messages to this list and also see them. -- Ray

1 0

Fwd: Delivery Status Notification (Delay)
by Jean-Claude Beaudoin 08 Dec '20

08 Dec '20

24 hours ago or so, I tried to post to the PRO-CL list from my gmail account and here is below what googlemail answered me back! Is there a problem with the mailing-list server on common-lisp.net? ---------- Forwarded message --------- From: Mail Delivery Subsystem <mailer-daemon(a)googlemail.com> Date: Tue, Dec 8, 2020 at 12:11 AM Subject: Delivery Status Notification (Delay) To: <jean.claude.beaudoin(a)gmail.com> [image: Error Icon] Delivery incomplete There was a temporary problem delivering your message to *pro(a)common-lisp.net*. Gmail will retry for 47 more hours. You'll be notified if the delivery fails permanently. The response from the remote server was: 451 Temporary local problem - please try later ---------- Forwarded message ---------- From: Jean-Claude Beaudoin <jean.claude.beaudoin(a)gmail.com> To: Common Lisp pros <pro(a)common-lisp.net> Cc: Bcc: Date: Sun, 6 Dec 2020 23:52:57 -0500 Subject: In CLOS, instance remorphing considered useless in practice? ----- Message truncated -----

1 0

Gitlab security warnings
by Robert Goldman 02 Dec '20

02 Dec '20

When I connect to the Gitlab repo for ASDF at cl.net, I am seeing this banner: ![](cid:86F10C45-6DAA-4818-9D3F-1B9E6B97C882@sift.info "PastedImage.png") I have no idea what this means, but whatever it is, reloading the page does not resolve it. Any idea what this is? Thanks, R

3 2

Proposal: project pages deployment through GitLab
by Erik Huelsmann 18 Nov '20

18 Nov '20

Hi all, As you all have noticed, I've been working to clean up common-lisp.net and simplifying the administration process. One of the things we have done is that we implemented a deployment pipeline for the common-lisp.net main site using GitLab. It's been a great joy to work with it so far and made deployment of new site content easier than ever before. *My proposal is to set up a GitLab CI based deployment pipeline* for *all common-lisp.net <http://common-lisp.net> projects*. Meaning that I'm proposing to import the current project pages (/project/*/public_html) into GitLab repositories (<project-name>-site) with a gitlab-ci file which causes the content to be published. The approach above will mean simple import of the existing static content. However, after import, the static output can be replaced by different input and a static content generator, just like we did with the common-lisp.net site. Eager to hear your thoughts, Erik.

5 8

cl.net https certificate expired
by Anton Vodonosov 01 Nov '20

01 Nov '20

2 1

CI capacity?
by Raymond Toy 16 Oct '20

16 Oct '20

All this talk about Jenkins and ASDF makes we wonder how much capacity is available for CI on common-lisp.net. I've been reluctant to run much except for the website generator on c-l.net. This doesn't run very often so I don't think it's a burden. For my other work, I use my own machines so as not to load c-l.net too much. (But CI doesn't run very often on my own machines---maybe a couple times per month, but tends to be very bursty depending on how much free time and motivation I have.) I also didn't want to interfere with trac and gitlab for all the projects on the site. -- Ray

1 0

Re: Jenkins expertise?
by Dave Cooper 16 Oct '20

16 Oct '20

Dear Robert, Are you sure you want to use Jenkins? Gitlab has built-in CI. And the CLF has acquired Allegro CL licenses for a ASDF testing (graciously donated by Franz Inc), and we have a to-do item to attempt the same for LispWorks. If you’re willing, we would like to help set up ASDF testing pipelines as part of common-lisp.net infrastructure. If you have reasons of your own to set up a Jenkins setup and could use access to Allegro and maybe Lispworks licenses for that purpose, please reach out regarding that as well. I am not sure about any Jenkins experience among clf or cl.net volunteers, however. Please advise, Dave On Tue, Oct 13, 2020 at 11:06 PM Robert Goldman <rpgoldman(a)sift.info> wrote: > Does anyone have expertise configuring Jenkins to run against a remote > Gitlab install? > > If so, would you please reach out to me? I have *finally* restored some > of my CI support for ASDF, but I don't know how to set up my Jenkins to run > against merge requests on Gitlab (if that is even possible). > > I have a backlog of patches that I would like to get evaluated and merged, > but could use some help with the automation. > > Thanks! > -- My Best, Dave Cooper, david.cooper(a)gen.works genworks.com, gendl.org +1 248-330-2979

3 3

Trac on common-lisp.net
by Erik Huelsmann 10 Oct '20

10 Oct '20

Hi, The VM running common-lisp.net needs an O/S upgrade: the host is running Debian Stretch which has gone EOL in July (but is receiving LTS updates for specific components). Due to package compatibility issues, the upgrade needs to go directly to Debian Bullseye (skipping Debian Buster). We have a dependency problem with this upgrade: Debian Buster - which we'll skip - was the last to support Python 2.7. We depend on Python 2.7 for the following services: Trac, Mailman2.1, ViewVC and greylistd. All other services either don't depend on Python, or have Python3 compatible versions in Debian Bullseye. For Mailman2.1 we have a "simple" solution: migration to Mailman3. Mailman3 is a totally new application coming from the developers of Mailman2.1. For greylistd we will be able to either find an alternative or we can stop greylisting entirely. For ViewVC, we hope to see a release soonish which supports Python3 (and its inclusion in Debian); in its repository, there's support for Python3 already, as is the required Python3 support for the Subversion bindings. This leaves us with just Trac which has been removed from Debian because of its Python 2.7 dependency. Looking at its homepage, there doesn't seem to be a Python3 compatible release yet. I really want to be running OS packages, because those include (security) releases when issues are found -- which saves the common-lisp.net manual monitoring of our dependencies. These projects have Trac projects: armedbear bknr cl-darcs cl-irc cl-markdown cl-openid cl-test-grid cl-trane cl-weblocks clfswm clo cmucl elephant f2cl fset gsharp isidorus mcclim movitz nio oct ucw usocket So what's our next step? Do we go looking for a Trac alternative? Does anybody have contacts with the Trac team and can consult with them about their plans? Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

4 3