Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] migrating email to a new computer
Date: Thu, 11 Dec 2008 17:31:41 -0800	[thread overview]
Message-ID: <1229042458-sup-7539@entry> (raw)
In-Reply-To: <1228710381-sup-9800@buckwheat>

Reformatted excerpts from Daniel Wagner's message of 2008-12-07:
> entries in the dump file    26462

What is this number from? Is it a wc -l on the dumpfile, or sup-sync's
"Restored state on X messages" message? If the latter, what is wc -l?
(And if the former, what's the other number?)

> entries scanned             24779
> entries added               24373
> warnings                       27
> fakes                          75

Warnings and fakes we can ignore. (They still count as being added.)
Did sup-sync report a number of updates?

It should be the case that num adds + num updates = num scanned,
and num adds = index size (when starting from an empty index).

> The Numbers According To sup
>                             old machine     new machine
> messages in the index       26459           24416
> messages with +inbox           50              45
> messages with +Starred         67              57
> 
> So, I'm not sure I understand how to reconcile these numbers.  Things
> are mismatched in odd ways; for example, how could there be more
> entries in the dump than there are messages in the index?

Yes, that is weird. 26462 vs 26459 is what concerns me. How did three
new messages appear at dump time?

> Or how come "entries added" + "warnings" != "messages in the index"?

Messages with warnings or that needed fake headers should still be
added, so the question is really 24416 vs 24373. That's 43 new messages
that appeared in the index.

> That's okay, though.  There are people for whom impermanence is a way
> of life.

Uh oh. 

> There are a few categories of messages for which I really, really
> want the impermanence to start later, though -- specifically +inbox and
> +Starred messages.  Since there's only 15 of these lost, is there some
> way I can grab/index those manually?

The most direct way is to query the index through devel/console.sh. You
can find examples on the wiki or in the mailing list archives. Something
like
  Index.ferret.search("label:inbox", :limit => :all).hits.map { |h| Index.ferret[h.doc] }

will give you all the Ferret records with the index label, and you can
then query them for all the fields listed in index.rb. (They'll appear
as empty hashes, {}, when irb prints them out, but in reality they're
just lazily-filled.

That should give you the information you need to compare the two sets of
documents on both indexes, and figure out what the differences are.
-- 
William <wmorgan-sup at masanjin.net>


  parent reply	other threads:[~2008-12-12  1:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19 22:50 Daniel Wagner
2008-11-27  0:05 ` William Morgan
2008-12-08  5:14   ` Daniel Wagner
2008-12-08  5:33     ` Mr.
2008-12-12  1:31     ` William Morgan [this message]
2008-11-28  2:25 ` Daniel Wagner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1229042458-sup-7539@entry \
    --to=wmorgan-sup@masanjin.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox