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.
Upgrade trouble
Added by Jan Wedekind at 2011-07-19 05:22 pm
Hi,
I am trying to upgrade to v2.0 and have a problem with bundler. I am running Ubuntu 10.04.2 LTS.
Upon sudo bundle install, I get
sudo bundle install Fetching source index for http://rubygems.org/ Using rake (0.9.2) Using activesupport (2.3.12) Using rack (1.1.2) Using actionpack (2.3.12) Using actionmailer (2.3.12) Using activerecord (2.3.12) Using activeresource (2.3.12) Using coderay (0.9.8) Using edavis10-object_daddy (0.4.3) Using i18n (0.4.2) Using mocha (0.9.12) Using mysql (2.8.1) Using mysql2 (0.2.11) Installing pg (0.9.0) with native extensions /usr/local/lib/site_ruby/1.8/rubygems/installer.rb:483:in `build_extensions': ERROR: Failed to build gem native extension. (Gem::Installer::ExtensionBuildError) /usr/bin/ruby1.8 extconf.rb checking for pg_config... no checking for libpq-fe.h... no Can't find the 'libpq-fe.h header *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/usr/bin/ruby1.8 --with-pg --without-pg --with-pg-config --without-pg-config --with-pg-dir --without-pg-dir --with-pg-include --without-pg-include=${pg-dir}/include --with-pg-lib --without-pg-lib=${pg-dir}/lib --enable-static-build --disable-static-build Gem files will remain installed in /usr/lib/ruby/gems/1.8/gems/pg-0.9.0 for inspection. Results logged to /usr/lib/ruby/gems/1.8/gems/pg-0.9.0/ext/gem_make.out from /usr/local/lib/site_ruby/1.8/rubygems/installer.rb:446:in `each' from /usr/local/lib/site_ruby/1.8/rubygems/installer.rb:446:in `build_extensions' from /usr/local/lib/site_ruby/1.8/rubygems/installer.rb:198:in `install' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/source.rb:101:in `install' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/rubygems_integration.rb:78:in `preserve_paths' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/source.rb:91:in `install' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/installer.rb:58:in `run' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/rubygems_integration.rb:93:in `with_build_args' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/installer.rb:57:in `run' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/spec_set.rb:12:in `each' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/spec_set.rb:12:in `each' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/installer.rb:49:in `run' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/installer.rb:8:in `install' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/cli.rb:222:in `install' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/vendor/thor/task.rb:22:in `send' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/vendor/thor/task.rb:22:in `run' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/vendor/thor/invocation.rb:118:in `invoke_task' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/vendor/thor.rb:246:in `dispatch' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/vendor/thor/base.rb:389:in `start' from /usr/lib/ruby/gems/1.8/gems/bundler-1.0.15/bin/bundle:13 from /usr/bin/bundle:19:in `load' from /usr/bin/bundle:19
So apparently it fails to install the pg gem. But since I am running chili on MySQL, do I assume correctly that I can exclude pg from bundler?
Thanks!
Jan
Replies (4)
RE: Upgrade trouble - Added by Jan Wedekind at 2011-07-19 05:37 pm
Well nevermind that, should have read more carefully the Wiki page on Bundler
But now my rake task gives me
sudo rake db:migrate RAILS_ENV=production --trace ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment rake aborted! syntax error on line 184, col 2: ` error_can_not_remove_role: "This role is in use and cannot be deleted."' /usr/lib/ruby/1.8/yaml.rb:133:in `load' /usr/lib/ruby/1.8/yaml.rb:133:in `load' /usr/lib/ruby/1.8/yaml.rb:144:in `load_file' /usr/lib/ruby/1.8/yaml.rb:143:in `open' /usr/lib/ruby/1.8/yaml.rb:143:in `load_file' /usr/lib/ruby/gems/1.8/gems/i18n-0.4.2/lib/i18n/backend/base.rb:205:in `load_yml' /usr/lib/ruby/gems/1.8/gems/i18n-0.4.2/lib/i18n/backend/base.rb:191:in `send' /usr/lib/ruby/gems/1.8/gems/i18n-0.4.2/lib/i18n/backend/base.rb:191:in `load_file' /usr/lib/ruby/gems/1.8/gems/i18n-0.4.2/lib/i18n/backend/base.rb:20:in `load_translations' /usr/lib/ruby/gems/1.8/gems/i18n-0.4.2/lib/i18n/backend/base.rb:20:in `each' /usr/lib/ruby/gems/1.8/gems/i18n-0.4.2/lib/i18n/backend/base.rb:20:in `load_translations' /usr/lib/ruby/gems/1.8/gems/i18n-0.4.2/lib/i18n/backend/simple.rb:57:in `init_translations' /usr/lib/ruby/gems/1.8/gems/i18n-0.4.2/lib/i18n/backend/simple.rb:40:in `available_locales' /usr/lib/ruby/gems/1.8/gems/i18n-0.4.2/lib/i18n/config.rb:39:in `available_locales' /usr/lib/ruby/gems/1.8/gems/i18n-0.4.2/lib/i18n.rb:36:in `available_locales' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.12/lib/action_view/template.rb:226:in `valid_locale?' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.12/lib/action_view/template.rb:243:in `parse_extensions' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.12/lib/action_view/template.rb:233:in `split' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.12/lib/action_view/template.rb:118:in `initialize' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.12/lib/action_view/template.rb:92:in `new' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.12/lib/action_view/template.rb:92:in `create_template' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.12/lib/action_view/template.rb:87:in `templates_in_path' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.12/lib/action_view/template.rb:86:in `each' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.12/lib/action_view/template.rb:86:in `templates_in_path' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.12/lib/action_view/template.rb:69:in `load!' /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.12/lib/active_support/dependencies.rb:173:in `to_proc' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.12/lib/action_view/paths.rb:40:in `each' /usr/lib/ruby/gems/1.8/gems/actionpack-2.3.12/lib/action_view/paths.rb:40:in `load!' /usr/lib/ruby/gems/1.8/gems/rails-2.3.12/lib/initializer.rb:402:in `load_view_paths' /usr/lib/ruby/gems/1.8/gems/rails-2.3.12/lib/initializer.rb:194:in `process' /usr/lib/ruby/gems/1.8/gems/rails-2.3.12/lib/initializer.rb:113:in `send' /usr/lib/ruby/gems/1.8/gems/rails-2.3.12/lib/initializer.rb:113:in `run' /var/www/chiliproject/config/environment.rb:33 /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.12/lib/active_support/dependencies.rb:182:in `require' /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.12/lib/active_support/dependencies.rb:182:in `require' /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.12/lib/active_support/dependencies.rb:547:in `new_constants_in' /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.12/lib/active_support/dependencies.rb:182:in `require' /usr/lib/ruby/gems/1.8/gems/rails-2.3.12/lib/tasks/misc.rake:4 /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:205:in `call' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:205:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:200:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:200:in `execute' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:158:in `invoke_with_call_chain' /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:151:in `invoke_with_call_chain' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:176:in `invoke_prerequisites' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:174:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:174:in `invoke_prerequisites' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:157:in `invoke_with_call_chain' /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:151:in `invoke_with_call_chain' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:144:in `invoke' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:112:in `invoke_task' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:90:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:90:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:90:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:129:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:84:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:62:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:129:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:59:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.9.2/bin/rake:32 /usr/bin/rake:19:in `load' /usr/bin/rake:19 Tasks: TOP => db:migrate => environment
Any pointers would be much appreciated ...
Thanks!
Cheers,
Jan
RE: Upgrade trouble - Added by Holger Just at 2011-07-20 07:05 am
Jan Wedekind wrote:
sudo rake db:migrate RAILS_ENV=production --trace ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment rake aborted! syntax error on line 184, col 2: ` error_can_not_remove_role: "This role is in use and cannot be deleted."' /usr/lib/ruby/1.8/yaml.rb:133:in `load' /usr/lib/ruby/1.8/yaml.rb:133:in `load' /usr/lib/ruby/1.8/yaml.rb:144:in `load_file'
This is a funny error because it points to a completely wrong direction :) The error has nothing to do with actual roles or the deletion of those. But it is a syntax error in one of the i18n files in config/locales
, probably en.yml
. The YAML library just failes to load and parse that file because well, a syntax error in that file.
On IRC you noted that you have changed the translations. So make sure you have the correct syntax. Note: leading whitespace is important and is part of the syntax!
Hope that helps,
Holger
RE: Upgrade trouble - Added by Jan Wedekind at 2011-07-20 11:09 am
Hi Holger,
Yes, that was my mistake by keeping the old en.yml.
But my current problems are way deeper. I couldn't upgrade because the rake db:migrate would not finish with the error
rake aborted! An error has occurred, all later migrations canceled: uninitialized constant Contact
which is arguably related to some rests of the Contacts plugin, which I thought I had got rid off but apparently not completely.
Then also, I got some passenger error and app wouldn't load because of a missing gem. I used bundler which told me everything was fine.
Anyway: I reverted everything to the previous installation (v1.4.0), i.e., dropped the db, switched to the v1.4.0 branch, re-imported the backup and things seemed to work. But now notifications don't work anymore and give me a pretty weird error on the admin screen
An error occurred while sending mail (555 5.5.2 Syntax error. fx12sm91736wbb.25 )
There is nothing in production.log that would help. Running
sudo rake redmine:email:test[jwedekind] RAILS_ENV=production --trace
runs just fine and tells me "An email was sent to ..." but I don't receive anything.
Here is a gem list - I suspect that in all this process I screwed up gem dependencies or something. I've never touched the configuration.yml, which only contains a simple Gmail smtp configuration anyway.
gem list *** LOCAL GEMS *** abstract (1.0.0) actionmailer (2.3.5) actionpack (2.3.12, 2.3.11, 2.3.8, 2.3.5) activerecord (2.3.12, 2.3.11, 2.3.8, 2.3.5) activeresource (2.3.12, 2.3.11, 2.3.8, 2.3.5) activesupport (3.0.7, 2.3.12, 2.3.11, 2.3.8, 2.3.5) acts-as-taggable-on (2.0.6) arel (2.1.0, 2.0.9) builder (3.0.0, 2.1.2) bundler (1.0.15, 1.0.13) coderay (0.9.8) edavis10-object_daddy (0.4.3) erubis (2.7.0, 2.6.6) fastercsv (1.5.4) gcal4ruby (0.5.5) gdata4ruby (0.1.5) i18n (0.4.2) mail (2.3.0, 2.2.19) mime-types (1.16) mocha (0.9.12) mysql (2.8.1) mysql2 (0.2.11) polyglot (0.3.1) rack (1.1.2, 1.0.1) rack-mount (0.7.2, 0.6.14) rack-test (0.6.0, 0.5.7) rails (2.3.5) rake (0.8.7) rdoc (3.8) rmagick (2.13.1, 1.15.17) ruby-openid (2.1.8) rubygems-update (1.8.1) rubytree (0.5.3) shoulda (2.10.3) thor (0.14.6) treetop (1.4.9) tzinfo (0.3.27) will_paginate (2.3.15)
Any pointers would really help me out a lot here.
Thanks a million,
Jan
RE: Upgrade trouble - Added by Jan Wedekind at 2011-07-20 12:53 pm
The mail sending issue was resolved on IRC, apparently it is a Rails 2.3.5 bug. The sender email address must be entered as email alone, variations as "Name Bla" <email@me.com> produced this error.
As for the upgrade to CP 2.0 - I will now dig first a bit deeper, make a fresh test install and try to migrate the db there.
Thanks for all your help.
(1-4/4)