Project

General

Profile

Actions

Bug #12215

closed

Debian package build is failing with "`ruby_22` is not a valid platform."

Added by Anonymous almost 9 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Tests
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Jenkins output:

17:38:21 /usr/bin/bundle package
17:38:21 `ruby_22` is not a valid platform. The available options are: [:ruby, :ruby_18,
17:38:21 :ruby_19, :ruby_20, :ruby_21, :mri, :mri_18, :mri_19, :mri_20, :mri_21, :rbx,
17:38:21 :jruby, :jruby_18, :jruby_19, :mswin, :mingw, :mingw_18, :mingw_19, :mingw_20,
17:38:21 :mingw_21, :x64_mingw, :x64_mingw_20, :x64_mingw_21]
17:38:21 debian/rules:11: recipe for target 'build/foreman' failed


Related issues 2 (0 open2 closed)

Related to Foreman - Bug #11016: missing gem in test.rb under ruby 2.2.0Closed07/05/2015Actions
Related to Smart Proxy - Bug #12217: `ruby_21` is not a valid platform` with older versions of BundlerClosed10/20/2015Actions
Actions #1

Updated by Anonymous almost 9 years ago

  • Related to Bug #11016: missing gem in test.rb under ruby 2.2.0 added
Actions #2

Updated by The Foreman Bot almost 9 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2841 added
  • Pull request deleted ()
Actions #3

Updated by Dominic Cleal almost 9 years ago

  • Related to Bug #12217: `ruby_21` is not a valid platform` with older versions of Bundler added
Actions #4

Updated by Dominic Cleal almost 9 years ago

  • Translation missing: en.field_release set to 71
Actions #5

Updated by Anonymous almost 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF