From: James Tucker <jftucker@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: Getting started submitting a patch
Date: Sun, 18 Mar 2012 17:38:05 -0700 [thread overview]
Message-ID: <5A3F2920-A774-47C0-901B-C89D53F6A5A7@gmail.com> (raw)
In-Reply-To: <20120305203453.GA1831@dcvr.yhbt.net>
On Mar 5, 2012, at 12:34 PM, Eric Wong wrote:
> brycemcd <brycebrycebaby@gmail.com> wrote:
>> ruby 1.9.3
>
>> test-unit (2.4.7)
>
>> /usr/local/rvm/gems/ruby-1.9.3-p0@rack-contrib/gems/test-spec-0.10.0/lib/test/spec.rb:12:in
>> `<class:AutoRunner>': uninitialized constant
>> Test::Unit::AutoRunner::RUNNERS (NameError)
>
> It could be a conflict with the test-unit (minitest wrapper) that's
> already bundled with Ruby 1.9.3. Does uninstalling test-unit 2.4.7
> help?
Correct, there is a conflict. Pretending to "update" test unit in ruby was quite the mistake.
We need to move rack-contrib over to bacon, test-spec is basically deprecated and largely unsupported these days.
prev parent reply other threads:[~2012-03-19 0:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 23:30 Getting started submitting a patch brycemcd
2012-03-05 20:34 ` Eric Wong
2012-03-19 0:38 ` James Tucker [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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5A3F2920-A774-47C0-901B-C89D53F6A5A7@gmail.com \
--to=rack-devel@googlegroups.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).