Project

General

Profile

Actions

Feature #19477

open

Custom EPEL product is not integrated seamlessly

Added by Lukas Zapletal almost 7 years ago. Updated over 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Subscriptions
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Hey,

when you add RHEL product, Satellite automatically detect RHEL version and add appropriate version into redhat.repo, but when using EPEL custom product, this is not possible and users must create custom activation keys like ak-epel-6 and ak-epel-7 to differentiate between versions.

It would be nice to offer them some level of integration so this is more seamless. Most of RHEL users use EPEL repositories.

Actions #1

Updated by Justin Sherrill almost 7 years ago

  • translation missing: en.field_release set to 114
Actions

Also available in: Atom PDF