clo-devel May 2015

clo-devel@common-lisp.net

3 participants
4 discussions

/custom/bin/add-project.sh not working smooth
by Mark Evenson 27 May '15

27 May '15

/custom/bin/add-project.sh apparently needs some debugging to keep it in sync with system changes, as running it produced the following errors: common-lisp.net# sudo /custom/bin/add-project.sh cl-player clin Creating project cl-player, using handle cl-player in 5 seconds. Adding group `cl-player' (GID 1008) ... Done. Adding user `clin' to group `cl-player' ... Adding user clin to group cl-player Done. ln: failed to create symbolic link `/var/lib/svnroots/cl-player': No such file or directory Hit enter to notify cl-player-devel owner... Subscribed: clin(a)common-lisp.net Subscribed: sxhash(a)gmail.com Add members to a list from the command line. Usage: add_members [options] listname Options: […] You must supply at least one of -r and -d options. At most one of the files can be `-'. No such list: cl-player-announce Configure a list from a text file description. Usage: config_list [options] listname Options: --inputfile filename […] The options -o and -i are mutually exclusive. No such list "cl-player-cvs" Creating a default page for cl-player in /project/cl-player/public_html -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."

1 0

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

clo-devel May 2015