Bug 160971
Summary: | plone alpha 2.1 put into extras instead of extras/testing | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Keith Kube <keith-kube> |
Component: | plone | Assignee: | Aurelien Bompard <gauret> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | noarch | ||
OS: | Linux | ||
URL: | www.kube.homelinux.net | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-07-01 12:39:04 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Keith Kube
2005-06-19 11:27:33 UTC
Correction - all zope sites are crashing, the one site I thought wasn't was on another machine. The problem is : Plone 2.0.x does not work with Zope 2.8, and Zope 2.8 has been published into FC-3 (it should have waited for FC4, my mistake here). Only Plone 2.1 works with Zope 2.8 In addition, Plone 2.4 does not work with python 2.4 (shipped in FC4), so I have to update it to 2.1 anyway. (In reply to comment #2) > The problem is : Plone 2.0.x does not work with Zope 2.8, and Zope 2.8 has been > published into FC-3 (it should have waited for FC4, my mistake here). Only Plone > 2.1 works with Zope 2.8 > In addition, Plone 2.4 does not work with python 2.4 (shipped in FC4), so I have > to update it to 2.1 anyway. Thanks for getting back to this so quick. This still leaves me with all my plone sites being down (see www.kube.homelinux.net for a detailed traceback). Any suggestions on how to move forward. Do I try to rollback the plone instance, or try to solve the problems? I'd suggest to rollback both plone and zope for the moment. Sorry about that. |