sup talk - Feb 2011 - message missing in source, sup v0.12.1, sup-sync no longer has --changed?

Hi!
I have my sent messages in a maildir and deleted one message.
sup-sync used to have --changed to fix this in the index, but no longer 
has (the FAQ still says so).
Sup only says that there was an error loading the message, but does not 
say how to fix the index.
Is there a new method to do this?

Thanks in advance and
all the best,
John

Excerpts from Jon Austin''s message of Fri Feb 11 20:29:28 +0100
2011:
> I think sup-sync -o may fix it.
> 
> (I''ve been having a strange issue since .12 came out if I send a
message and then quit sup, then relaunch, it''ll show the first line of
the message, ending in ''.....'' and then show the below error
(inside the message), until I sup-sync -o)
> 
> ***********************************************************************
>  An error occurred while loading this message.
> ***********************************************************************
> 
> I even spent several hours yesterday completely rebuilding the xapian
index, but still happening...if anyone has a clue what could be causing this,
I''d love to hear it :)

Hmm. In lib/sup/index.rb it says:
  ## xapian-compact takes too long, so this is a no-op
  ## until we think of something better
  def optimize
  end

And from what I understand, the -o optime does not do more at the moment.

So the question remain - if messags are missing from one Maildir, is my only
option to dump, reindex all and restore?
That would be painful given the number of messages...

--

Excerpts from John Wyzer''s message of Wed Feb 09 06:57:19 +0100 2011:
> I have my sent messages in a maildir and deleted one message.
> sup-sync used to have --changed to fix this in the index, but no longer 
> has (the FAQ still says so).
> Sup only says that there was an error loading the message, but does not 
> say how to fix the index.
Check out the recent thread "Delete email from Sup index" [1] on
sup-talk and my patch [2] on sup-devel.

Sascha

[1] http://rubyforge.org/pipermail/sup-talk/2011-February/thread.html#4511
[2] http://rubyforge.org/pipermail/sup-devel/2011-February/thread.html#982
-- 
http://sascha.silbe.org/
http://www.infra-silbe.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 494 bytes
Desc: not available
URL:
<http://rubyforge.org/pipermail/sup-talk/attachments/20110213/139c733e/attachment-0001.bin>

Hi,

Excerpts from John Wyzer''s message of Sun Feb 13 09:20:13 +0100
2011:
> So the question remain - if messags are missing from one Maildir, is my
only
> option to dump, reindex all and restore?  That would be painful given the
> number of messages...
Not only painful and annoying but also very stupid. Why would someone want to
get rid of sup-sync --changed? It happens all the time that Maildirs are
externally changed, there *should* be some easy way to sync these changes back,
at least that''s my insignificant opinion. I don''t completely
understand the
motivation for getting rid of this feature in the first place. Can someone
please explain?

Best regards,

Moritz

Excerpts from Moritz Wilhelmy''s message of 2011-02-13 08:59:12
-0500:
> Excerpts from John Wyzer''s message of Sun Feb 13 09:20:13 +0100
2011:
> > So the question remain - if messags are missing from one Maildir, is
my only
> > option to dump, reindex all and restore?  That would be painful given
the
> > number of messages...
> 
> Not only painful and annoying but also very stupid. Why would someone want
to
> get rid of sup-sync --changed? It happens all the time that Maildirs are
> externally changed, there *should* be some easy way to sync these changes
back,
> at least that''s my insignificant opinion. I don''t
completely understand the
> motivation for getting rid of this feature in the first place. Can someone
> please explain?
sup-sync --changed was removed because it is no longer necessary. The
maildir code can now gracefully deal with messages being moved and
deleted. If all locations for a message are deleted it will keep the
index entry (including the snippet) but display an error (inline, not
disrupting the rest of the UI) if you try to view the message.

Is this the behavior you''re seeing, or is there a bug in the
implementation?

Sascha posted a patch that deletes index entries with no locations after
a sync. I''d rather see that as a extra sup-sync --purge option, and if
you don''t want deleted messages to appear in the UI we should just
check
for that before adding them to the ThreadSet.