Hello,
This is just a warning that we are putting out a new release of v2 Format
Converter and Analysis pretty soon, likely tomorrow the way things are
going.
But for Analysis users there are a few housekeeping notes to get through
first.
So the first note is that normally you can do an update from inside
Analysis and it will notice that you have an out-of-date version and try
to download the latest version. Unfortunately testing stuff at the
weekend I discovered that a bug was introduced into the update code in
December which means that in 2.0.6 Analysis this update feature is broken
(it will just not get around to asking about downloading the new version).
So I've just now put a fix on the update server for 2.0.6 users.
For people who do *not* get this fix before the next release is out (and
once the next release is out you won't be able to get it), here is how to
fix it in your 2.0.6 code. In the file
ccpnmr2.0/python/ccpnmr/update/UpdatePopup.py on line 77 you have:
self.update()
Change that to:
self.updateFiles()
And hopefully you can then upgrade from inside Analysis (well, obviously
do not start Analysis up to do the upgrade until after that line is
fixed).
Which brings me onto the next point of bureaucracy. Many people have
pre-compiled releases of 2.0.6 Analysis. Unfortunately in 2.0.6, the
update mechanism for you would still download the source code version of
2.0.7 and try and compile that (with the same Python/Tcl/Tk as was used
for 2.0.6, at least). Now this compilation will almost certainly fail for
some people for various reasons (e.g. some system header files might be
missing, we've already hit that one in another context).
In 2.0.7 I've changed things so that from now on pre-compiled releases
will try and download pre-compiled releases. But for now, anybody who has
a 2.0.6 pre-compiled release I would recommend that you get the 2.0.7
pre-compiled release yourself from:
http://www.ccpn.ac.uk/ccpn/software/downloads-v2/
(when it is ready, it's not yet!), instead of using the Analysis update
mechanism. Just unpack and run "python configRelease.py" again (as last
time). But first move the 2.0.6 release because both 2.0.6 and 2.0.7 will
unpack into the same place (well, if you unpack in the same directory).
Wayne
|