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

Progress migrating projects away from CVS and next steps
by Erik Huelsmann 07 May '15

07 May '15

Hi all, Next week, the last batch of CVS repositories will be migrated. Based on feedback on earlier batches, they will most likely be migrated to Git (so far, there were no projects opting for Subversion instead of Git). After that step has been completed, work will move on to migrate Darcs repositories to Git so we can phase out Darcsweb. Preparations for this migration can't be started while the CVS migration is on-going due to time constraints on my part. This means that it'll take a while before any visible progress will be made. As for the procedure to be used, I've yet to decide whether to go with the CVS approach where we did batches or to go with the Git approach where we did everything at once. Given that there are Darcs repositories litterally all over the place, I'm currently leaning to a phased migration. There are somewhere between 280 and 600 darcs repositories to be migrated. By looking at the paths in the server, it looks like there are over 600 darcs repositories, however, it seems that some of them are 'public_html' clones serving the purpose of being the document root. With the knowledge I currently have about the darcs repositories, current users of the system can really, really help by cleaning out any Darcs repositories they have laying around which they don't need any more and which need not be migrated to Git. Projects could help by indicating which repositories they consider the canonical source and which ones are simply used as workspaces to serve anything from. Anybody who wants to help create a list of Darcs repositories which should and which ones shouldn't be migrated: your efforts and inputs are greatly welcomed! Kindest regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

Where in our site to hook up the pages about common-lisp.net itself?
by Erik Huelsmann 19 Apr '15

19 Apr '15

Hi, We have a number of pages about common-lisp.net itself: https://common-lisp.net/gitlab-migration-status https://common-lisp.net/gitlab-migration-repository-mapping/ Further more, I think that a number of mails (with their reactions) to this list should be converted to pages on the site: https://mailman.common-lisp.net/pipermail/clo-devel/2015-February/000934.ht… (policy/strategy) https://mailman.common-lisp.net/pipermail/clo-devel/2015-February/000941.ht… (policy/strategy) https://mailman.common-lisp.net/pipermail/clo-devel/2015-April/001036.html (faq) Does anybody have any ideas where to put these in the current site structure? I think it's a good idea that they're easy to find. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

What you could help me with
by Erik Huelsmann 19 Apr '15

19 Apr '15

Hi all, I have a not-so-high priority item which I do deem important enough to ask you to do it instead of doing it myself in a few months (when I have time/finished the migrations). So, the task looks not too complex (to me -- let me know if it isn't :-) ): We currently have a page on common-lisp.net which makes very little sense now that we're actively supporting Git and Subversion and phasing out support for all other VC systems. Could someone pick up the task of rewriting that page, possibly after discussing here if they're unsure what the "direction statement" ( https://mailman.common-lisp.net/pipermail/clo-devel/2015-February/000934.ht…) means for the items described on that page (or whether items are missing from that page due to the direction statement). Thanks for any and all offers for help. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

Migration of CVS repositories to Git
by Erik Huelsmann 19 Apr '15

19 Apr '15

Hi all, Just wanted to announce here that the first batch of CVS repositories (10 projects) has been migrated from CVS to Git+GitLab. Projects were offered to be migrated to Subversion as an alternative migration, but none elected to take that option. Rewrite rules were installed to forward traffic from ViewCVS/ViewVC to the new GitLab repository browsing. Read more here: https://common-lisp.net/news/#2015_04_19 (includes list of projects now migrated). -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

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