sup talk - Nov 2011 - failure to start sup

Something happend on my Arch computer to cause sup to stop loading.

When I run sup I get the following messages:
--------------------------------------------------
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'': iconv
will
be deprecated in the future, use String#encode instead.
/usr/lib/ruby/gems/1.9.1/gems/gettext-2.1.0/lib/gettext/runtime/locale_path.rb:20:
Use RbConfig instead of obsolete and deprecated Config.
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'':
libxapian.so.22: cannot open shared object file: No such file or directory
- /usr/lib/ruby/gems/1.9.1/gems/xapian-full-1.2.3/lib/_xapian.so (LoadError)
        from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in
`require''
        from
/usr/lib/ruby/gems/1.9.1/gems/xapian-full-1.2.3/lib/xapian.rb:42:in
`<module:Xapian>''
        from
/usr/lib/ruby/gems/1.9.1/gems/xapian-full-1.2.3/lib/xapian.rb:40:in `<top
(required)>''
        from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in
`require''
        from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in
`require''
        from /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup/index.rb:3:in
`<top (required)>''
        from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in
`require''
        from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in
`require''
        from /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/lib/sup.rb:358:in
`<top (required)>''
        from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in
`require''
        from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in
`require''
        from /usr/lib/ruby/gems/1.9.1/gems/sup-0.12.1/bin/sup:15:in `<top
(required)>''
        from /usr/bin/sup:19:in `load''
        from /usr/bin/sup:19:in `<main>''
------------------------------------------------------

I removed sup and I think all of its dependancies and then reinstalled
using yaourt -S sup.
I noticed that ruby is not 1.9.3 which I think was 1.9.1 before.  I
don''t
know if that has any impact or not.

I appreciate any insight anybody might have.

I am looking forward to having my favorite email client usable again.

Karl

-- 
Karl Harris
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/sup-talk/attachments/20111110/874dc522/attachment.html>

Reformatted excerpts from Karl Harris''s message of
2011-11-10:
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'':
> libxapian.so.22: cannot open shared object file: No such file or directory
Looks like it can''t find xapian. The first thing to try would be
reinstalling
the xapian-full gem.
-- 
William <wmorgan-sup at masanjin.net>