Dear Eugene

ccp4um doesn't work for me at all (update worked fine up until #012).

node066:/software/CCP4-6.3.0/ccp4-6.3.0/bin-45> ccp4um
Traceback (most recent call last):
  File "ccp4um", line 17, in <module>
    shutil.copy2 ( fname,fname1 )
  File "/software/python/python_v2.7.3_64/lib/python2.7/shutil.py", line
128, in copy2
    copyfile(src, dst)
  File "/software/python/python_v2.7.3_64/lib/python2.7/shutil.py", line
82, in copyfile
    with open(src, 'rb') as fsrc:
IOError: [Errno 2] No such file or directory: '/libexec/ccp4um'

Did I do something wrong?  Or is it just that there's nothing to update?

Cheers

-- Ian


On 16 January 2013 15:11, <eugene.krissi...@stfc.ac.uk> wrote:

> Dear Andreas,
>
> Sorry for late response to your post and confusion with the updater. For
> technical reasons (Windows does not like names containing "update" :)), the
> updater was renamed into ccp4um (ccp4 update manager) and is found in
> $CCP4/bin.
>
> I hope this helps,
>
> Eugene
>
>
> Dear CCP4 maintainers,
>
> I've come to appreciate the CCP4 update functionality, which, in our
> multiuser network (RHEL 6.2), I used to invoke by calling $CCP4/bin/update.
>
> Update 012 removed that script with no immediately obvious replacement.
>   Was that on purpose?  Is there a way of updating CCP4 from the command
> line without calling CCP4i?
>
> Thanks
>
>
> Andreas
>
>
> (from update.log:
>
> [Thu Jan 3 2013 11:00:21]
> Ready to make changes
>
>   --- applying update 6.3.0-012
>   --- update header read
>   --- creating restore package, please wait ...
>   --- done
>     ... file '/csb/soft/Linux64/share/ccp4-6.3.0/bin/update' removed
>     ... file '/csb/soft/Linux64/share/ccp4-6.3.0/lib_exec/update' removed
>     ... file '/csb/soft/Linux64/share/ccp4-6.3.0/lib_exec/_update' removed
>     ... directory '/csb/soft/Linux64/share/ccp4-6.3.0/lib_exec' removed
>
>
> some more blah blah)
>
>
> --
>          Andreas Förster, Research Associate
>          Paul Freemont & Xiaodong Zhang Labs
> Department of Biochemistry, Imperial College London
>
> --
> Scanned by iCritical.
>
>

Reply via email to