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

Signing up via github and/or google?
by Raymond Toy 14 Apr '15

14 Apr '15

Does that work yet? I just tried using my github and google accounts. Neither of them work. Mostly just curious, since I, of course, have an account. But what about new users? -- Ray

2 2

Old git URLs
by Anton Vodonosov 13 Apr '15

13 Apr '15

Hello, I have just discovered that old git URLs, mentioned in various web pages and manuals do not work. For example, git clone git://common-lisp.net/projects/asdf/asdf.git fails with fatal: unable to connect to common-lisp.net: common-lisp.net[0: 148.251.248.130]: errno=Connection refused common-lisp.net[1: 2a01:4f8:200:4310::30]: errno=Network is unreachable New format, as suggested at GitLab project pages: git clone git@common-lisp.net:asdf/asdf.git works. It makes sense, if technically possible, to support old addresses too. Best regards, - Anton

2 2

Mailing list history repaired and restored
by Erik Huelsmann 10 Apr '15

10 Apr '15

Hi, The mailing list history has been restored, finally! The scattered mailing list histories (old mailman system, mlmmj intermediate and new mailman system) have been merged into one and the HTML archives have been re-generated. You should find the history of your favorate mailing list(s) at https://mailman.common-lisp.net/pipermail/ -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

4 6

Git hooks for sending commits to a mailing list?
by Raymond Toy 09 Apr '15

09 Apr '15

Before the change over to gitlab, I had set up a git post-receive hook so that all commits were sent to the cmucl-commit (and cmucl-cvs) mailing lists. (The hook also automatically updated a trac issue, but that seems not necessary anymore with gitlab.) I can't seem to find out how to do that now. There's a page on web hooks, but I can't easily tell what I'm supposed to do with that. I just want each commit to be sent to the cmucl-commit mailing list. -- Ray

2 1

Proposed approach for decommissioning of CVS (migration to Git / Subversion)
by Erik Huelsmann 09 Apr '15

09 Apr '15

Hi, As announced in [1] and with follow-up in [2], common-lisp.net in migrating away from the use of CVS as one of the supported version control systems. The git migration as mentioned in those mails has already taken place. The darcs migration requires more attention due to the sheer number of darcs repositories on the system. For that reason, we will be decommissioning CVS as a next step first. The benefits of decommissioning CVS in terms of having simplified system maintenance are bigger than those from decommissioning Darcs, so when looking at it that way, this is a logical step. The migration for the CVS repositories will be carried out according to the steps below. Note that the default conversion for CVS repositories is going to be to /git/ and imported into GitLab. However, we do understand that in some cases this isn't going to meet the maintainers wishes. We'll notify maintainers 1 week before the conversion is going to take place so a migration to Subversion can be requested. * 1 week before conversion, project members will be notified of expected conversion * Conversion to Git (default) or Subversion (upon request) * Import into GitLab, in case of Git conversion * Decommissioning (removing) CVS repository Due to the need to contact project members *and* the fact that we're talking about 110 repositories, migration will take place in batches. If one has multiple repositories on common-lisp.net using CVS, but notification has come in only for one repo, then the batches for the others aren't being worked on yet. If people want to express their preference to migrate their repositories to Subversion in advance of receiving a migration notification mail, requests can be filed in clo's Trac instance: https://trac.common-lisp.net/clo/newticket I intend to send a summary of the above to the site announcements list incorporating any adjustments to the procedure, based on your feedback. [1] https://mailman.common-lisp.net/pipermail/clo-devel/2015-February/000934.ht… [2] https://mailman.common-lisp.net/pipermail/clo-devel/2015-February/000941.ht… -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

Every love has a story
by Marian Blevins 08 Apr '15

08 Apr '15

http://www.slinckx.be/brake.html Doyo you wish her this night?

1 0

test?
by Drew C 08 Apr '15

08 Apr '15

ok ok ok

1 0

Re: asdf, poiu, etc.
by Anton Vodonosov 08 Apr '15

08 Apr '15

17.04.2013, 00:41, "Faré" <fahree(a)gmail.com>: > [This is a test of the new asdf-devel mailing-list.] It would be good if the mailing list added [asdf-devel] to the subject line. > While I'm at it, may I attract your attention to POIU? It now has a > deterministic mode, so it's reasonably usable in your buildbots. > > Several tweaks since release 2.33, but nothing really new since then. > > If your implementation hasn't upgraded to 2.33 yet, now is a good time.

1 0

Status of anonymous CVS access?
by Marco Antoniotti 08 Apr '15

08 Apr '15

Hi subject says it all. It appears that anonymous CVS reads are disabled. Is that so? -- Marco Antoniotti

1 1

web admin contact info
by Daniel Herring 08 Apr '15

08 Apr '15

Hi all, Sorry for the broadcast. I lost track of the best way to contact the maintainers of common-lisp.net and wiki.alu.org. Regarding cl.net, the http://common-lisp.net/project/clo/ page is outdated, and the "email this list" link to http://lists.common-lisp.net/mailman/listinfo/clo-devel is broken. There is no clear link to contact the site maintainers. Regarding the "ALU" wiki, I would like to forward a message regarding some spam on that site. It would also be good to fix the webmaster address on the "About" page (http://wiki.alu.org/ALU) to something more appropriate. Thanks, Daniel

1 0