Fabio Tranchitella wrote: > Il giorno mer, 28/06/2006 alle 13.35 +0200, Maximilian Mehnert ha > scritto: >> Package: zope-kupu >> Version: 1.3.7-1 >> Severity: grave >> Justification: renders package unusable
> Hi Maximilian, > > I'm not able to reproduce this bug, especially considering that > installing a plone site automatically installs kupu, and even removing > and installing it again doesn't hit what you report. > > Could you please try to build a new zope instance, with a new plone site > and reproduce the problem? And, if you are able to reproduce it, could > you please send me the exported plone site? It seems as if there are incompatibilities when different versions of packages that are built from the zope-cmf1.4 source (and maybe others) do coexist. I cannot point out a special package anymore, but I had some of the zope-cmf* packages that use a common versioning (at the moment 1.4.7-4 and 1.4.8-3, e.g. zope-cmfcore, zope-cmf, etc. ) installed with mixed versions. In the beginning, everything was fine. A few days ago I upgraded some of the zope-cmf packages manually (system default is "stable"). Obviously I missed some of them. This seems to have caused the error mentioned in my bug report. (I found some other reports on the net that seem to support this theory.) After upgrading all zope1.4.x-packages to a common version everything was ok. So IMHO this is not a kupu bug but a problem with the zope-cmf inter-package dependencies. Maybe the upgrading of one zope-cmf package should enforce the upgrading of packages that are build from the same source package. I am not sure what to do here - close this bug, reopen a bug for zope-cmf1.4? I'm leaving this to you. :-) Regards and thanks for all the work! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]