[sup-talk] sup-sync-back not syncing all usual sources

[William Morgan]

Excerpts from jeff.covey's message of Sun Jun 17 18:00:24 -0700 2007:
> thanks, it now spits out the names of all of my usual sources and
> moves deleted files from some, but not all of them.

This I'm still not sure about and I can't replicate. a) Does it still
happen with recent SVN, and b) are there any distinguishing features
about which sources it moves stuff from and which it wrongly ignores?

> would it make more sense for sup-sync-back to process only those
> sources which need to be synced back (at this stage in sup-sync-back's
> life, those which have spam/deleted messages)?

Great idea. This is in SVN now.

> also, at the end of running sup-sync-back without specifying a source, i get
> this:
> 
> Scanning sup://sent...
> Scanned 4, deleted 0, moved 0 messages from sup://sent.
> [Sun Jun 17 20:32:34 -0400 2007] saving index and sources...
> [Sun Jun 17 20:32:35 -0400 2007] unlocking /home/jeff/.sup/lock...
> /usr/lib/ruby/1.8/fileutils.rb:505:in `rename': No such file or directory -
> /tmp/sup-sync-back-9998.1089.0 or  (Errno::ENOENT)

This should be fixed as well.

Let me know how things are working for you.

-- 
William <wmorgan-sup at masanjin.net>