Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] scary exception
Date: Wed, 27 May 2009 09:03:13 -0700	[thread overview]
Message-ID: <1243439962-sup-7477@entry> (raw)
In-Reply-To: <1243143847-sup-5003@tangerine.lanl.gov>

Reformatted excerpts from John Bent's message of 2009-05-23:
> current with git pull; rake gem; sudo gem install pkg/sup-999.gem.  But
> with a new work proxy and my inability to get git to work w/ a proxy, I
> switched to:
> 
> git clone http://git.gitorious.org/sup/mainline.git
> 
> Then I couldn't figure out how to make a gem in mainline or install

These operations should all be the same, regardless of whether you're
cloning the git:// uri or the http:// one.

> just figured out I could approximate an install by copying bin/* into my
> path . . . forgot the lib.  Anyway, I got the scary exception again and
> looked at exception-log.txt and realized I had a mismatch with my libs.
> So now I'm doing the git clone mainline thing and using ruby -l lib -w
> bin/sup.

Sup does maintain different version numbers for bin/sup and lib/sup.rb,
and checks for a mismatch, but that's not useful for different versions
from git, since they all claim version "git".

Oh well, glad it works now.
-- 
William <wmorgan-sup at masanjin.net>


      reply	other threads:[~2009-05-27 16:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27  3:28 John Bent
2009-04-27 17:25 ` William Morgan
2009-04-27 17:34   ` John Bent
2009-04-27 17:46     ` William Morgan
2009-05-24  5:54       ` John Bent
2009-05-27 16:03         ` William Morgan [this message]

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=1243439962-sup-7477@entry \
    --to=wmorgan-sup@masanjin.net \
    /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