RE: CVS access via SSH

-----Original Message----- From: xemacs-beta-admin(a)xemacs.org [mailto:xemacs-beta-admin＠xemacs.org]On Behalf Of Stephen J. Turnbull Sent: Monday, October 22, 2001 10:04 AM To: xemacs-review(a)xemacs.org; xemacs-beta(a)xemacs.org; ben(a)xemacs.org Subject: CVS access via SSH I have the CVS repository online now. Due to local firewall restrictions, access has to be via SSH. If you had commit access on the old cvs.xemacs.org, I should have a valid public key for you already. Write accesses should be the same as on the old host. Host is tanko.sk.tsukuba.ac.jp [130.158.99.155]. Root is /usr/CVSroot. Access cvs via the ext method in the usual way: CVS_RSH=`which ssh` cvs -d :ext:xemacs＠tanko.sk.tsukuba.ac.jp:/usr/CVSroot This is SSH 1. It's not a top-of-the-line box, but should serve for the moment. This uses the SSH feature of restricting access to a particular application, namely "cvs server" for /usr/CVSroot. Lightly tested, it seems to work. I have tagged the current state of the trunk of the core as LAST_DAYS_OF_CAMELOT. Besides having the tarballs from the old host, we should also be able to replay to current state with that tag. Anybody with a shared private branch, I suggest doing the same. I haven't tagged packages yet, will do that tomorrow my time. We should be extremely careful with package commits anyway, since Steve Youngs is out of action. Plans: I considered changing cvs.xemacs.org to point to this box, but it doesn't seem worthwhile given that I expect to have the repository moved shortly, and given DNS propagation lags. The next steps are to set up an rsync (or similar) mirror, at SunSITE.dk or Tux.ORG, preferably both, open anonymous pserver access, then move the primary to one of those. Thank you for your patience. Let me know of any problems; I'll try to get to them as quickly as possible. -- Institute of Policy and Planning Sciences