five.intid 0.3.0 (the version currently pinned) breaks collective.dancing on Plone 4.0b3

[Rodrigo Bernardo Pimentel]

If I install Plone 4.0b3 (on Debian Linux, with Unified Installer), and then add collective.dancing to the buildout as described on the installation instructions (except that I have to comment out zope.component versioning, as the pinned version 3.5.1 conflicts with the zope.app.publisher requirement of'zope.component>=3.7.0'. ...), buildout works, but when I start an instance and try to access it, the client gives the following error:

(...)
    raise schema.ValidationError(v)
ZopeXMLConfigurationError: File "/opt/plone-vision-test/plone-vision/
zeocluster/parts/client1/etc/site.zcml", line 15.2-15.55
    ZopeXMLConfigurationError: File "/opt/plone-vision-test/plone-
vision/zeocluster/parts/client1/etc/package-includes/001-
collective.dancing-configure.zcml", line 1.0-1.62
    ZopeXMLConfigurationError: File "/opt/plone-vision-test/plone-
vision/buildout-cache/eggs/collective.dancing-0.8.16_1-py2.6.egg/
collective/dancing/configure.zcml", line 13.2-13.34
    ZopeXMLConfigurationError: File "/opt/plone-vision-test/plone-
vision/buildout-cache/eggs/five.intid-0.3.0-py2.6.egg/five/intid/
configure.zcml", line 8.2-8.51
    ZopeXMLConfigurationError: File "/opt/plone-vision-test/plone-
vision/buildout-cache/eggs/five.intid-0.3.0-py2.6.egg/five/intid/
base.zcml", line 6.2-6.45
    ConfigurationError: ('Invalid value for', 'package', 'ImportError:
Module zope.app has no global keyreference')

Apparently, zope.app.keyreference has been renamed to
zope.keyreference, and the pinned version 0.3.0 of five.initid doesn't know it
yet.

Is version 0.3.0 of intid absolutely required for some reason? Currently, it seems to prevent collective.dancing from working with Plone 4.0b3.

[Maurits van Rees (maurits-vanrees)]

Looks like updating to five.intid 0.4.4 would be fine for Plone 3. But that version still gives this problem with Plone 4. Using five.intid 0.5 works on Plone 4 but not Plone 3. So I am not going to add that in our known-good-set of versions.

I tried with a Plone 4 beta locally and with that five.intid 0.5. The effect is that this particular error goes away but another pops up. Fixing an import in collective.singing (committed on trunk) helped enough so that zope could at least start up. But there are lots and lots of test errors, so more effort is needed here, which I am not currently going to do.