Please report all errors/typos. etc
to Matt Choptuik at [email protected]
Last updated May 24, 2012
The
situation
- As of May 24, 2012, vnfe4.physics.ubc.ca is down with serious
hardware issues, and, in fact, may be offline permanently. The CVS repository that previously was
hosted on that machine has been migrated to bh1.physics.ubc.ca
What
you need to do
- In principle, there are only two things that require your
attention: contact Matt should the procedures described below not work
for you
- Change the setting of the CVSROOT
environment variable
- For each directory in the repository that you have
previously/currently checked out, use one of the following two options:
- Check out a new/fresh version of the directory from the
relocated repository, once the CVSROOT
environment variable has been set as described below
- Modify the contents of all CVS/Root files to reflect the new
location of the repository (see below). If the directory has outstanding changes
that need to be committed as of May 24, 2012, you should definitely use
this option.
- IMPORTANT!! No
matter which of the above two options you choose, you should ensure
that you BACK UP your most
recent working version of any directory previously stored in
[email protected] and RETAIN
THAT BACKUP COPY until you are sure that things are working
properly with the new repository.
1) Change the setting of CVSROOT
bash
tcsh
As usual, these commands are best placed in your ~/.bashrc or ~/.tcshrc (~/.cshrc)
2)
Modify the contents of all CVS/Root files in a checked out directory
Assuming that the working directory is one that was
previously checked out from [email protected], execute the
following command
find . -name Root -exec perl -p -i -e 's/vnfe4/bh1/g' {} \;
This will modify all of the Root files rooted in the working
directory so that subsequent cvs
update, commit etc.
commands will use the new version of the repository.
Note that if you choose to check out a fresh version of the directory
after having set the CVSROOT
variable to its new value (i.e. option 2), you do NOT have to execute this command
Again, if your directory contains
uncommitted changes as of May 24, you should use this option.
3) Access to the repository
All users who previously had
password-less access to [email protected] should now have the
same access to [email protected]. Concact Matt if this not
the case.
Let Matt know if you have
questions about this, or should you encounter problems using
[email protected], and
particularly if you find errors in the above
discussion!