Your message dated Tue, 23 Feb 2010 21:49:07 +0000 (WET)
with message-id <[email protected]>
and subject line Package zope-cmfplone has been removed from Debian
has caused the Debian Bug report #391758,
regarding plone-cms: No upgrade path for 2.1 to 2.5
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
391758: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=391758
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: plone-cms
Version: cmfplone
Severity: grave
Justification: causes non-serious data loss
After upgrading to plone-2.5 all my 2.1 instaces are gone.
The upgrade causes zope 2.9 to be installed, and updates plone packages in
zope2.8 instances. This leaves a non-functional
system.
The 2.8 instances are now broken, since they have ben upgraded to
packages that need 2.9 or higher, and no attempt is made to migrate plone
sites
to the 2.9 instance.
Ideally, the update of plone/zope should give the option of duplicating
or migrating instances to zope 2.9, but there should at least be a warning that
this
upgrade will break your existing plone sites in a major way.
Keep up the good work,
Gerrit jan
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
--- End Message ---
--- Begin Message ---
Version: 2.5.2-3+rm
You filed the bug http://bugs.debian.org/391758 in Debian BTS
against the package zope-cmfplone. I'm closing it at *unstable*, but it will
remain open for older distributions.
For more information about this package's removal, read
http://bugs.debian.org/455919. That bug might give the reasons why
this package was removed and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
--
Marco Rodrigues
--- End Message ---
