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

[clo-devel] Slime docs missing?
by Zach Beane 17 May '11

17 May '11

http://common-lisp.net/projects/slime/ has many broken images on it and the link to the manual, http://common-lisp.net/projects/slime/doc/html/, is broken - it gives a 404. What happened? Is there anything I can do to help fix? Zach

2 1

[clo-devel] SLIME updates warning
by Zach Beane 16 May '11

16 May '11

I get this message when I try to update SLIME from anonymous CVS: cvs update: warning: cannot open history file `/project/slime/cvsroot/CVSROOT/history' for write: Permission denied What should I do? Zach

2 2

[clo-devel] Migration status update [2011-05-13]
by Erik Huelsmann 14 May '11

14 May '11

As Hans wrote in a mail just ago, we're progressing nicely on the migration to the new server. These steps have been completed: * MTA is now on the new server * lists.common-lisp.net is served by the new server [traffic to http://common-lisp.net/{mailman/,pipermail/} is forwarded to http://lists.common-lisp.net/...] * trac.common-lisp.net is served by the new server * ssh traffic is handled by the new server (except for just a few of us who still need access to the old server) * the ticketing system is now on the new server (old tickets will be handled from the old system; data is not migrated) * the cron jobs are gradually being turned on [only partially done] Remaining steps: * configure the remaining cron jobs * configure the common-lisp.net vhost (with the same forwarding rules that are on old-* to forward the mailman links) * configure viewcvs * compile an SBCL which will run the IRC bots stably (Stelian works on it) I don't think we need WebSVN anymore: we have Trac now. Any other steps I forgot? (Probably lots...) Bye, Erik.

2 1

[clo-devel] New rt installation
by Hans Hübner 13 May '11

13 May '11

Hi, I have just installed a fresh copy of RT for request tracking on the new box. I prefer rt to otrs because it allows me to handle requests mostly by email, which is something that otrs does not seem to do. Currently, Erik and myself are on the list of recipients for new tickets. We'd be happy to see more folks join in. If you are interested in getting an rt account and rights to handle incoming emails, please let me know and I'll set things up for you. -Hans

1 0

[clo-devel] Abandoned projects
by Hans Hübner 13 May '11

13 May '11

Hi, what do we want to do with abandoned projects? By abandoned, I mean projects where the owner has become unreachable at the email address that he has provided or configured in their .forward file? Several users of common-lisp.net are no longer reachable by email, and mailman bounces moderation reminder emails back to us, which does not make a whole lot of sense. I tend to think that deleting (archiving) such project mailing lists would be best. If anyone is interested, they can always get in touch with us. Thoughts? Hans

5 8

[clo-devel] Migration status [2011-05-06]
by Erik Huelsmann 12 May '11

12 May '11

These things happened last week: * ssh connections to cl-net were routed to new-cl-net * we were asked to install several applications on new-cl-net (emacs, zsh) * we started to create subdomains for services (first: git.cl.net) * after being reported that people were missing group memberships, we've now migrated all project related groups with a gid < 1000; because those numbers are reserved for system groups, they were excluded from the account/group migration. In order to prevent similar issues in the future, all these groups have been renumbered. There's currently a batch running to re-assign all group ownerships in the file systems * we stopped routing traffic to new-cl-net because commit mails were no longer coming through [the mailer wasn't fully set up yet on new-cl-net] Next steps: * set up the mailer * re-instate the ssh traffic route to new-cl-net * set up the webserver in order to be able to migrate trac.c-l.net Anybody who wants to use new-cl-net services directly should log into tiger.common-lisp.net; passwords and ssh keys are the same as on common-lisp.net (aka elephant.common-lisp.net) Bye, Erik.

3 6

Re: [clo-devel] Commit fail on USOCKET SVN
by Hans Hübner 11 May '11

11 May '11

problem fixed. On Wednesday, May 11, 2011, Chun Tian (binghe) <binghe.lisp(a)gmail.com> wrote: > Hi, Hans > > Still cannot commit. But I tried my other project's SVN on cl.net, i.e. cl-net-snmp, svn commit is OK. So I guess this maybe a usocket specific issue. Now I've done a full dump of usocket svn data, and try to rebuild it into a new repository directory. > > But I need some root help, the first is following command: > > chmod g+w /project/usocket > > This let me (ctian, member of usocket group) could modify project root directory to create any new top-level directory. > > Regards, > > Chun Tian (binghe) > > 在 2011-5-11，13:47， Hans Hübner 写道： > >> Drew fixed the box and I manually mounted the nfs file systems. >> Please try again! >> >> -Hans >> >> 2011/5/11 Hans Hübner <hans.huebner(a)gmail.com>: >>> Oh well, I rebooted the box, but it fails to come up again. Drew will >>> have to take care of this. Sorry. >>> >>> -Hans >>> >>> 2011/5/11 Chun Tian (binghe) <binghe.lisp(a)gmail.com>: >>>> Hi, Hans >>>> >>>> Thanks for taking care this, but I'm afraid that the problem is still there. Below is what I did in past minutes: >>>> >>>> """ >>>> binghe@binghe-i7:~/Lisp/usocket/branches/0.5.x/test$ LANG=C svn ci -m "[test] Issue elliott-slaughter.2 (WAIT-FOR-INPUT/win32 on TCP socket)" >>>> Sending test/wait-for-input.lisp >>>> Transmitting file data .svn: Commit failed (details follow): >>>> svn: Can't get exclusive lock on file '/project/usocket/svn/db/write-lock': No locks available >>>> """ >>>> >>>> As a Linux administrator, I think the theory behind your NFS fix is good, but to make the configuration change actually applied to current system, you have to completely unmount the NFS volumes on common-lisp.net, and do a full restart of NFS related services and then mount them again. Or, A simply reboot of common-lisp.net (I'm not sure if it's virtual machine) could achieve the goal easily. But any of the two choices would cause services temporary shutdown. >>>> >>>> Regards, >>>> >>>> Chun Tian (binghe) >>>> >>>> 在 2011-5-11，12:38， Hans Hübner 写道： >>>> >>>>> Hi Binghe, >>>>> >>>>> thank you for reporting the problem. I have made a change in the NFS >>>>> configuration (http://gibbonsr.net/2009/02/nfs-and-subversion-it-can-work/) >>>>> so that Subversion should now work. Can you please give it a try and >>>>> let me know if it is okay? >>>>> >>>>> common-lisp.net is currently being migrated to a new "box", which is >>>>> why there may be some issues in the coming days and week. Please >>>>> don't hesitate to report them. >>>>> >>>>> Thanks, >>>>> Hans >>>>> >>>>> 2011/5/11 Chun Tian <binghe.lisp(a)gmail.com>: >>>>>> Hi, Hans >>>>>> >>>>>> Are you still an administrator of common-lisp.net? Recently I cannot commit to USOCKET SVN any more, my SVN client said: >>>>>> >>>>>>> "Commit failed: Can't get exclusive lock on file '/project/usocket/svn/db/write-lock': No locks available" >>>>>> >>>>>> I think this may be caused by NFS on common-lisp.net, please help me confirm if any other developer met the same issue. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Chun Tian (binghe) >>>>>> >>>>>> 下面是被转发的邮件： >>>>>> >>>>>>> 发件人: "Chun Tian (binghe)" <binghe.lisp(a)gmail.com> >>>>>>> 日期: 2011年5月10日 23时52分42秒+0800 >>>>>>> 收件人: Erik Huelsmann <ehuels(a)gmail.com> >>>>>>> 主题: Commit fail on USOCKET SVN >>>>>>> >>>>>>> Hi, Erik >>>>>>> >>>>>>> I think USOCKET SVN have something wrong, because I cannot commit new code to it, the error message is: >>>>>>> >>>>>>> "Commit failed: Can't get exclusive lock on file '/project/usocket/svn/db/write-lock': No locks available" >>>>>>> >>>>>>> I

1 0

Re: [clo-devel] Commit fail on USOCKET SVN
by Hans Hübner 11 May '11

11 May '11

Drew fixed the box and I manually mounted the nfs file systems. Please try again! -Hans 2011/5/11 Hans Hübner <hans.huebner(a)gmail.com>: > Oh well, I rebooted the box, but it fails to come up again. Drew will > have to take care of this. Sorry. > > -Hans > > 2011/5/11 Chun Tian (binghe) <binghe.lisp(a)gmail.com>: >> Hi, Hans >> >> Thanks for taking care this, but I'm afraid that the problem is still there. Below is what I did in past minutes: >> >> """ >> binghe@binghe-i7:~/Lisp/usocket/branches/0.5.x/test$ LANG=C svn ci -m "[test] Issue elliott-slaughter.2 (WAIT-FOR-INPUT/win32 on TCP socket)" >> Sending test/wait-for-input.lisp >> Transmitting file data .svn: Commit failed (details follow): >> svn: Can't get exclusive lock on file '/project/usocket/svn/db/write-lock': No locks available >> """ >> >> As a Linux administrator, I think the theory behind your NFS fix is good, but to make the configuration change actually applied to current system, you have to completely unmount the NFS volumes on common-lisp.net, and do a full restart of NFS related services and then mount them again. Or, A simply reboot of common-lisp.net (I'm not sure if it's virtual machine) could achieve the goal easily. But any of the two choices would cause services temporary shutdown. >> >> Regards, >> >> Chun Tian (binghe) >> >> 在 2011-5-11，12:38， Hans Hübner 写道： >> >>> Hi Binghe, >>> >>> thank you for reporting the problem. I have made a change in the NFS >>> configuration (http://gibbonsr.net/2009/02/nfs-and-subversion-it-can-work/) >>> so that Subversion should now work. Can you please give it a try and >>> let me know if it is okay? >>> >>> common-lisp.net is currently being migrated to a new "box", which is >>> why there may be some issues in the coming days and week. Please >>> don't hesitate to report them. >>> >>> Thanks, >>> Hans >>> >>> 2011/5/11 Chun Tian <binghe.lisp(a)gmail.com>: >>>> Hi, Hans >>>> >>>> Are you still an administrator of common-lisp.net? Recently I cannot commit to USOCKET SVN any more, my SVN client said: >>>> >>>>> "Commit failed: Can't get exclusive lock on file '/project/usocket/svn/db/write-lock': No locks available" >>>> >>>> I think this may be caused by NFS on common-lisp.net, please help me confirm if any other developer met the same issue. >>>> >>>> Thanks, >>>> >>>> Chun Tian (binghe) >>>> >>>> 下面是被转发的邮件： >>>> >>>>> 发件人: "Chun Tian (binghe)" <binghe.lisp(a)gmail.com> >>>>> 日期: 2011年5月10日 23时52分42秒+0800 >>>>> 收件人: Erik Huelsmann <ehuels(a)gmail.com> >>>>> 主题: Commit fail on USOCKET SVN >>>>> >>>>> Hi, Erik >>>>> >>>>> I think USOCKET SVN have something wrong, because I cannot commit new code to it, the error message is: >>>>> >>>>> "Commit failed: Can't get exclusive lock on file '/project/usocket/svn/db/write-lock': No locks available" >>>>> >>>>> I searched on Internet [1], but all possible reasons (file system permission, disk full, svnadmin recover) have been checked, nothing found and I still cannot commit. It's a shame to me because I'm a SVN administrator in my working company ... >>>>> >>>>> Please confirm if you can commit anything to USOCKET SVN, or just help me solve this. >>>>> >>>>> Regards, >>>>> >>>>> Chun Tian (binghe) >>>>> >>>>> [1] http://www.opensubscriber.com/message/users@subversion.tigris.org/7277559.h… >>>>> >>>>> >>>> >>>> >> >> >

1 0

Re: [clo-devel] Commit fail on USOCKET SVN
by Hans Hübner 11 May '11

11 May '11

Hi Binghe, thank you for reporting the problem. I have made a change in the NFS configuration (http://gibbonsr.net/2009/02/nfs-and-subversion-it-can-work/) so that Subversion should now work. Can you please give it a try and let me know if it is okay? common-lisp.net is currently being migrated to a new "box", which is why there may be some issues in the coming days and week. Please don't hesitate to report them. Thanks, Hans 2011/5/11 Chun Tian <binghe.lisp(a)gmail.com>: > Hi, Hans > > Are you still an administrator of common-lisp.net? Recently I cannot commit to USOCKET SVN any more, my SVN client said: > >> "Commit failed: Can't get exclusive lock on file '/project/usocket/svn/db/write-lock': No locks available" > > I think this may be caused by NFS on common-lisp.net, please help me confirm if any other developer met the same issue. > > Thanks, > > Chun Tian (binghe) > > 下面是被转发的邮件： > >> 发件人: "Chun Tian (binghe)" <binghe.lisp(a)gmail.com> >> 日期: 2011年5月10日 23时52分42秒+0800 >> 收件人: Erik Huelsmann <ehuels(a)gmail.com> >> 主题: Commit fail on USOCKET SVN >> >> Hi, Erik >> >> I think USOCKET SVN have something wrong, because I cannot commit new code to it, the error message is: >> >> "Commit failed: Can't get exclusive lock on file '/project/usocket/svn/db/write-lock': No locks available" >> >> I searched on Internet [1], but all possible reasons (file system permission, disk full, svnadmin recover) have been checked, nothing found and I still cannot commit. It's a shame to me because I'm a SVN administrator in my working company ... >> >> Please confirm if you can commit anything to USOCKET SVN, or just help me solve this. >> >> Regards, >> >> Chun Tian (binghe) >> >> [1] http://www.opensubscriber.com/message/users@subversion.tigris.org/7277559.h… >> >> > >

1 0

[clo-devel] Managing (version controlling) the common-lisp.net main website
by Erik Huelsmann 08 May '11

08 May '11

The clo project contains a copy of the c-l.net website in its repository. This repository is checked out in the public_html directory of the clo project and synced hourly from there to the main web pages in /var/www. However, if I look at the /var/www directory, it contains much more than what's in the clo directory and repository. To resolve this situation, I'd like to copy all files in /var/www to the clo project and add them to the repository. There were ideas from others - I believe Raymond and Stelian - to use a different solution to maintain the website; maybe using a CMS or wiki-based system which allows WYSIWYG editing on the web. For now, I'm going with my "copy back" solution. However, it looks to me like we do need *some* kind of enhanced control. (Maybe even just a description of location of different kinds of files for maintainers to consult?) Bye, Erik.

1 0