[/offlineimap/head: changeset 509
jgoerzen**20030718184913
 Added a section on upgrading to the documentation
] {
addfile ./offlineimap/head/UPGRADING
hunk ./offlineimap/head/UPGRADING 1
+NOTE:
+
+The configuration file has changed in incompatile ways with 4.0.  If you are
+upgrading from a previous version, please read the UPGRADING section in the 
+manual before invoking OfflineIMAP.
+
+-- John
+
+
hunk ./offlineimap/head/debian/changelog 1
+offlineimap (4.0.0) unstable; urgency=low
+
+  * Poof, this is 4.0.
+  * Added UPGRADING file and UPGRADING instructions.
+
+ -- John Goerzen <jgoerzen@complete.org>  Fri, 18 Jul 2003 17:31:14 -0500
+
hunk ./offlineimap/head/offlineimap.1 6
-.TH "OFFLINEIMAP" "1" "02 June 2003" "John Goerzen" "OfflineIMAP Manual"
+.TH "OFFLINEIMAP" "1" "18 July 2003" "John Goerzen" "OfflineIMAP Manual"
hunk ./offlineimap/head/offlineimap.1 80
-readers don't.
+readers don't.  However, this feature is not as time-tested
+as traditional syncing, so my advice is to stick with normal
+methods of operation for the time being.
hunk ./offlineimap/head/offlineimap.1 649
+\fBI've upgraded and now OfflineIMAP crashes when I start it up!  Why?\fR
+You need to upgrade your configuration
+file.  See [XRef to UPGRADING.4.0] at the end of this
+manual.
+.TP
hunk ./offlineimap/head/offlineimap.1 756
-specified in RFC2060
+specified in RFC2060 and RFC3501
hunk ./offlineimap/head/offlineimap.1 842
+.SH "UPGRADING TO 4.0"
+.PP
+If you are upgrading from a version of \fBOfflineIMAP\fR prior to
+3.99.12, you will find that you will get errors when
+\fBOfflineIMAP\fR starts up (relating to ConfigParser or
+AccountHashGenerator) and the
+configuration file.  This is because the config file format
+had to change to accomodate new features in 4.0.  Fortunately,
+it's not difficult to adjust it to suit.
+.PP
+First thing you need to do is stop any running \fBOfflineIMAP\fR
+instance, making sure first that it's synced all your mail.
+Then, modify your
+\fI~/.offlineimaprc\fR file.  You'll need to
+split up each account section (make sure that it now starts
+with "Account ") into two Repository sections (one for the
+local side and another for the remote side.)  See the files
+\fIofflineimap.conf.minimal\fR and
+\fIofflineimap.conf\fR in the distribution if
+you need more assistance.
+.PP
+\fBOfflineIMAP\fR's status directory area has also changed.
+Therefore, you should delete everything in ~/.offlineimap as
+well as your local mail folders.
+.PP
+When you start up \fBOfflineIMAP\fR 4.0, it will re-download all
+your mail from the server and then you can continue using it
+like normal.
hunk ./offlineimap/head/offlineimap.sgml 13
-      <date> $Date: 2003-06-02 09:06:18 -0500 (Mon, 02 Jun 2003) $ </date>
+      <date> $Date: 2003-07-18 13:49:13 -0500 (Fri, 18 Jul 2003) $ </date>
hunk ./offlineimap/head/offlineimap.sgml 117
-	  readers don't.
+	  readers don't.  However, this feature is not as time-tested
+	  as traditional syncing, so my advice is to stick with normal
+	  methods of operation for the time being.
hunk ./offlineimap/head/offlineimap.sgml 823
+	<varlistentry><term>I've upgraded and now &OfflineIMAP;
+	crashes when I start it up!  Why?</term>
+	  <listitem><para>You need to upgrade your configuration
+	file.  See <xref linkend="upgrading.4.0"> at the end of this
+	      manual.
+	    </para>
+	  </listitem>
+	</varlistentry>
+
hunk ./offlineimap/head/offlineimap.sgml 951
-	  specified in RFC2060</para></listitem>
+	  specified in RFC2060 and RFC3501</para></listitem>
hunk ./offlineimap/head/offlineimap.sgml 1059
+
+    <refsect1 id="upgrading.4.0">
+      <title>Upgrading to 4.0</title>
+      <para>
+	If you are upgrading from a version of &OfflineIMAP; prior to
+	3.99.12, you will find that you will get errors when
+	&OfflineIMAP; starts up (relating to ConfigParser or
+	AccountHashGenerator) and the
+	configuration file.  This is because the config file format
+	had to change to accomodate new features in 4.0.  Fortunately,
+	it's not difficult to adjust it to suit.
+      </para>
+      <para>
+	First thing you need to do is stop any running &OfflineIMAP;
+	instance, making sure first that it's synced all your mail.
+	Then, modify your
+	<filename>~/.offlineimaprc</filename> file.  You'll need to
+	split up each account section (make sure that it now starts
+	with "Account ") into two Repository sections (one for the
+	local side and another for the remote side.)  See the files
+	<filename>offlineimap.conf.minimal</filename> and
+	<filename>offlineimap.conf</filename> in the distribution if
+	you need more assistance.
+      </para>
+      <para>
+	&OfflineIMAP;'s status directory area has also changed.
+	Therefore, you should delete everything in ~/.offlineimap as
+	well as your local mail folders.
+      </para>
+      <para>
+	When you start up &OfflineIMAP; 4.0, it will re-download all
+	your mail from the server and then you can continue using it
+	like normal.
+      </para>
+    </refsect1>
+	
}