Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Neil Stewart <neil.stewart@warwick.ac.uk>
To: sup-talk@rubyforge.org
Subject: [sup-talk] gem install sup fail
Date: Thu, 8 Apr 2010 11:49:46 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.1.10.1004081146590.23329@stewart.warwick.ac.uk> (raw)

So I'm trying to install sup-0.11 and am having trouble. I think my install
went okay:

# gem install sup
Building native extensions.  This could take a while...
Building native extensions.  This could take a while...
Successfully installed xapian-full-1.1.3.4
Successfully installed ncurses-0.9.1
Successfully installed rmail-1.0.0
Successfully installed highline-1.5.2
Successfully installed net-ssh-2.0.21
Successfully installed trollop-1.16.2
Successfully installed lockfile-1.4.3
Successfully installed mime-types-1.16
Successfully installed locale-2.0.5
Successfully installed gettext-2.1.0
Successfully installed sup-0.11
11 gems installed
Installing ri documentation for xapian-full-1.1.3.4...
Installing ri documentation for ncurses-0.9.1...
Installing ri documentation for rmail-1.0.0...
Installing ri documentation for highline-1.5.2...
Installing ri documentation for net-ssh-2.0.21...
Installing ri documentation for trollop-1.16.2...
Installing ri documentation for lockfile-1.4.3...
Installing ri documentation for mime-types-1.16...
Installing ri documentation for locale-2.0.5...
Installing ri documentation for gettext-2.1.0...
Installing ri documentation for sup-0.11...
Installing RDoc documentation for xapian-full-1.1.3.4...
Installing RDoc documentation for ncurses-0.9.1...
Installing RDoc documentation for rmail-1.0.0...
Installing RDoc documentation for highline-1.5.2...
Installing RDoc documentation for net-ssh-2.0.21...
Installing RDoc documentation for trollop-1.16.2...
Installing RDoc documentation for lockfile-1.4.3...
Installing RDoc documentation for mime-types-1.16...
Installing RDoc documentation for locale-2.0.5...
Installing RDoc documentation for gettext-2.1.0...
Installing RDoc documentation for sup-0.11...

But how do I run sup? This fails:

# /var/lib/gems/1.8/bin/sup
/usr/lib/ruby/1.8/rubygems.rb:578:in `report_activate_error': Could not find
/RubyGem archive-tar-minitar (~> 0.5) (Gem::LoadError)
         from /usr/lib/ruby/1.8/rubygems.rb:134:in `activate'
         from /usr/lib/ruby/1.8/rubygems.rb:158:in `activate'
         from /usr/lib/ruby/1.8/rubygems.rb:157:in `each'
         from /usr/lib/ruby/1.8/rubygems.rb:157:in `activate'
         from /usr/lib/ruby/1.8/rubygems.rb:158:in `activate'
         from /usr/lib/ruby/1.8/rubygems.rb:157:in `each'
         from /usr/lib/ruby/1.8/rubygems.rb:157:in `activate'
         from /usr/lib/ruby/1.8/rubygems.rb:49:in `gem'
         from /var/lib/gems/1.8/bin/sup:18

Any comments would be much appreciated---sup seems too good for me to give
up now!

Best,
Neil.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


             reply	other threads:[~2010-04-08 11:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08 10:49 Neil Stewart [this message]
2010-04-08 12:04 ` Neil Stewart

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=alpine.DEB.1.10.1004081146590.23329@stewart.warwick.ac.uk \
    --to=neil.stewart@warwick.ac.uk \
    --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