Project

General

Profile

Actions
Copy link

Bug #16816

closed

Don't use generic name in gemspec for gem name

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

Status:
Closed
Priority:
Normal
Assignee:
Marek Hulán
Target version:
foreman_openscap 0.6.3
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman_openscap/pull/222
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Getting following when starting Foreman with openscap plugin

foreman_openscap.gemspec:3: warning: already initialized constant GEM_NAME

Related issues 1 (0 open — 1 closed)

Copied to Discovery - Bug #16817: Don't use generic name in gemspec for gem nameClosedMarek Hulán10/06/2016Actions
Actions
Copy link
 #1

Updated by The Foreman Bot over 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_openscap/pull/222 added
Actions
Copy link
 #2

Updated by Marek Hulán over 7 years ago

  • Copied to Bug #16817: Don't use generic name in gemspec for gem name added
Actions
Copy link
 #3

Updated by Marek Hulán over 7 years ago

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

Also available in: Atom PDF