Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#744259: isync: mbsync prints previous slave message counts when creating new

164 views
Skip to first unread message

Guillem Jover

unread,
Apr 12, 2014, 12:50:02 AM4/12/14
to
Package: isync
Version: 1.1.0-2
Severity: minor

Hi!

While doing the first sync with mbsync, it needs to create the Maildir
folders, after having stopped the sync mid-air, and started it again it
seems it's not properly initializing some data structures, and ends
up printing the message count for the previously initialized Maildir
folder, here's an excerpt of the second session:

,--
Selecting master debian/lists/hurd...
Selecting slave debian/lists/hurd...
Loading master...
Loading slave...
slave: 5758 messages, 1263 recent
master: 5758 messages, 0 recent
Synchronizing...
Selecting master debian/lists/devel-games...
Selecting slave debian/lists/devel-games...
Loading master...
Loading slave...
slave: 3014 messages, 832 recent
master: 3014 messages, 0 recent
Synchronizing...
Selecting master debian/lists/announce...
Selecting slave debian/lists/announce...
Maildir notice: no UIDVALIDITY, creating new.
Loading master...
Loading slave...
slave: 3014 messages, 832 recent
master: 94 messages, 0 recent
Synchronizing...
M: +0/0 *0/0 #0/0 S: +94/94 *0/0 #0/0
Selecting master debian/lists/private...
Selecting slave debian/lists/private...
Maildir notice: no UIDVALIDITY, creating new.
Loading master...
Loading slave...
slave: 3014 messages, 832 recent
master: 8465 messages, 3 recent
Synchronizing...
M: +0/0 *0/0 #0/0 S: +8465/8465 *0/0 #0/0
`---

So, here debian/lists/hurd and debian/lists/devel-games had been synced
in the previous run, but not the subsequent ones.

Thanks,
Guillem


--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Alessandro Ghedini

unread,
Apr 12, 2014, 2:10:02 PM4/12/14
to
I'm not sure I understand. Were debian/lists/hurd and debian/lists/devel-games
completely synchronized on the first run (the one you interrupted)? If so, I
don't see any problem. The output of mbsync is rather verbose, and for each run
it always prints something like this:

Selecting master <maildir>...
Selecting slave <maildir>...
Loading master...
Loading slave...
slave: X messages, Y recent
master: W messages, Z recent
Synchronizing...

but if master and slave are already synchronized it doesn't do anything else.

Cheers
signature.asc

Guillem Jover

unread,
Apr 12, 2014, 6:00:01 PM4/12/14
to
On Sat, 2014-04-12 at 19:59:11 +0200, Alessandro Ghedini wrote:
> On Sat, Apr 12, 2014 at 06:44:52AM +0200, Guillem Jover wrote:
> > Package: isync
> > Version: 1.1.0-2
> > Severity: minor

Yes, I see I was probably not clear enough. debian/lists/devel-games was
the last fully synced Maildir, notice the message count:

,---
slave: 3014 messages, 832 recent
master: 3014 messages, 0 recent
`---

then it continues with debian/lists/announce, which was partially synced
and w/o a .uidvalidity file, as it had been interrupted in the middle in
the previous run, now notice the slave messages which are clearly wrong,
and a copy of the previous slave Maildir:

,---
slave: 3014 messages, 832 recent
master: 94 messages, 0 recent
`---

and the same for all subsequent Maildirs, which were non-existent
locally at this point, like debian/lists/private:

,---
slave: 3014 messages, 832 recent
master: 8465 messages, 3 recent
`---

same slave counts as debian/lists/devel-games. Hope that clarifies.

So my guess is that the program uses a data structure to hold the
Maildir information, and it shares it with all folders, and for newly
created ones it does not reset them to 0? Or something like that.

Alessandro Ghedini

unread,
Apr 13, 2014, 6:40:03 AM4/13/14
to
Control: tags -1 fixed-upstream

On sab, apr 12, 2014 at 11:52:36 +0200, Guillem Jover wrote:
> On Sat, 2014-04-12 at 19:59:11 +0200, Alessandro Ghedini wrote:
> > On Sat, Apr 12, 2014 at 06:44:52AM +0200, Guillem Jover wrote:
> > > Package: isync
> > > Version: 1.1.0-2
> > > Severity: minor
>
> > I'm not sure I understand. Were debian/lists/hurd and debian/lists/devel-games
> > completely synchronized on the first run (the one you interrupted)?
>
> Yes, I see I was probably not clear enough. debian/lists/devel-games was
> the last fully synced Maildir, notice the message count:
>
> ,---
> slave: 3014 messages, 832 recent
> master: 3014 messages, 0 recent
> `---
>
> then it continues with debian/lists/announce, which was partially synced
> and w/o a .uidvalidity file, as it had been interrupted in the middle in
> the previous run, now notice the slave messages which are clearly wrong,
> and a copy of the previous slave Maildir:
>
> ,---
> slave: 3014 messages, 832 recent
> master: 94 messages, 0 recent
> `---
>
> and the same for all subsequent Maildirs, which were non-existent
> locally at this point, like debian/lists/private:
>
> ,---
> slave: 3014 messages, 832 recent
> master: 8465 messages, 3 recent
> `---
>
> same slave counts as debian/lists/devel-games. Hope that clarifies.

Ah, I understand now. In any case upstream has been quicker than me and already
pushed a fix [0].

Cheers

[0] http://sourceforge.net/p/isync/isync/ci/4d85751
signature.asc
0 new messages