diff options
| author | Louise Crow <louise.crow@gmail.com> | 2013-04-30 15:32:39 +0100 |
|---|---|---|
| committer | Louise Crow <louise.crow@gmail.com> | 2013-04-30 15:32:39 +0100 |
| commit | 67c1c920e772dabab5c7a8ed2582bebbe890ac34 (patch) | |
| tree | 75eea5e046540cbd3d6ae251141f17d8da51620e | |
| parent | 1ea62dfd30f44e2bbbb21b57bfa00d6e7858a427 (diff) | |
Re-remove text removed in e0db6cf956e2270413143017baa7c1472b2e95f2 and reinstated in subsequent merge.
| -rw-r--r-- | doc/INSTALL.md | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/doc/INSTALL.md b/doc/INSTALL.md index 278aee370..09bc8fd43 100644 --- a/doc/INSTALL.md +++ b/doc/INSTALL.md @@ -501,19 +501,6 @@ various other things that can be automated for deployment. [https://github.com/mysociety/alaveteli/issues/128#issuecomment-1814845](this issue followup) for further discussion. -* **I'm getting lots of `SourceIndex.new(hash) is deprecated` errors when running the tests** - - The latest versions of rubygems contain a large number of noisy - deprecation warnings that you can't turn off individually. Rails - 2.x isn't under active development so isn't going to get fixed (in - the sense of using a non-deprecated API). So the only vaguely - sensible way to avoid this noisy output is to downgrade rubygems. - - For example, you might do this by uninstalling your - system-packaged rubygems, and then installing the latest rubygems - from source, and finally executing `sudo gem update --system - 1.6.2`. - * **I'm seeing `rake: command not found` when running the post install script The script uses `rake`. |