Excerpts from William Morgan's message of Tue Jan 26 08:00:02 -0500 2010: > Reformatted excerpts from Steve Goldman's message of 2010-01-25: > > 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. > > And just to confirm, when you run that sup-sync command by itself, > outside of sup-config, it just dies without a backtrace, right?
Correct. > Since this didn't happen with Ferret, my best guess is that the problem > lies somewhere in the bowels of Xapian or the bindings thereof: > > > xapian-bindings-ruby-1.0.17-2.fc11.x86_64 > > I would try and get the latest xapian-full gem. I have no experience > with the bindings Fedora distributes, but I know that that gem works for > me and for others. > > It's possible to install and run gems entirely out of your home > directory (at least in recent versions), so it should be possible to do > this without involving your sysadmin, if that's easier. > > Something like: > > gem install gemcutter > gem install xapian-full > > Ought to magically work, if your gems are new enough. Do I need to do something to make ruby use this xapian and not the Fedora xapian? How can I tell which it is using? > > 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. > > Let's wait on playing with Ruby versions until we have your Xapian > bindings locked down. I did some sleuthing and found that it hangs on the loop over all the messages in my first source (imap) after it gets through exactly seven of them. Specifically, it hangs at the top of the loop: Redwood::PollManager.each_message_from source do |m| Any ideas? Thanks. -- Steve Goldman [email protected] T: 212.219.6014 F: 212.219.6007 Tower Research Capital, LLC 377 Broadway, 11th Fl. New York, NY 10013 _______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
