[LON-CAPA-dev] Re: LON-CAPA-dev digest, Vol 1 #96 - 13 msgs
Fri, 02 Jul 2004 04:55:23 -0400
-----BEGIN PGP SIGNED MESSAGE-----
~ My apologies to all. When I was checking them in I wasn't thinking
about the dependency on the ssl support for perl. I was thinking that
all you really needed were the updated config files (loncapa_apache)
that allow the software to fail back to insecure connection.
Michigan State University
East Lansing, MI 48824-1321
The ancestor of every action is a thought. - Ralph Waldo Emerson
| From: "Matthew Brian Hall" <email@example.com>
| Last week I sent out an email asking people to not update their cvs
| repositories until they heard from me. This was due to some code being
| checked in which made all the development machines unusable until the
| system was updated and an encryption key was obtained from Ron Fox.
| email describing the needed steps apparently did not make it out to the
| developer mailing list. I've attempted to put together the necessary
| packages required to run the new code but I have been unable to test them
| for completeness. Since Ron is unavailable currently we need to work
| the situation. It is quite frustrating to be telling everyone to update
| their repository every day and then have to send an email out asking them
| not to. But this is a chance for a brief review of CVS.
| The fix is to check out specific versions of some of the files:
| cd loncapa/loncom
| cvs update -r 1.30 LondConnection.pm
| cvs update -r 1.193 lond
| cvs update -r 1.4 lonlocal.pm
| cvs update -r 1.7 lonssl.pm
| cvs update -r 1.47 loncnew
| And then
| cd ..
| cvs update -d
| When you issue a "cvs update" in the future, the versions of lond and the
| other modules will be preserved - in the cvs vernacular, they are
| Changes you see float by the cvs mailing list which apply to these files
| will not be made to your system. Please avoid modifying these files
| time being.
| I imagine that by this time next week we will tell you to issue a "cvs
| update -A". The "-A' parameter causes cvs to reset all "sticky" tags,
| causing the system to update every file.
| Matthew Hall firstname.lastname@example.org
| LON-CAPA developer
| Michigan State University
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----