From: cworth@cworth.org (Carl Worth)
Subject: [sup-talk] Exception trying to run git source
Date: Wed, 19 Aug 2009 14:37:15 -0700 [thread overview]
Message-ID: <1250717434-sup-4489@yoom.home.cworth.org> (raw)
In-Reply-To: <1250712045-sup-3506@masanjin.net>
Excerpts from William Morgan's message of Wed Aug 19 13:02:26 -0700 2009:
> I find it surprising too. I haven't seen taht behavior before. FWIW, Sup
> does try and detect if bin/sup and lib/sup have mismatched versions, and
> that didn't fire... I wonder if it's just sent.rb that's been loaded.
> Did you somehow delete sent.rb from your git directory, or something
> like that?
Nope. The git checkout is entirely intact, and it was quite a large
number of modules getting misloaded.
I ran an strace on the ruby process[*] and was able to plainly see
that modules were being correctly loaded from ./lib until after
/usr/lib/ruby/1.8/chronic.rb was loaded. After that, ruby would look
for modules in /usr/lib/ruby/1.8 before ./lib. And sure enough, the
first line of my chronic.rb has:
$:.unshift File.dirname(__FILE__) # For use/testing when no gem is installed
I'll go ahead and find the right place to file that bug, but at least
the mystery is solved now.
-Carl
[*] http://cworth.org/~cworth/tmp/ruby-sup.strace
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090819/5e1ba854/attachment.bin>
next prev parent reply other threads:[~2009-08-19 21:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 0:49 Carl Worth
2009-08-19 2:47 ` Ben Walton
2009-08-19 15:59 ` Ben Walton
2009-08-19 16:19 ` William Morgan
2009-08-19 16:33 ` Carl Worth
2009-08-19 16:34 ` Ben Walton
2009-08-19 17:53 ` Carl Worth
2009-08-19 18:08 ` Ben Walton
2009-08-19 18:52 ` William Morgan
2009-08-19 19:40 ` Carl Worth
2009-08-19 20:02 ` William Morgan
2009-08-19 21:37 ` Carl Worth [this message]
2009-08-22 20:23 ` William Morgan
2009-08-26 21:26 ` Carl Worth
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=1250717434-sup-4489@yoom.home.cworth.org \
--to=cworth@cworth.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