[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#599813: [PATCH 3/3] Add information about upgrading evolution

From: Adam D. Barratt <adam@adam-barratt.org.uk>

Patch by Adam D. Barratt.

Bug #599813
This introduces a "package specific issues" section, currently
only mentioning evolution

Signed-off-by: Adam D. Barratt <adam@adam-barratt.org.uk>
Acked-by: Yves-Alexis Perez <corsac@debian.org>
Signed-off-by: Julien Cristau <jcristau@debian.org>
 en/upgrading.dbk |   32 ++++++++++++++++++++++++++++++++
 1 files changed, 32 insertions(+), 0 deletions(-)

diff --git a/en/upgrading.dbk b/en/upgrading.dbk
index d2cb8aa..1cebc09 100644
--- a/en/upgrading.dbk
+++ b/en/upgrading.dbk
@@ -1190,6 +1190,38 @@ Arrow</keycap></keycombo> to switch between the different text-mode terminals.
+<section id="package-specific-issues">
+<title>Special care for specific packages</title>
+In most cases, packages should upgrade smoothly between &oldreleasename;
+and &releasename;.  There are a small number of cases where some intervention
+may be required, either before or during the upgrade; these are detailed
+below on a per-package basis.
+<section id="issues-evolution">
+Evolution (the GNOME Desktop mail client) has been updated from version
+<literal>2.22</literal> to <literal>2.30</literal>. This changes the
+storage format used by the package for local data and there is a
+possibility of data loss if the upgrade is performed whilst <systemitem
+role="package">evolution</systemitem> is running. Exiting the
+application itself may not be sufficient, as various related components
+will continue to run in the background. To avoid any potential issues,
+it is recommended that you completely exit your desktop environment
+before beginning the upgrade to &releasename;.    
+As part of the upgrade process, <systemitem
+role="package">evolution</systemitem> will check whether any related
+processes are running and will recommend that they be closed. A
+secondary check for processes will then be performed; if necessary, a
+choice will be offered between allowing the remaining processes to be
+killed or aborting the upgrade in order to resolve the situation by
 <!-- End of 'trouble' section -->

Reply to: