#211 — adding as buildout egg does not get latest stable version of Poi
by
Matt Barkau
—
last modified
Jul 05, 2010 12:34 PM
| State | Resolved |
|---|---|
| Version: | 2.0.3 |
| Area | Functionality |
| Issue type | Bug |
| Severity | Medium |
| Submitted by | Matt Barkau |
| Submitted on | Jun 21, 2010 |
| Responsible | Maurits van Rees |
| Target release: | 2.0.4 |
The instructions at
http://plone.org/products/extreme-management-tool
say
"Just add Products.eXtremeManagement in the main eggs section of your buildout.cfg."
but this defaults to an alpha version of Poi:
"We already have: Plone 3.3.5
but Products.Poi 2.0a1 requires 'Plone>=4.0a1'."
http://plone.org/products/extreme-management-tool
say
"Just add Products.eXtremeManagement in the main eggs section of your buildout.cfg."
but this defaults to an alpha version of Poi:
"We already have: Plone 3.3.5
but Products.Poi 2.0a1 requires 'Plone>=4.0a1'."
Added by
Matt Barkau
on
Jun 21, 2010 07:32 PM
(I worked around this by pinning, but have posted this so the issue can be resolved for others. Thanks!)
Added by
Maurits van Rees
on
Jul 05, 2010 12:34 PM
Problems like this will start occurring with more products, and it is not really a problem in xm itself in my opinion. But since we know that Poi 2.0a1 or higher depends on Plone 4 and xm is not ready for Plone 4, it makes sense to restrict the version of Poi in our setup.py. I have released Products.eXtremeManagement 2.0.4 which contains only this fix.
Issue state:
Unconfirmed
→
Resolved
Responsible manager:
(UNASSIGNED)
→
maurits
Target release:
None
→
2.0.4
Thanks for the report.
No responses can be added.
If you can, please log in before submitting a reaction.
