Project

General

Profile

Bug #16817

Don't use generic name in gemspec for gem name

Added by Marek Hulán over 6 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Marek Hulán
Category:
-
Target version:
1.5.0
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman_discovery/pull/308
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Getting following when starting Foreman with openscap plugin

foreman_discovery.gemspec:6: warning: already initialized constant GEM_NAME

Related issues

Copied from OpenSCAP - Bug #16816: Don't use generic name in gemspec for gem nameClosed2016-10-06

Associated revisions

Revision 953b73dc (diff)
Added by Marek Hulán over 6 years ago

Fixes #16817 - avoid conflicting constant name

History

#1 Updated by Marek Hulán over 6 years ago

  • Copied from Bug #16816: Don't use generic name in gemspec for gem name added

#2 Updated by The Foreman Bot over 6 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_discovery/pull/308 added

#3 Updated by Anonymous over 6 years ago

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

Also available in: Atom PDF