Bug 165268 - Stable plone conflicts with zope on testBTreeFolder2.py
Summary: Stable plone conflicts with zope on testBTreeFolder2.py
Alias: None
Product: Fedora
Classification: Fedora
Component: plone
Version: 4
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Aurelien Bompard
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2005-08-06 09:46 UTC by Göran Uddeborg
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2005-08-06 10:42:40 UTC

Attachments (Terms of Use)

Description Göran Uddeborg 2005-08-06 09:46:44 UTC
Description of problem:
I tried to install the latest stable Plone from FE with yum.  As I expected, it
wanted to bring in the zope package, zope-2.8.0-2.fc4.i386 to be precise, which
I accepted.

But when it was about to install it complained about a conflict in
/usr/lib/zope/lib/python/Products/BTreeFolder2/tests/testBTreeFolder2.py between
the two packages.

Version-Release number of selected component (if applicable):

How reproducible:
Every time

Steps to Reproduce:
1. Install FC4 (with updates)
2. yum install plone-2.0.5
Actual results:
Conflict when about to install.

Expected results:
Clean installation.

Additional info:
It is one line which differs between the two packages:

--- testBTreeFolder2.py.plone   2005-08-06 11:14:33.000000000 +0200
+++ testBTreeFolder2.py.zope    2005-08-06 11:13:59.000000000 +0200
@@ -19,7 +19,7 @@
 import unittest
 import ZODB
 import Testing
-import Zope
+import Zope2
 from Products.BTreeFolder2.BTreeFolder2 \
      import BTreeFolder2, ExhaustedUniqueIdsError
 from OFS.ObjectManager import BadRequestException

Comment 1 Aurelien Bompard 2005-08-06 10:42:40 UTC
Plone 2.0.5 does not work with Zope 2.8. The latest Plone in Fedora Extras is
2.1c1, and should work with Zope 2.8 :

Comment 2 Göran Uddeborg 2005-08-06 11:01:40 UTC
The Plone web site says 2.0.5 is the latest stable release, so that was why I
took that version.  But I'll try the latest instead then.

Note You need to log in before you can comment on or make changes to this bug.