Bug 11475 - redmine does not start
Summary: redmine does not start
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-15 09:08 CEST by José Jorge
Modified: 2015-03-31 16:05 CEST (History)
0 users

See Also:
Source RPM: redmine
CVE:
Status comment:


Attachments

Description José Jorge 2013-10-15 09:08:06 CEST
redmine does not start because it's config file was not updated for Apache 2.4.
Itrid to see what is needed :

mv /etc/httpd/conf.d/redmine.conf /etc/httpd/conf/vhosts.d/

edit redmine.conf, replacing allow and deny lines with :

Require all granted

Still, it fails with :

cannot load such file -- rubygems/spec_fetcher

Reproducible: 

Steps to Reproduce:
Comment 1 José Jorge 2013-10-15 11:02:27 CEST
Workaround for spec_fetcher :

sudo ln -s /usr/share/ruby/gems/rubygems /usr/share/ruby/gems/gems/bundler-1.2.1/lib/
Comment 2 José Jorge 2013-10-15 11:04:13 CEST
Then :

Could not find gem 'mocha (~> 0.13.3) ruby' in the gems available on this machine.

Now is it a Requires to add to redmine or to another gem?
Comment 3 José Jorge 2013-10-15 11:41:53 CEST
A few more gems missing to do "rake generate_secret_token" :

- ruby-jquery-rails = 2.0.2 (none provided)
- ruby-coderay
- ruby-fastercsv
- ruby-builder = 3.0.0 (3.0.4 provided)
Comment 4 Marja Van Waes 2015-03-31 16:05:51 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.