sup talk - Jun 2007 - sup-sync-back not syncing all usual sources

sup-sync-back''s help says "If no sources are given, sync back all
usual
sources", but this doesn''t seem to be happening.

i just tested it by commenting out the sup-sync-back section of my sup
wrapper script and marking a bunch of threads to be deleted.  then i ran
this:

sup-sync-back --move-deleted ~/tmp/sup-deleted.mbox --move-spam
~/tmp/sup-deleted.mbox

, and it acted as though there were nothing to be done.  then i reinstated
the part of my script which checks which sources need to be sync-backed
(included below), and it processed them all and moved the deleted messages
out of them as it should.

thanks,
jeff


ruby=''ruby -I lib -w''
cd ~/tmp/sup/trunk

echo "checking for messages to delete..."
deletedids=`$ruby bin/sup-dump | grep deleted | sed -e
''s/(.*//''`;
mboxes=~/mail/*-`date +%Y-%m`
for id in $deletedids ; do
	deletedmboxes=`grep -l $id $mboxes`;
	for mbox in $deletedmboxes ; do 
		$ruby bin/sup-sync-back --move-deleted ~/tmp/sup-deleted.mbox --move-spam
~/tmp/sup-deleted.mbox mbox://$mbox ;
		$ruby bin/sup-sync --changed mbox://$mbox ;
	done ;
done


-- 
jeff covey
http://jeffcovey.net/

Excerpts from jeff.covey''s message of Thu Jun 14 09:13:21 -0700
2007:
> sup-sync-back''s help says "If no sources are given, sync back
all usual
> sources", but this doesn''t seem to be happening.
Fixed in svn. Thanks!

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

Excerpts from William Morgan''s message of Sun Jun 17 16:30:08 -0400
2007:
> > sup-sync-back''s help says "If no sources are given, sync
back all usual
> > sources", but this doesn''t seem to be happening.
> 
> Fixed in svn. Thanks!
thanks, it now spits out the names of all of my usual sources and moves
deleted files from some, but not all of them.  i changed my wrapper script
to first just run sup-sync-back without specifying a source, then to run it
as i used to do on those sources with messages tagged "deleted" in the
index.  the first run moves some deleted messages, and the second the rest.

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)?

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)
        from /usr/lib/ruby/1.8/fileutils.rb:505:in `mv''
        from /usr/lib/ruby/1.8/fileutils.rb:1395:in `fu_each_src_dest''
        from /usr/lib/ruby/1.8/fileutils.rb:1411:in `fu_each_src_dest0''
        from /usr/lib/ruby/1.8/fileutils.rb:1393:in `fu_each_src_dest''
        from /usr/lib/ruby/1.8/fileutils.rb:494:in `mv''
        from bin/sup-sync-back:115
        from bin/sup-sync-back:68:in `each''
        from bin/sup-sync-back:68


-- 
jeff covey
http://jeffcovey.net/

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>

Excerpts from William Morgan''s message of Tue Jul 10 14:21:57 -0400
2007:
> > 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?
i just tried running sup-sync-back without specifying any sources for a
week, then ran my script to look for messages waiting to be deleted.  my
script didn''t find anything, so this seems to be working fine for me
now.

thanks,

-- 
jeff covey
http://jeffcovey.net/