On Thu, Nov 09, 2006 at 00:11:01 +0100, Nicolas Boullis wrote:
> Hi,
>
> On Sun, Nov 05, 2006 at 12:55:03PM +0100, Nicolas Boullis wrote:
> >
> > OK, I can't promise anything but I can try to prepare a 1.0.3 upload (at
> > least for experimental at first).
>
> I just tried 1.0.3 (at last) and to be honnest I am slightly
> disappointed. I found a few behavioral differences:
> 1) when User was not specified, 0.9.2 used the name of the user
> running isync; 1.0.3 fails;
OK, I'll look at this if I find the time. Sounds easy to fix, though.
> 2) when a message is deleted localy, 0.9.2 redownloads it while 1.0.3
> deletes it remotely;
I would call this a feature, not a bug. You don't need "set
maildir_trash" anymore in your .muttrc, and isync will also work with
MUAs that don't support the "trash" flag. That means that isync should
now work with any MUA that supports maildir.
> 3) the MaxMessages option does not work at all.
OK, I never used that. I'll try to reproduce that, too.
>
> 1) is not much of an issue, since one can easily add a User option to
> ~/.isyncrc.
> 2) might be confusing. I guess not that many users delete a message
> and expect it to be redownloaded, but those who do would experience data
> loss.
I've prepared an isync 1.0.3 package that contains a NEWS.Debian file
that already describes the maildir_trash issue, but the above comment
could also be added.
> 3) is a major regression for me, since I have some huge IMAP mailboxes
> and use isync to keep a local copy of the latest messages of each
> mailbox on my (very space-limited) laptop.
I'm quite sure that upstream will fix this once it gets reported. All
other compatibility issues I found were fixed very fast.
> Unless I am missing something, I don't think it would be a good idea to
> replace the old isync with the new one. On the other hand, adding a new
> package would be an option, but both would have /usr/bin/isync and hence
> have to conflict.
I don't think it's a good idea to release Etch with a 2,5 year old
upstream version, with known bugs and limittions (in my point of view,
that maildir_trash thing is a limitation) that are sorted out in new
upstream versions.
As the isync wrapper is intended to behave like the old version, there
is no need for a completely new package. However, it still seems to
have some glitches and needs more testing.
Apart from that, the new mbsync program is much more configurable, and
maybe the users want to benefit from that.
My isync 1.0.3 package can be found here:
http://tikei.de/isync/
It misses the debconf and translation stuff from the 0.9.2 package, as
it addresses an older compatibility issue and I don't think that it is
relevant anymore.
Regards,
Tino
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
