From: Karl Harris <karlh626@gmail.com>
To: sup-talk@rubyforge.org
Subject: [sup-talk] failure to start sup
Date: Thu, 10 Nov 2011 11:47:23 -0500 [thread overview]
Message-ID: <CAJRi-a-4st1iyYgUqYeyQQ7RMrTSFPwga2idkAsftS+UvsDitQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2133 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 2611 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2011-11-10 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 16:47 Karl Harris [this message]
2011-11-10 17:22 ` William Morgan
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=CAJRi-a-4st1iyYgUqYeyQQ7RMrTSFPwga2idkAsftS+UvsDitQ@mail.gmail.com \
--to=karlh626@gmail.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