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

[clo-devel] Added support: Anonymous checkout of Subversion repositories through HTTP
by Erik Huelsmann 05 Jun '11

05 Jun '11

Last year, there were some people asking for anonymous checkout of some of the Subversion repositories on common-lisp.net, because they were behind corporate proxies. While projects can set up the equivalent for Git themselves, this is not the case for Subversion. To support wider distribution of project sources from common-lisp.net, I've set up anonymous checkout for Subversion-using projects on http://svn.common-lisp.net/<project> The same URL allows browsing the HEAD revision of the repository, although that doesn't seem too relevant anymore, since ViewVC is now available for Subversion browsing too. The svn.common-lisp.net root directory listing is empty because the repositories are collected into one directory using symlinks instead of being true directories; there's not much I can do about that (other than patching the sources and rebuilding mod_dav_svn, which I'm not about to do). Bye, Erik.

1 0

[clo-devel] Subversion repository browsing enabled through ViewVC
by Erik Huelsmann 05 Jun '11

05 Jun '11

Turns out setting up ViewVC to do Subversion repository browsing was trivial once we had a mechanism to collect repository roots in one place. For Subversion, I set up /var/lib/svnroots which has the same purpose as /var/lib/cvsroots. I set up a cron job to fill the svnroots directory with symlinks on a daily interval. All symlinks which points to repositories which don't have a "revision 1" are deleted, assuming that's a good indicator of which projects use Subversion. The http://common-lisp.net/viewvc listing contains CVS and Subversion repositories sorted by alphabet. Bye, Erik.

1 0

[clo-devel] Updating the cl.net website?
by Erik Huelsmann 05 Jun '11

05 Jun '11

What's the preferred way to update the website? I think there are many files sitting in /var/www which don't have an equivalent in /project/clo/public_html. Should we start using rsync with the --delete flag to sync the two to make sure they are exactly the same? I think most of the time the only correct way to edit the clo website would be to edit the files in /project/clo/public_html, isn't it? Bye, Erik.

2 2

[clo-devel] Drop support for ArchZoom?
by Erik Huelsmann 05 Jun '11

05 Jun '11

Since I'm installing repository viewers, I had to look at the list of repository viewers we currently support. We decided to drop ViewSVN, basically because Trac is a great repository viewer and we can easily add more Trac instance, which will provide projects much more than just repository viewing. Since GitWeb, ViewVC and darcsweb have now been set up, the only repository viewer not set up (but supported before) is ArchZoom. Should we drop support for ArchZoom? Are there projects and people using Arch? [I can't even find arch in the list of Debian packages!] If it's not clear from the above, if it were up to me, I'd drop Arch and ArchZoom. Bye, Erik.

3 2

[clo-devel] ViewVC (formerly ViewCVS) set up
by Erik Huelsmann 05 Jun '11

05 Jun '11

Just finished setting up ViewVC. In order to make it work, I had to create a directory /var/lib/cvsroots which contains symlinks to all cvsroots in all projects. This takes advantage of ViewVCs feature to list all repositories in a specific directory. To keep the list current, I installed a nightly cron job: cron.root.update-viewvc-cvsroots.sh. No actual copying takes place, just symlinks to the original repositories. Additionally, I had to install a RedirectMatch because of the name-change. Bye, Erik.

1 1

[clo-devel] Subversion post-commit hook fixed & enhanced
by Erik Huelsmann 04 Jun '11

04 Jun '11

