Table of Contents
Update packages
The tarballs linked to this page are for use with CCP4 updater (ccp4um) in off-line mode (e.g. without network connection). You do not need them if your CCP4 update works normally through the internet.
Follow instructions below if you do intend to use the CCP4 updater in off-line mode.
Linux, Mac OS X
1. Download and uncompress the appropriate update directory:
2. Start Update Manager from the command line as follows:
ccp4um -uri full-path-to-update-directoryWindows
1. Download and uncompress the appropriate update directory:
2. Double-click on CCP4-Console icon on the Desktop
3. Start Update Manager from CCP4-Console as in Example below.
Example
The full path to downloaded and unzipped update directory:
C:\Users\Andrey\Downloads\ccp4-7.0-updates-win64The command to run in CCP4-Console (note that URI contains slashes, not backslashes):
ccp4um -uri file:///C:/Users/Andrey/Downloads/ccp4-7.0-updates-win64An issue with double occurrence of ccp4-7.0-updates-win64 in the folder path.
There are several ways of performing step (1). One of them is to download the zip-archive, right mouse click on the archive icon and select Extract All… from the menu. The Extract window opens with the default destination path ending with ccp4-7.0-updates-win64. With such a default, the path to update folder will have two occurrences of ccp4-7.0-updates-win64 in it, for example:
C:\Users\Andrey\Downloads\ccp4-7.0-updates-win64\ccp4-7.0-updates-win64Correct URI in (3) accordingly in such a case or move the internal folder to a more convenient location.
Known issues with Update Manager
| No | 6 |
| Fixed | 7.0.070 |
| Introduced | 7.0.069 |
| Symptoms | CCP4i2 does not start |
| Affected interfaces | CCP4i2 |
| Affected platforms | Some versions of Mac OS X and Linux |
| Additional conditions | – |
| What to do | 1. Open Terminal window 2A. If ccp4-7.0 was installed “for all users”, type in
2B. Otherwise, type in
3. This command starts Update Manager. Use it to apply update 70 or newer. * Update Manager not starting at step (2A/B) means CCP4 environment variables are not set in the Terminal shell. In this case, specify full path to ccp4um:
or
for cases (2A) and (2B), respectively. ** Alternatively, start Update Manager from CCP4i. |
| No | 5 |
| Fixed | – |
| Introduced | 7.0.053 (16.03.18) |
| Symptoms | Interface shows message Checking for new updates and does not activate the Manage Updates button |
| Affected interfaces | CCP4i |
| Affected platforms | Mac OS X (and others?) |
| Additional conditions | – |
| What to do | Start Update Manager from CCP4i2 or from the command line (as in No 4) |
| No | 4 |
| Fixed | 7.0.053 (19.03.18) |
| Introduced | 7.0.053 (16.03.18) |
| Symptoms | Update Manager window does not open |
| Affected interfaces | CCP4i2, CCP4i |
| Affected platforms | Linux, Mac OS X |
| Additional conditions | CCP4 is installed “for all users” (Update Manager asks for admin password) Update 53 installed before Sunday 18th of March 22:30 GMT |
| What to do | 1. Open Terminal window 2. Type in
3. In the Update Manager window: “Next”; uncheck the check box next to 7.0.053; “Apply” 4. Repeat (2) and apply new updates (including the repaired version of update 53) * Update Manager not starting at step (2) means CCP4 environment variables are not set in the Terminal shell. In this case, specify full path to ccp4um:
|
| No | 3 |
| Fixed | 7.0.053 (16.03.18) |
| Introduced | 7.0.052 (28.02.18) |
| Symptoms | Update Manager window does not open |
| Affected interfaces | CCP4i2 |
| Affected platforms | Windows |
| Additional conditions | – |
| What to do | 1. Double-click on CCP4-Console icon on the Desktop 2. Type in
3. Apply new updates |
| No | 2.2 |
| Fixed | – |
| Introduced | Windows feature |
| Symptoms | Error dialog: Update encountered the following error: Cannot open file: … and cannot continue normally |
| Affected interfaces | CCP4i2, CCP4i, command line |
| Affected platforms | Windows |
| Additional conditions | There are running CCP4 jobs |
| What to do | 1. Wait for all jobs to finish 2. Start Update Manager 3. In the Update Manager window: “Next”; uncheck the check box next to the last applied update; “Apply”; “Finish” 4. Start Update Manager again and apply new updates * In some cases files remain locked even when job has finished and you may need to restart your computer. See also No 2.1 below |
| No | 2.1 |
| Fixed | 7.0.053 (16.03.18) |
| Introduced | 7.0.000 (07.01.16) |
| Symptoms | Error dialog: Update encountered the following error: Cannot open file: … and cannot continue normally |
| Affected interfaces | CCP4i2 |
| Affected platforms | Windows |
| Additional conditions | No CCP4 programs are currently running |
| What to do | 1. Quit CCP4i2 2. Start Update Manager from CCP4i or from CCP4-Console (as in No 3) 3. In the Update Manager window: “Next”; uncheck the check box next to the last applied update; “Apply”; “Finish” 4. Start Update Manager again and apply new updates See also No 2.2 above |
| No | 1.2 |
| Fixed | 7.0.053 (16.03.18) |
| Introduced | 7.0.049 (15.01.18) |
| Symptoms | Postinstall scripts fail with the following error messageQObject::connect: Cannot connect MonitoredProcess::lines(const QString) to (null)::append(const QString) |
| Affected interfaces | command line |
| Affected platforms | Linux, Mac OS X, Windows |
| Additional conditions | – |
| What to do | Apply new updates |
| No | 1.1 |
| Fixed | 7.0.049 (15.01.18) |
| Introduced | 7.0.000 (07.01.16) |
| Symptoms | Postinstall scripts occasionally fail with timeout message |
| Affected interfaces | CCP4i2, CCP4i |
| Affected platforms | Linux, Mac OS X, Windows |
| Additional conditions | – |
| What to do | Restart Update Manager and continue applying new updates. The best option for Windows is to apply new updates from CCP4-Console (as in No 3 above) or to reinstall CCP4 |
Update summaries
There are no updates yet.
Reporting bugs
All bugs should be reported to ccp4@ccp4.ac.uk.