mirror of https://git.code.sf.net/p/isync/isync
Theodore Ts'o
21 years ago
14 changed files with 346 additions and 24 deletions
@ -0,0 +1,16 @@ |
|||||||
|
isync (0.8-1) unstable; urgency=low |
||||||
|
|
||||||
|
IMPORTANT upgrade note: |
||||||
|
|
||||||
|
This version includes a change to the way the UID for each message is |
||||||
|
stored in the local mailbox. You need to remove all the messages in your |
||||||
|
local folder if you were previously using another version of isync or else |
||||||
|
you will end up with duplicate messages on your IMAP server. |
||||||
|
|
||||||
|
A suggested upgrade procedure is to use isync version 0.7 to synchronize |
||||||
|
any local changes in isync-managed mailboxes with your IMAP server, and |
||||||
|
then remove the contents of the local mailboxes, before upgrading to this |
||||||
|
version. Then run isync again to pull down the mail again. You must do |
||||||
|
this manually, the Debian package will not do this for you. |
||||||
|
|
||||||
|
-- Joey Hess <joeyh@debian.org> Tue, 29 Oct 2002 13:50:40 -0500 |
||||||
@ -0,0 +1,22 @@ |
|||||||
|
A note from isync's web site: |
||||||
|
|
||||||
|
To use this command effectively, you need a mail client that sets the T |
||||||
|
(trashed) flag when it deletes a message from a maildir mailbox, instead of |
||||||
|
just removing it altogether. Currently, only Mutt 1.3.27 supports this. Without |
||||||
|
such a client, isync will refetch the locally deleted messages from the server |
||||||
|
since they will never get expunged. Be sure to put |
||||||
|
|
||||||
|
set maildir_trash |
||||||
|
|
||||||
|
in your ~/.muttrc when using Mutt. |
||||||
|
|
||||||
|
isync can be integrated into Mutt fairly easily with a few hooks: |
||||||
|
|
||||||
|
folder-hook ~A bind index $ <sync-mailbox> |
||||||
|
folder-hook +maildir 'macro index $ "<sync-mailbox>!isync -e maildir\n"' |
||||||
|
|
||||||
|
where maildir is the name of the local mailbox (or its alias). This works well |
||||||
|
so long as you are not modifying the IMAP mailbox outside of Mutt. However, if |
||||||
|
you are using another mail program simultaneously Mutt will have the wrong idea |
||||||
|
of the local mailbox flags and messages will start disappearing from its index |
||||||
|
display (don't worry, they are still on disk). |
||||||
@ -0,0 +1,8 @@ |
|||||||
|
#!/bin/sh |
||||||
|
set -e |
||||||
|
. /usr/share/debconf/confmodule |
||||||
|
if [ "$1" = "configure" -a ! -z "$2" ] && \ |
||||||
|
dpkg --compare-versions "$2" lt 0.8; then |
||||||
|
db_input critical isync/upgrade_0.8 || true |
||||||
|
db_go || true |
||||||
|
fi |
||||||
@ -0,0 +1 @@ |
|||||||
|
[type: gettext/rfc822deb] templates |
||||||
@ -0,0 +1,60 @@ |
|||||||
|
# |
||||||
|
# Translators, if you are not familiar with the PO format, gettext |
||||||
|
# documentation is worth reading, especially sections dedicated to |
||||||
|
# this format, e.g. by running: |
||||||
|
# info -n '(gettext)PO Files' |
||||||
|
# info -n '(gettext)Header Entry' |
||||||
|
# |
||||||
|
# Some information specific to po-debconf are available at |
||||||
|
# /usr/share/doc/po-debconf/README-trans |
||||||
|
# or http://www.debian.org/intl/l10n/po-debconf/README-trans |
||||||
|
# |
||||||
|
# Developers do not need to manually edit POT or PO files. |
||||||
|
# |
||||||
|
#, fuzzy |
||||||
|
msgid "" |
||||||
|
msgstr "" |
||||||
|
"Project-Id-Version: PACKAGE VERSION\n" |
||||||
|
"Report-Msgid-Bugs-To: \n" |
||||||
|
"POT-Creation-Date: 2003-10-14 21:55+0200\n" |
||||||
|
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" |
||||||
|
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" |
||||||
|
"Language-Team: LANGUAGE <LL@li.org>\n" |
||||||
|
"MIME-Version: 1.0\n" |
||||||
|
"Content-Type: text/plain; charset=CHARSET\n" |
||||||
|
"Content-Transfer-Encoding: 8bit\n" |
||||||
|
|
||||||
|
#. Description |
||||||
|
#: ../templates:4 |
||||||
|
msgid "Abort isync upgrade" |
||||||
|
msgstr "" |
||||||
|
|
||||||
|
#. Description |
||||||
|
#: ../templates:4 |
||||||
|
msgid "" |
||||||
|
"You are upgrading from an older version of isync that stored the UID of each " |
||||||
|
"message in a way that is not compatable with the new version. You need to " |
||||||
|
"remove all the messages in local folders downloaded with the old version of " |
||||||
|
"isync. Otherwise isync will get confused and upload duplicate messages to " |
||||||
|
"the IMAP server." |
||||||
|
msgstr "" |
||||||
|
|
||||||
|
#. Description |
||||||
|
#: ../templates:4 |
||||||
|
msgid "" |
||||||
|
"A suggested upgrade procedure is to use the isync version 0.7 to synchronize " |
||||||
|
"any local changes in isync-managed mailboxes with your IMAP server (if there " |
||||||
|
"are any local changes to synchronise), and then remove the contents of the " |
||||||
|
"local mailboxes, before upgrading to version 0.8 or above. Then run isync " |
||||||
|
"again to pull down the mail again. You must do this manually; the Debian " |
||||||
|
"package will not do this for you." |
||||||
|
msgstr "" |
||||||
|
|
||||||
|
#. Description |
||||||
|
#: ../templates:4 |
||||||
|
msgid "" |
||||||
|
"If you want, the upgrade of isync can be aborted to let you deal with this " |
||||||
|
"issue. Or you can just suspend the upgrade or switch to a different virtual " |
||||||
|
"console to take care of it. Do not continue past this point before manually " |
||||||
|
"resolving this issue!" |
||||||
|
msgstr "" |
||||||
@ -0,0 +1,19 @@ |
|||||||
|
#!/bin/sh |
||||||
|
set -e |
||||||
|
|
||||||
|
if [ "$1" = "upgrade" ] && dpkg --compare-versions "$2" lt "0.8"; then |
||||||
|
# Do not do debconf stuff if debconf is not there. |
||||||
|
# I don't want to have to pre-depend on debconf. |
||||||
|
if [ -e /usr/share/debconf/confmodule ]; then |
||||||
|
. /usr/share/debconf/confmodule |
||||||
|
db_get isync/upgrade_0.8 |
||||||
|
if [ "$RET" = true ]; then |
||||||
|
echo "Aborting isync upgrade at your request so you can manually resolve upgrade issue." >&2 |
||||||
|
exit 1 |
||||||
|
fi |
||||||
|
else |
||||||
|
echo "WARNING: Read NEWS.Debian file about manual upgrade issues from isync 0.7." >&2 |
||||||
|
fi |
||||||
|
fi |
||||||
|
|
||||||
|
#DEBHELPER# |
||||||
@ -0,0 +1,21 @@ |
|||||||
|
Template: isync/upgrade_0.8 |
||||||
|
Type: boolean |
||||||
|
Default: false |
||||||
|
_Description: Abort isync upgrade |
||||||
|
You are upgrading from an older version of isync that stored the UID of |
||||||
|
each message in a way that is not compatable with the new version. You |
||||||
|
need to remove all the messages in local folders downloaded with the old |
||||||
|
version of isync. Otherwise isync will get confused and upload duplicate |
||||||
|
messages to the IMAP server. |
||||||
|
. |
||||||
|
A suggested upgrade procedure is to use the isync version 0.7 to |
||||||
|
synchronize any local changes in isync-managed mailboxes with your IMAP |
||||||
|
server (if there are any local changes to synchronise), and then remove |
||||||
|
the contents of the local mailboxes, before upgrading to version 0.8 or |
||||||
|
above. Then run isync again to pull down the mail again. You must do this |
||||||
|
manually; the Debian package will not do this for you. |
||||||
|
. |
||||||
|
If you want, the upgrade of isync can be aborted to let you deal with this |
||||||
|
issue. Or you can just suspend the upgrade or switch to a different |
||||||
|
virtual console to take care of it. Do not continue past this point before |
||||||
|
manually resolving this issue! |
||||||
Loading…
Reference in new issue