Hello all, I need some help to find a fix for #411657. The problem is that sarge included the zope2.7 package which requires python2.3, but python2.3 will not be shipped with etch and the current python package conflicts with it. Matthias uploaded zope-common 0.5.31 with the following change: * debian/control: Depend on the unversioned python package. Which means that zope-common now depends on python (>= 2.4) instead of python2.4. After this change, upgrading from sarge to etch means that the sarge version of python2.3 will be uninstalled as well as zope2.7, which I would like to avoid. It will be common for our users to upgrade from sarge to etch with sites running zope2.7, and it would be a good thing to let them run both in order to manually upgrade their instances. See here: $ apt-cache show python | grep Conflicts Conflicts: python2.3 (<< 2.3.5-14), python2.1 (<= 2.1.2), python-xmlbase, python-csv, python-bz2, python-base, python-central (<< 0.5.5) I think that changing the dependency on zope-common to something like: Depends: python (>= 2.4) | python2.4, ... would do the trick, leaving the old python package around without removing python2.3, but I'm not even sure and to say the truth I do not understand why the dependency on python2.4 has been replaced with python (>= 2.4). Any idea? Thanks in advance, -- Fabio Tranchitella http://www.kobold.it Free Software Developer and Consultant http://www.tranchitella.it _____________________________________________________________________ 1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564
Attachment:
signature.asc
Description: Digital signature