ChiliProject is not maintained anymore. Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.
ruby-debug19 breaks on Ruby 1.9.3 (Bug #839)
In the test group, we inclue
ruby-debug19. This currently breaks on Ruby 1.9.3. I'd like to fix that for the final 3.0.0 release.
- We remove the
ruby-debugdependencies from the Gemfile completely and expect users who really need this to include it into their
- We try some workaround to make it work on 1.9.3
- We don't care.
Right now, I'm in favor of the first variant. Can I please hear a Yay or Nay for that in the next seven days?
[#839] Remove ruby-debug dependency.
It completely breaks on Ruby 1.9.3-p0. This is a stopper for people installing all groups. For the rest it is rarely used at all. Developers and testers requiring it can include it into their Gemfile.local
Please take ruby-debug19 out of the main Gemfile. It is only a development tool not a runtime dependency. Whatâ€™s more, currently the Gemfile.lock points to pre-release versions of linecache and ruby-debug-base19 that have to be manually tracked down and installed, even when on ruby 1.9.2
Gerrit Kaiser wrote:
It is only a development tool not a runtime dependency.
That's why it is the
test group which is not expected to be installed on production installs. See Bundler fr more information.
Whatâ€™s more, currently the Gemfile.lock points to pre-release versions of linecache and ruby-debug-base19 that have to be manually tracked down and installed, even when on ruby 1.9.2
We don't ship a
Gemfile.lock. That is generated by your local bundler. And on my systems, a new install on Ruby 1.9.2 with the test group included succeeds. It just breaks on 1.9.3 because of the incompatibility.
This is a patch from my Redmine Rails3 branch.
- File ruby-debug19.diff added
- Status changed from Closed to Ready for review
Toshi, thanks for the patch. However, I came to the conclusion that requiring ruby-debeg in the core is more trouble than it's worth. Having to maintain a row of dependencies of pre-release gems doesn't feel very stable to me. And as I said in the commit message: it's rarely used by anyone and those people who know they need it can include it into their
Thus, I feel comfortable now to not include the dependency at all.
- Status changed from Ready for review to Closed