Project

General

Profile

Actions

Defect #30074

closed

Puma shouldn't be included in the Gemfile

Added by Pavel Rosický over 5 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Gems support
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

right now it isn't possible to use a different Puma version or define it for a production environment because there's a conflict

https://github.com/redmine/redmine/blob/master/Gemfile#L91

group :test do
  # For running system tests
  gem 'puma', '~> 3.7'
end

Gemfile.local

source 'https://rubygems.org'

group :production do
  gem "puma" 
end

[!] There was an error parsing `Gemfile`:
[!] There was an error parsing `Gemfile.local`: You cannot specify the same gem twice with different version requirements.
You specified: puma (~> 3.7) and puma (>= 0). Bundler cannot continue.

 #  Gemfile.local:4
 #  -------------------------------------------
 #
 >
 #  source 'https://rubygems.org'
 #  -------------------------------------------
. Bundler cannot continue.

 #  from Gemfile.local:4
 #  -------------------------------------------
 #    eval_gemfile file
 >  end
 #  source 'https://rubygems.org'
 #  -------------------------------------------
Actions #1

Updated by Pavel Rosický over 5 years ago

IMO, your CI should add Puma to Gemfile.local in a before_script or use Capybara.server = :webrick if Puma isn't available

Actions #2

Updated by Go MAEDA over 4 years ago

The version of puma is not fixed after r19338.

Actions #3

Updated by Go MAEDA over 3 years ago

  • Status changed from New to Closed
  • Resolution set to Fixed

Fixed by r19338.

Actions

Also available in: Atom PDF