After the migration to new cl.net, Subversion commit mails were broken. Today, I fixed the issue (all links were pointing to a subversion location in /usr/local which didn't get ported over). The links have been changed to all point to /custom/bin/svn-post-{commit,revprop-change} Additionally, I've created a 'mailer.py' configuration file in /custom/conf/svn-mailer.conf which contains all the configuration to work with current and future repositories as long as they are being set up in the /project hierarchy. In the armedbear project, I've long maintained a custom post-commit hookscript which invoked Trac's post-commit script to close or update tickets. This functionality has now been built into the default script, if there is a 'trac' directory residing next to the 'svn' directory within the project. Bye, Erik.

1 1

[clo-devel] Migration status: can we take down old common-lisp.net (aka elephant.common-lisp.net)?
by Erik Huelsmann 31 May '11

31 May '11

It seems Franz changed the DNS for paste.lisp.org, the last service I think which was still running on old common-lisp.net. So, is there any reason not to stop that VM now? There are probably some issues to work through before we can call new common-lisp.net fully operational though. One of the things I know of is the fact that viewCVS isn't working yet. I'll be working on that coming weekend. Another one is that the Subversion commit mails don't seem to get through. Please anybody who has any remaining issues, file bugs at admin(a)common-lisp.net so we can address in an orderly manner. Thanks in advance! Bye, Erik.

1 0

[clo-devel] Migration status [2011-05-21]
by Erik Huelsmann 23 May '11

23 May '11

common-lisp.net migration is progressing nicely: - Today I was able to migrate lisppaste to new common-lisp.net. - At the moment, I'm working to restore the functionality of many of the cron jobs. - The ticket tracker (available at admin at cl-net) is working correctly (did I mention that already?) We're serving multiple domains from common-lisp.net now and most of the services. There are some issues to be solved/ steps to be completed: * cron jobs need to be enabled [working on it] * viewvc needs to be configured correctly * DNS for paste.lisp.org should point to our new IP, or become a CNAME for paste.common-lisp.net [asked Andreas Fuchs to contact Franz system admins, Franz hosts the DNS] Questions: * have git-daemon and gitweb been configured correctly? Remarks: * Some projects stored their binaries in directories related to the old ftp service, which have been removed, because the ftp service has been disabled for years now [project admins should probably be notified] Anybody who wants / is able to comment or complement? Bye, Erik.

2 1

[clo-devel] is viewcvs down?
by Anton Vodonosov 21 May '11

21 May '11

Hello. Is viewcvs down currently, or is it moved to some subdomain? Best regards, - Anton

2 2

Re: [clo-devel] Недоставленное сообщение
by Hans Hübner 18 May '11

18 May '11

Anton, I copied the spamassassin configuration to the new box moments ago. Please let us know if your problem persists. -Hans 2011/5/18 Anton Vodonosov <avodonosov(a)yandex.ru>: > Hello, > > I am getting bounced by common-lisp.net mail server. > > Hans, I remember there was a similar problem earlier, > and you have added me to the spamassasin white list. > Probably the white list is lost during the migration. Could you fix it? > > Best regards, > - Anton > > -------- Forwarded message -------- > 18.05.2011, 01:37, mailer-daemon(a)yandex.ru: > > ********** > > Это письмо отправлено почтовым сервером yandex.ru > > К сожалению, мы вынуждены сообщить Вам о том, что Ваше письмо не может > быть отправлено одному или нескольким адресатам. Причины указаны ниже. > > Пожалуйста, не отвечайте на это сообщение. > > ********** > > This is the mail system at host yandex.ru > > I'm sorry to have to inform you that your message could not > be delivered to one or more recipients. It's attached below. > > Please, do not reply to this message. > > <cl-plus-ssl-devel(a)common-lisp.net>;: host a.mx.common-lisp.net[74.115.254.14] > said: 550 This message scored 2.3 spam points. (in reply to end of DATA > command) > > Reporting-MTA: dns; forward9.mail.yandex.net > X-Yandex-Queue-ID: 5CC7BCE180B > X-Yandex-Sender: rfc822; avodonosov(a)yandex.ru > Arrival-Date: Wed, 18 May 2011 01:26:24 +0400 (MSD) > > Final-Recipient: rfc822; cl-plus-ssl-devel(a)common-lisp.net > Original-Recipient: rfc822;cl-plus-ssl-devel(a)common-lisp.net > Action: failed > Status: 5.0.0 > Remote-MTA: dns; a.mx.common-lisp.net > Diagnostic-Code: smtp; 550 This message scored 2.3 spam points. > -------- End of the forwarded message -------- > Final-Recipient: rfc822; cl-plus-ssl-devel(a)common-lisp.net > Original-Recipient: rfc822;cl-plus-ssl-devel(a)common-lisp.net > Action: failed > Status: 5.0.0 > Remote-MTA: dns; a.mx.common-lisp.net > Diagnostic-Code: smtp; 550 This message scored 2.3 spam points. > > > ---------- Forwarded message ---------- > From: Anton Vodonosov <avodonosov(a)yandex.ru> > To: Attila Lendvai <attila.lendvai(a)gmail.com> > Date: Wed, 18 May 2011 01:26:23 +0400 > Subject: Re: [cl-plus-ssl-devel] concurrency problems when used with chrome? > Hello Attila, > > There is an outstanding multi-threading problem which so far was confirmed > for CCL + Windows. We thought for Linux it works OK (it was tested with ApacheBench). > You may find more details in the recent cl-plus-ssl-devel archives. > In short, this problem is not easy to catch, and there is a hight probability if > will remain unfixed in the nearest months. > > What is your platform (OS and Lisp impl)? Any other details you think relevant? > > As a workaround, until the problem is fixed, you may need to use a reverse proxy like > nginx for https. > > Best regards, > - Anton > > 18.05.2011, 00:49, "Attila Lendvai" <attila.lendvai(a)gmail.com>: >> dear list, >> >> i've successfully added https support to hu.dwim.web-server, which >> thanks to cl+ssl was much less trouble (for now) than i've expected. >> >> it seems to work mostly fine with ff and opera, but with chrome i get >> the following error randomly in half of the worker threads (one worker >> for one connection): >> >> The TLS/SSL connection on handle #.(SB-SYS:INT-SAP #X00C1C4A0) has >> been closed. (return code: 5)SSL error queue: >> >> [Condition of type CL+SSL::SSL-ERROR-ZERO-RETURN] >> >> the relevant part of the backtrace: >> >> 5: ((LABELS HU.DWIM.UTIL::HANDLE-LEVEL-1-ERROR) >> #<CL+SSL::SSL-ERROR-ZERO-RETURN {10088187B1}>) >> 6: (SIGNAL #<CL+SSL::SSL-ERROR-ZERO-RETURN {10088187B1}>) >> 7: (ERROR CL+SSL::SSL-ERROR-ZERO-RETURN :HANDLE #.(SB-SYS:INT-SAP >> #X7FFFEC0654B0) :RET 5 :QUEUE "SSL error queue: \n") >> 8: (CL+SSL::SSL-SIGNAL-ERROR #.(SB-SYS:INT-SAP #X7FFFEC0654B0) >> #<FUNCTION CL+SSL::SSL-READ> 5 0) >> 9: ((FLET #:WPO[READ-HTTP-REQUEST/HEAD]46)) >> 10: (HU.DWIM.WEB-SERVER::READ-HTTP-REQUEST/HEAD 15 >> #<CL+SSL::SSL-SERVER-STREAM for 15> #.(SB-SYS:INT-SAP #X7FFFEC0654B0) >> :LENGTH-LIMIT 65536) >> >> i suspect that there's something inside cl+ssl that is not threadsafe, >> because afaik chrome is more aggressively parallel than the others... >> maybe there's a C struct that should be thread local and is a mere >> global? >> >> unfortunately my first glance didn't find anything suspicious. >> >> any ideas how to proceed with this? >> >> -- >> attila >> >> Notice your eroding (digital) freedom, and do something about it! >> >> PGP: 2FA1 A9DC 9C1E BA25 A59C 963F 5D5F 45C7 DFCD 0A39 >> OTR XMPP: 8647EEAC EA30FEEF E1B55146 573E52EE 21B1FF06 >> BitCoin: 154uf86Vd9rpjMULd9CXa7nVwikknYZJiB >> >> _______________________________________________ >> cl-plus-ssl-devel mailing list >> cl-plus-ssl-devel(a)common-lisp.net >> http://lists.common-lisp.net/cgi-bin/mailman/listinfo/cl-plus-ssl-devel > >

2 1