summaryrefslogtreecommitdiff
path: root/ISSUES.md
diff options
context:
space:
mode:
authorAndre Arko <andre@arko.net>2011-05-27 12:42:39 -0700
committerAndre Arko <andre@arko.net>2011-05-27 12:42:39 -0700
commit571e3e9c42cf06af7bd2a8c83a862fb62799f626 (patch)
tree6f3b2b5b3a9619041dda1fb6a44e830e68f10896 /ISSUES.md
parent365ce9564d90316134b335c9020e656d4b7e712e (diff)
downloadbundler-571e3e9c42cf06af7bd2a8c83a862fb62799f626.tar.gz
Update spork issue fix with versions
Diffstat (limited to 'ISSUES.md')
-rw-r--r--ISSUES.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/ISSUES.md b/ISSUES.md
index f04e47dd99..3fe035fcb2 100644
--- a/ISSUES.md
+++ b/ISSUES.md
@@ -8,7 +8,7 @@ Ruby Enterprise Edition users may see a `Zlib::GzipFile::Error` while installing
### Rake activation error
-Anyone who has installed the Spork gem may see activation errors while running `rake` directly. This is because installing Spork would [install the newest rake using a mkmf file](https://github.com/timcharper/spork/issues/119). To resolve the issue, update your Gemfile to include either the newest version of Rake or the newest version of Spork (which no longer installs Rake).
+Anyone who has installed the Spork gem may see activation errors while running `rake` directly. This is because old versions of Spork would [install the newest rake using a mkmf file](https://github.com/timcharper/spork/issues/119). To resolve the issue, update the Spork version requirement in your Gemfile to at least `"~>0.8.5"` or `"~>0.9.0.rc8"`.
## Troubleshooting