From: johnbent@lanl.gov (John Bent)
Subject: [sup-talk] scary exception
Date: Sat, 23 May 2009 23:54:42 -0600 [thread overview]
Message-ID: <1243143847-sup-5003@tangerine.lanl.gov> (raw)
In-Reply-To: <1240854270-sup-8870@entry>
Excerpts from William Morgan's message of Mon Apr 27 11:46:43 -0600 2009:
> Reformatted excerpts from John Bent's message of 2009-04-27:
> > I'm sorry. I don't remember. The timestamp on my sup executable says
> > Jan 13 2009. I'll try to upgrade and see if I ever see this again.
>
> Yeah, I think it was around March that things got merged in. Try it with
> the latest & greatest and see if it happens again.
>
Ok, I figured out what the problem was. I used to be able to stay
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 so I
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.
Anyway, at the risk of embarrassing myself, I wanted to get this info
out there in case some other poor schlub wanders down my same convoluted
path.
Thanks,
John
next prev parent reply other threads:[~2009-05-24 5:54 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 [this message]
2009-05-27 16:03 ` 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=1243143847-sup-5003@tangerine.lanl.gov \
--to=johnbent@lanl.gov \
/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