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

[clo-devel] New Unpaid Item Message from tany70 : #294653688662
by eBay＠common-lisp.net 14 Oct '06

14 Oct '06

1 0

[clo-devel] Fixing wrong mailman listnames.
by Erik Enge 11 Oct '06

11 Oct '06

Many months ago something happened to our mailinglist config files (they are named config.pck by Mailman). I don't recall the details but I think maybe it was a bug in Mailman. Anyway, the result was that the "real_name" attribute of some mailinglists was changed to some other mailinglist's name. For instance, Alastair just noticed that cl-cli-parser-cvs was named beep-cvs (everything still works; it's just the real_name attribute that's wrong). I think I've fixed most of these but there's a script that will do it for any that's still missing: /custom/bin/fix-wrong-list-name.py cl-cli-parser-cvs \ /custom/sys/mailman/mailman/lists/cl-cli-parser-cvs/config.pck So you pass it the correct real_name and then the config file to edit. (I just took care of this for cl-cli-parser-cvs.) Thanks, Erik.

1 0

[clo-devel] Upgrading mailman on common-lisp.net
by Erik Enge 11 Oct '06

11 Oct '06

I just upgraded mailman. They have a security announcement for mailman every other month or so. We have two custom changes that we have to apply after the upgrade: a) see /custom/pak/mailman/HTMLFormatter.py's RestrictedListMessage and copy-paste (or make a patch) into the new one in /usr/lib/mailman/Mailman/HTMLFormatter.py b) Comment out line 119 and 120 in /usr/lib/mailman/cron/nightly_gzip (the lines that print "bogus archive") I just did this and hopefully we shouldn't have to mess with it again for a few months but now the information has been shared for prosperity. Also note that the actual list archives and config files for the lists are in symlinked from /var/lib/mailman into /custom/sys/mailman. I did this a few years back just in case a mailman upgrade decided to screw up our archives or config files. Thanks, Erik.

1 0

[clo-devel] The clo project on common-lisp.net.
by Erik Enge 10 Oct '06

10 Oct '06

Ok, one more thing. The "clo" project on common-lisp.net is the project to manage the site itself. Originally it was common-lisp.org, so that's where we get the c-l-o from. Now its CVS tree hosts the webpages you see when you visit http://common-lisp.net/ and its trac instance has our TODO list: http://trac.common-lisp.net/clo So there are some people subscribed to clo-devel that care about how we admin the box so I usually CC this list whenever I discuss these matters. Thanks, Erik.

1 0

[clo-devel] Perennial admin issue with cvs pserver on common-lisp.net
by Erik Enge 10 Oct '06

10 Oct '06

I wanted to share this with you and make it available on the mailinglist because it took me a few minutes to figure out and it's a stupid issue so I don't want you to waste any time on it. The cvs pserver passes all repositories that it wants to serve, on the command line. Thus, how many repositories you can serve is limited by how many characters you can pass on the command line. This is really silly because there's already a config file where it can read this from (/etc/cvsd/cvsd.conf). I haven't found a way around it. So, every now and then, someone will complain that pserver checkouts (anonymous cvs access) doesn't work. Usually there will be some "pam_auth token not released" error of some sort. What I do then is that I edit the /etc/cvsd/cvsd.conf file and remove all projects who are using svn, darcs or arch (I check the project page, they usually announce this) until cvs pserver works again. Then it works until I have added enough projects to make it break again at which point I go back and revise which of the new projects aren't using CVS. I don't have a longterm fix for that one yet but it's probably something we need to address over the next year. One possible solution is to symlink /project to /p which will drastically shorten the arguments to cvsd on the command line but this would mean that anonymous CVS users would have to specify anonymous@common-lisp.net:/p/project/cvsroot and SSH CVS users would still use :/project/project/cvsroot - that's probably going to confuse the hell out of alot of people. Erik.

1 0

[clo-devel] More information about admining common-lisp.net.
by Erik Enge 10 Oct '06

10 Oct '06

Now that you have the passwords you can start approving any projects that come in. Usually there's one or two a week so don't expect to be busy. ;-) You should subscribe to the admin, clo-devel and system-notification mailinglists if you haven't already. Thanks again, Erik.

1 0

[clo-devel] common-lisp.net admins
by Erik Enge 10 Oct '06

10 Oct '06

Hi guys, thanks for volunteering to help me out. I'm starting a new job this week and it'll be hectic over the next few months. I really like what common-lisp.net provides to the community so I figure instead of risking anything I wanted to reach out and get some help. I will continue to pay for the server from the donated money so you don't have to worry about that part. To give you an idea, here's what's required on a week-to-week basis: - monitor system-notifications@ mailinglist for warnings about diskspace or integrit failures (integrit is similar to tripwire) - run /custom/bin/add-user.sh and /custom/bin/add-project.sh - on occasion run /custom/bin/add-trac.sh - run /custom/bin/update-integrit whenever you change something That's mostly it. To figure out what the server is doing you can start by visiting /etc/crontab and see all processes that are ran every day. Mostly everything just works but there are a good bit of things actually running. People will mail requests to admin@ for a new project. Our job is to make sure they give us all information we need (licence, project name, project members and any GPG keys) and then run the appropriate scripts. I usually go ahead and approve projects as long as the license is open-source although if there's another Common Lisp project out there with the exact name I will want to get in touch with that person first and see what's going on (see the admin list archives for cl-screen, for an example). I'll send you guys an encrypted email with the root password shortly but I will not CC the list for that one. Please feel free to call me on 770-906-7641 if you have any questions and I can't be reached by email. Since we will now be three admins we have introduced a race condition about approving projects. I suggest as a policy the person approving/creating a project replies immediately to that request saying something like "Ok, I'll take care of this" so the other admins know not to try anything. Opinions welcome, of course. Lastly, it's not too late to back out if this is more than you think you signed up for, no hard feelings. Thanks, Erik.

1 0