From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Can't search without crashing
Date: Sun, 01 Nov 2009 09:23:49 -0800 [thread overview]
Message-ID: <1257095945-sup-1972@masanjin.net> (raw)
In-Reply-To: <1257094049-sup-1250@sgoldmanlinux.tower-research.com>
Reformatted excerpts from Steve Goldman's message of 2009-11-01:
> I'm replacing those sources (at least I backed up the sources.yaml
> file) and will see how that goes.
If you're really done with a source, you can remove it from
sources.yaml, but you also need to remove all messages from the index.
You should be able do something like:
$ sh devel/console.sh
>> q = Index.parse_query "source_id:4"
=> # ...
>> Index.each_id(q) { |id| Index.delete id }
=> nil
>> Index.save
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2009-11-01 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 20:15 Steve Goldman
2009-10-26 23:30 ` Steve Goldman
2009-10-27 9:58 ` Tero Tilus
2009-10-27 12:14 ` Steve Goldman
2009-11-01 16:32 ` William Morgan
2009-11-01 16:48 ` Steve Goldman
2009-11-01 17:23 ` William Morgan [this message]
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=1257095945-sup-1972@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-talk@rubyforge.org \
/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