Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: John Bent <johnbent@lanl.gov>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] git co old version
Date: Wed, 11 May 2011 21:28:39 -0600	[thread overview]
Message-ID: <1305170697-sup-9267@barista.lanl.gov> (raw)
In-Reply-To: <1303842631-sup-8740@tilus.net>

Excerpts from Tero Tilus's message of Tue Apr 26 12:33:14 -0600 2011:
> John Bent, 2011-04-26 19:30:
> > Sadly however, I still can't get sup-convert-ferret-index to run.
> 
> I've got no idea whats wrong with your sup-convert-ferret-index.  I'm
> not 100% sure, but I assume you could just try to sup-dump with old
> enough sup (preferably the one you've been using) and reindex +
> restore using current.
> 
Just a follow-up.  I am finally off ferret and am all the way onto
0.12.1!  I'm not sure why it was so difficult but I could never
successfully convert from ferret to xapian on an OS X box.  On 10.5.8, I
couldn't ever get xapian working and on 10.6 I couldn't get ferret
working.  I finally just migrated to a real linux box and am happily
sup'ing again!  Thanks to everyone who chimed in trying to help me. 
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


      reply	other threads:[~2011-05-12  3:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-22 14:29 John Bent
2011-04-22 16:14 ` Tero Tilus
2011-04-22 20:03   ` John Bent
2011-04-23  9:25     ` Tero Tilus
2011-04-26 16:30       ` John Bent
2011-04-26 18:33         ` Tero Tilus
2011-05-12  3:28           ` John Bent [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=1305170697-sup-9267@barista.lanl.gov \
    --to=johnbent@lanl.gov \
    --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