Redmine devel r1623 and above is compatible with Rails 2.1.
But Redmine 0.7.x releases are not. Please freeze your rails to 2.0.2 version:$ rake rails:freeze:edge TAG=rel_2-0-2
Make sure Ruby on Rails is properly installed on your machine.
You have to specify the socket location in config/database.yml
.
See http://dev.rubyonrails.org/ticket/200.
You're running Rails 1.1.x but Redmine requires 1.2.6.
Upgrade Rails (if you're using gem package system, run the command gem update
as root/administrator).
There's a bug in ruby/mysql adapter < 2.7.3 that leads to loose the database connection. Please update your adapter.
You can see thread at: http://rubyforge.org/forum/message.php?msg_id=25951.
Redmine 0.6.3 is Rails 2.0 compatible, but prior versions are not.
The best solution is to upgrade Redmine to the latest version. But if you really want to use Redmine 0.6.0 on a box running Rails 2.0, please freeze your Rails version for Redmine (it won't affect your other Rails applications) by typing this command from your Redmine directory:
rake rails:freeze:edge TAG=rel_1-2-6
Don't forget to restart your server.
Once you've created a new issue status, you need to include it in the workflow.
Say you have created a status named 'In progress' and you want the developers to be able to change bugs from 'New' to 'In progress'.
Go to "Admin -> Issue tracking -> Workflow", select 'Bug' and 'Developer' then click edit.
You now see all the transitions allowed for developers on bugs. Check the 'New' -> 'In progress' checkbox and save.
See Workflow setup.
Using Issue #100 as the one you set the relationship and Issue #101 as the "related to"
By default, Redmine fetches the new commits from the repository only when you browse it.
If you want the commits to be retrieved periodically by Redmine in the background for all your repositories, uncheck 'Autofetch commits' setting and add a cron that runs (with appropriate environment):
ruby script/runner "Repository.fetch_changesets" -e production
If you're accessing the repository over HTTPS:
The initial import of a subversion repository over https requires that the ssl certificate fingerprint be manually validated and stored in a config-dir accessible by the user running the web server. It is recommended that a directory local to the redmine application root be provided, either as a default (./svn/.subversion) or as a provided parameter in the repository settings for subversion.
The work around for the certificate acceptance issue is to manually checkout anything from the svn server specifying the local config-dir and accepting the certificate permanently.
Example:
$ svn --config-dir ./svn/.subversion co https://svn.mydomain.com/project/trunk delete-me Error validating server certificate for 'https://svn.mydomain.com:443': - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! - The certificate hostname does not match. - The certificate has expired. Certificate information: - Hostname: svn.mydomain.com - Valid: from Apr 8 12:00:00 2006 GMT until Sep 24 12:00:00 2010 GMT - Issuer: mydomain.com, vrsource.org, Geneva, UN - Fingerprint: 01:27:d9:6a:b8:db:63:f3:24:e3:41:c8:15:0a:f8:93:f6:7c:0f:11 (R)eject, accept (t)emporarily or accept (p)ermanently? p
There's a bug in rexml 3.1.7 provided with ruby 1.8.6.
In ruby/1.8/rexml/document.rb
(line 186), change: if transitive
to if trans
then restart the app.
See http://www.germane-software.com/projects/rexml/ticket/115 for details.
You have to configure email notification, or desactivate it. Please turn off email notification feature if you don't use it. In config/environment.rb replace the line
config.action_mailer.perform_deliveries = true
to
config.action_mailer.perform_deliveries = false
and restart redmine.
Rails built-in time zone implementation doesn't handle DST. You have to install TZInfo.
To do so, run the following from your Redmine directory:
ruby script/plugin install tzinfo_timezone