From: cworth@cworth.org (Carl Worth)
Subject: [sup-talk] Exception trying to run git source
Date: Wed, 26 Aug 2009 14:26:18 -0700 [thread overview]
Message-ID: <1251321606-sup-7393@yoom.home.cworth.org> (raw)
In-Reply-To: <1250964942-sup-8625@masanjin.net>
Reformatted excerpts from William Morgan's message of Sat Aug 22 13:23:17 -0700 2009:
> Reformatted excerpts from Carl Worth's message of 2009-08-19:
> > $:.unshift File.dirname(__FILE__) # For use/testing when no gem is installed
>
> I'd call that a bug in chronic. It shouldn't be screwing with the load
> path.
That's what I thought too. I filed a Debian bug against the
libchronic-ruby package here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542491
But I reall only did that because I didn't find any contact
information for how to submit an upstream bug against chronic
(http://chronic.rubyforge.net didn't have any details that I could
find).
So if someone knows a better place to file the bug, I'd be glad to do
that.
> Nice debug work.
Thanks.
-Carl
-------------- 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/20090826/41bd963c/attachment.bin>
prev parent reply other threads:[~2009-08-26 21:26 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
2009-08-22 20:23 ` William Morgan
2009-08-26 21:26 ` Carl Worth [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=1251321606-sup-7393@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