LON-CAPA User Help: CVS LON-CAPA User Help : Server System Administration : CVS CVS + Subcategories: + + Answers in this category: + <(*) (missing or broken file) + LON-CAPA User Help : Server System Administration : CVS : CVS info (All examples below assume your cvs checkout is in /somewhere/loncapa)Send an e-mail to to make the change to use :ext recursively. Updating the repository To update a repository to have the files marked STABLE do this: $ cd /somewhere/loncapa $ cvs update -d -r STABLE It is expected that all production machines will be using this. To change a repository to have the latest (and maybe greatest versions) do this: $ cd /somewhere/loncapa $ cvs update -d -A It is expected that all developers to be using this. If you have updated a repository to the Latest (and as it turns out not so great) version, doing: $ cd /somewhere/loncapa $ cvs update -d -r STABLE Will take you back to the STABLE version. A refresher on how to upgrade your machine: export CVS_RSH=ssh export CVSROOT=:ext:USERNAME@source.lon-capa.org:/home/cvs cd loncapa cvs update -d -r STABLE cd loncom/build su make install make configinstall /etc/rc.d/init.d/httpd restart /etc/rc.d/init.d/loncontrol restart Using a public key The downside to using ssh for remote authentication in place of pserver is that you will be prompted to enter your password each time you issue a cvs command. A solution to this is to use $ ssh-keygen -t dsa to generate public and private keys in ~/.ssh/ Send the public key (id_dsa.pub) to helpdesk@lon-capa.org so it can be added to the appropriate authorized_keys file on source.lon-capa.org If you have any problems or questions please contact me. -- Stuart Raeburn helpdesk@lon-capa.org This document is at: http://help.loncapa.org/cgi-bin/fom?file=18 Generated by FAQ-O-Matic 2.719, available at http://faqomatic.sourceforge.net/