From: Tero Tilus <tero@tilus.net>
To: Sup users <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] git co old version
Date: Sat, 23 Apr 2011 12:25:36 +0300 [thread overview]
Message-ID: <1303550452-sup-7133@tilus.net> (raw)
In-Reply-To: <1303502527-sup-8162@guava.lanl.gov>
John Bent, 2011-04-22 23:03:
> But now a sup problem if you don't mind with sup-convert-ferret-index:
>
> jvpn-132-106:~>sup-convert-ferret-index
> /opt/local/lib/ruby1.9/gems/1.9.1/gems/sup-0.10.2/lib/sup/index.rb:229:in
> `rescue in init': unknown index type "ferret": no such file to load --
> ferret (RuntimeError)
Wasn't ferret support dropped already before 0.10 or do I just remeber
wrong? And why did you ask for git commands if you are using old sup
from gems? And in case I got something wrong here, it seems to be
missing ferret (the gem). Does gem list show ferret?
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-04-23 9:34 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 [this message]
2011-04-26 16:30 ` John Bent
2011-04-26 18:33 ` Tero Tilus
2011-05-12 3:28 ` John Bent
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=1303550452-sup-7133@tilus.net \
--to=tero@tilus.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