clo-devel

clo-devel@common-lisp.net

3 participants
610 discussions

Darcs repository migration to GitLab: proposed approach
by Erik Huelsmann 15 May '15

15 May '15

Hi all, As proposed earlier this year [1], common-lisp.net will stop running darcsweb repository browsing and in fact will stop "supporting" Darcs completely. As a result, it makes sense to the common-lisp.net admins to convert projects with Darcs repositories to Git+GitLab, as that's the only remaining DVC option on the system. This is my current thinking with respect to the migration. The migration is inspired on the approach with the CVS migration with the notable exception that I do not envision offering projects to migrate to Subversion (offering only to migrate to Git+GitLab where we supported both Subversion and Git for CVS migration). Offering to migrate to Subversion doesn't seem to make sense as it would mean migrating to a centralized VC from a decentralized one. These are the steps that I forsee in the preparation of the migration: 1) Determine if there are any Darcs source repositories that map to existing target repositories, e.g. because equally named Git repository which was already migrated to GitLab 2) Run a few test conversions on a test-installation *** looking for volunteers to help out validate the conversion-runs *** 3) Post a full listing of all paths which will be affected by the conversion on the common-lisp.net site for review by anyone interested These are the steps that I forsee for the migration itself: 1) One week before migration: notify the affected project/user of the intended migration date [requesting projects/users to remove any repositories that should not be migrated] 2) Migrate the repositories as announced * Repositories in /home will be migrated to individual user accounts * Repositories in /project will be migrated to GitLab groups 3) Send migration confirmation to the respective affected users/projects As some users and projects seem to use Darcs repositories to manage their public_html directories, my current thinking is to convert those repositories, but leave these in-place so projects can replace them with git check-outs at a later date Same as with the CVS migration, it's likely that the migration/conversion of repositories will be executed in batches. [1] https://mailman.common-lisp.net/pipermail/clo-devel/2015-February/000934.ht… Could you provide me with your questions and opinions? -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

CVS repository migration completed!
by Erik Huelsmann 13 May '15

13 May '15

Hi all, This mail is to announce - with great pleasure, I must add - that today the last batch of CVS repositories was converted to Git+GitLab, meaning that CVS is now officially deprecated on common-lisp.net! Again nobody opted to migrate to Subversion+Trac. At this point, we have: 379 Git repositories ("projects") 395 GitLab users 435 Groups ("common-lisp.net projects") Thanks to everybody who helped make the migrations complete smoothly. It's possible that you find repositories for projects which used to have their main ("canonical") project repository on common-lisp.net, but which have their main repository now elsewhere, e.g. on GitHub.com or GitLab.com. If this is the case, we probably converted an old repository. Please report these cases so we can set up mirrorring from the canonical source to the gitlab.common-lisp.net repository. That way we don't serve outdated content. Thanks in advance! Next steps include dismantling the CVS infrastructure on the box as well as moving on to migrating the Darcs repositories to Git+GitLab in the same way as has happened with the CVS repositories. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

2 1

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

← Newer
1
...
19
20
21
22
23
24
25
...
61
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

clo-devel