Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Steve Goldman <sgoldman@tower-research.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Problems running sup-convert-ferret-index
Date: Mon, 25 Jan 2010 16:56:24 -0500	[thread overview]
Message-ID: <1264456502-sup-2092@sgoldmanlinux.tower-research.com> (raw)
In-Reply-To: <1264454942-sup-8589@masanjin.net>

Excerpts from William Morgan's message of Mon Jan 25 16:30:48 -0500 2010:
> Reformatted excerpts from Steve Goldman's message of 2010-01-25:
> > Tried running sup-config from scratch last night.  No dice.  sup-sync
> > failed after about ten minutes.
> > 
> > What info can I supply that would help debug this?
> 
> Is it still a segfault?

Presumably.  I run it through sup-config, which outputs "Rats, that
didn't work" when the return code is non-zero.  But sup-sync outputs
nothing.


> If so, what does gem list --local say the version is of the "xapian" or
> "xapian-full" gem?

It's installed with our Fedora release, but my guy tells me this is
the version info:

xapian-bindings-ruby-1.0.17-2.fc11.x86_64


> > ruby version 1.8.6
> 
> How difficult would it be to try with 1.9.1, or at least 1.8.7?

He says the Fedora release will likely get there soon, but we could
try to get it in advance if you think this will help.

Thanks.
-- 

Steve Goldman
sgoldman@tower-research.com

T: 212.219.6014
F: 212.219.6007

Tower Research Capital, LLC
377 Broadway, 11th Fl.
New York, NY 10013
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2010-01-25 22:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-17 19:50 Steve Goldman
2010-01-17 20:38 ` William Morgan
2010-01-17 21:22   ` Steve Goldman
2010-01-17 21:34     ` William Morgan
2010-01-17 23:38       ` Steve Goldman
2010-01-18  0:04         ` William Morgan
2010-01-18  0:28           ` Steve Goldman
2010-01-18  1:44             ` Steve Goldman
2010-01-18  2:10               ` Rich Lane
2010-01-18  6:03                 ` Anirudh Sanjeev
2010-01-18 17:04                   ` William Morgan
2010-01-18 17:27                     ` Anirudh Sanjeev
2010-01-18 19:43                 ` Steve Goldman
2010-01-18 22:05                   ` William Morgan
2010-01-19 13:31                     ` Steve Goldman
2010-01-19 13:37                       ` William Morgan
2010-01-25 16:34                         ` Steve Goldman
2010-01-25 21:30                           ` William Morgan
2010-01-25 21:56                             ` Steve Goldman [this message]
2010-01-26 13:00                               ` William Morgan
2010-01-27  3:24                                 ` Steve Goldman

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=1264456502-sup-2092@sgoldmanlinux.tower-research.com \
    --to=sgoldman@tower-research.com \
    --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