Bug 13259 - Running the instructions from the README.urpmi of chiliproject gives an error
Summary: Running the instructions from the README.urpmi of chiliproject gives an error
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
Keywords: Triaged
Depends on:
Reported: 2014-04-24 12:21 CEST by Shlomi Fish
Modified: 2015-09-21 14:06 CEST (History)
2 users (show)

See Also:
Source RPM: chiliproject
Status comment:


Description Shlomi Fish 2014-04-24 12:21:20 CEST
For more information, see:


Hi all,

running the instructions from the README.urpmi gives me this error in the "rake generate_session_store":

rake aborted!
Bundler couldn't find some gems. Did you run `bundle install`?
/var/www/chiliproject/config/preinitializer.rb:32:in `rescue in <top (required)>'
/var/www/chiliproject/config/preinitializer.rb:27:in `<top (required)>'
/var/www/chiliproject/config/boot.rb:42:in `load'
/var/www/chiliproject/config/boot.rb:42:in `preinitialize'
/var/www/chiliproject/config/boot.rb:24:in `boot!'
/var/www/chiliproject/config/boot.rb:137:in `<top (required)>'
/var/www/chiliproject/Rakefile:4:in `<top (required)>'
(See full trace by running task with --trace)


-- Shlomi Fish

Version-Release number of selected component (if applicable):

Mageia 4. (Possibly also Cauldron).

How reproducible:



Steps to Reproduce:
Manuel Hiebel 2014-05-01 20:25:16 CEST

Keywords: (none) => Triaged
CC: (none) => thomas
Assignee: bugsquad => shikamaru

Comment 1 Rémy CLOUARD (shikamaru) 2014-05-05 08:39:35 CEST
Yes, in mga1 the package was well tested and running as intended. Since rails3 bundler is mandatory in every rails app. It needs a Gemfile.lock file, but I don't know a sane way to package it. The script in %post could run bundle install but that would pull gems from rubygems.org if some of them are missing. Bundle install --local would circumvent the issue, but doing it this way would expect every gem in the Gemfile, even those in the development or testing group. This is old  and I cannot check right now, but last time I checked you couldn't use --local in conjunction with --without-test or the equivalent. I thought the package was dropped BTW, was it brought back into life ?

Comment 2 Marja Van Waes 2015-04-21 18:43:27 CEST
Assigning back to Bug Squad, since shikamaru went MIA

CC: (none) => marja11
Assignee: shikamaru => bugsquad

Comment 3 Samuel Verschelde 2015-09-21 13:20:15 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 4 Shlomi Fish 2015-09-21 14:06:14 CEST
closing as old because chiliproject is no longer in Mageia.

Resolution: (none) => OLD

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