I have been given a legacy Plone 220.127.116.11 (4206) site to migrate from a FreeBSD 9 server that I do not have full access to. I plan to deploy the site on a new Debian VM and migrate to a newer version. I have a full backup of the site directory (data.fs etc.). However, I am unable to install a new instance of Plone 4.2. I have tried to install 4.2 on Debain 8 & 9 and also macOS Catalina and get similar errors on all platforms (see below from Debian 9).
I have successfully installed Plone 4.3 on a new VM, but when the old site filestorage is copied over @@plone-upgrade shows errors resulting from the difference between the 4.2 data and the 4.3 site.
The live 4.2 site @@plone-upgrade page says that 'Your site is up to date', so there does not seem to be a way to upgrade to 4.3 on the live server. Do I need to install an instance of 4.2 locally first in order to start the migration, if so how? I would be grateful if you could advise a viable migration path. Thanks.
Installing Python-2.7.3. This takes a while... Installing distribute... /usr/local/Plone/Python-2.7/bin/easy_install missing. Aborting. Installation has failed. See the detailed installation log at /home/john/Plone-4.2-UnifiedInstaller/install.log to determine the cause. $ tail /home/john/Plone-4.2-UnifiedInstaller/install.log self.cmdclass[command] = cmdclass = ep.load() File "/home/john/Plone-4.2-UnifiedInstaller/packages/distribute-0.6.24/pkg_resources.py", line 1989, in load entry = __import__(self.module_name, globals(),globals(), ['__name__']) File "/home/john/Plone-4.2-UnifiedInstaller/packages/distribute-0.6.24/setuptools/command/easy_install.py", line 25, in <module> from setuptools.package_index import PackageIndex File "/home/john/Plone-4.2-UnifiedInstaller/packages/distribute-0.6.24/setuptools/package_index.py", line 10, in <module> from md5 import md5 File "/usr/local/Plone/Python-2.7/lib/python2.7/md5.py", line 10, in <module> from hashlib import md5 ImportError: cannot import name md5