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? 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. > 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. -- William <wmorgan-...@masanjin.net> _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
