Zodbverify 1.0.2 installed as UNKNOWN 0.0.0

I am trying to prepare a Plone 4.3 installation for an in-place migration to Python 3/Plone 5.2 according to

https://docs.plone.org/manage/upgrading/version_specific_migration/upgrade_zodb_to_python3.html

However zodbverify is always installed as UNKNOWN 0.0.0..where is this coming from?

Installing zodbverify 1.0.2
Caused installation of a distribution:
UNKNOWN 0.0.0
with a different project name.
Installing zodbverify 1.0.2
Caused installation of a distribution:
UNKNOWN 0.0.0
with a different version.
Got None.
Getting distribution for 'zodbverify==1.0.2'.
warning: no files found matching '*' under directory 'zodbverify'
warning: no previously-included files matching '*.pyc' found anywhere in distribution
warning: no previously-included files matching '*' found under directory 'news'
warning: no previously-included files found matching 'news'
warning: install_lib: 'build/lib.linux-x86_64-2.7' does not exist -- no Python modules to install

zip_safe flag not set; analyzing archive contents...
Installing zodbverify 1.0.2
Caused installation of a distribution:
UNKNOWN 0.0.0
with a different project name.
Installing zodbverify 1.0.2
Caused installation of a distribution:
UNKNOWN 0.0.0
with a different version.
Path /home/ajung/.buildout/eggs/UNKNOWN-0.0.0-py2.7.egg unexpectedly already exists.
Maybe a buildout running in parallel has added it. We will accept it.
If this contains a wrong package, please remove it yourself.
Got None.
Version and requirements information containing zodbverify:
  [versions] constraint on zodbverify: 1.0.2
  Base installation request: 'Zope2', 'Plone', 'python-ldap', 'mr.developer', 'zchl.policy', 'zchl.basetheme', 'Products.ATVocabularyManager', 'plone.api', 'plone.app.workflowmanager', 'Pillow', 'plone4.csrffixes==1.1', 'z3c.jbot', 'five.pt', 'Products.PloneHotfix20161129', 'Products.PloneHotfix20170117', 'Products.PloneHotfix20171128', 'sauna.reload', 'zodbupdate', 'zodbverify', 'plone.recipe.zope2instance'
While:
  Installing instance.
Error: There is a version conflict.
We already have: UNKNOWN 0.0.0

I saw this with "very" old setuptools.

Wouldn't say "very old" but just old. :upside_down_face:

We had this problem for example using setuptools 26.1.1 (a package from 2016) - which is pinned in Plone cfgs itself. https://dist.plone.org/release/4.3-latest/versions.cfg

We've discussed about updating these packages in https://github.com/plone/Products.CMFPlone/issues/1502

1 Like