Bug 683415

Summary: perl-Net-Telnet package is not available in rhel 6 workstation channel
Product: Red Hat Enterprise Linux 6 Reporter: dipu <ddevaraj>
Component: distributionAssignee: Dennis Gregorovic <dgregor>
Status: CLOSED WONTFIX QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0CC: dgregor, jwest, syeghiay, yjog
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-18 18:09:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description dipu 2011-03-09 11:36:12 UTC
Description of problem:
The perl-Net-Telnet used to be available on the standard rhel workstation channel in rhel5(rhel-x86_64-client-5). In rhel6 is the package is not availalbe in the standard channel rhel-x86_64-workstation-6(its only available in RHEL Server Resilient Storage and RHEL Server High Availability channels).

Is there any particular reason for moving it from the rhel 6 workstation channel. One of the customer is very concerned about it and he is asking for the reason for the move.

Here is the customer update
----------------------------------------------

I seem to be missing the logic in placing perl-Net-Telnet in a the GFS channel.

There is nothing GFS specific to perl-Net-Telnet.  quoted from the perl-Net-Telnet spec file description:

Net::Telnet allows you to make client connections to a TCP port and do
network I/O, especially to a port using the TELNET protocol. Simple I/O
methods such as print, get, and getline are provided. More sophisticated
interactive features are provided because connecting to a TELNET port
ultimately means communicating with a program designed for human interaction.
These interactive features include the ability to specify a time-out and to
wait for patterns to appear in the input stream, such as the prompt from a
Shell.

Since it is a generic perl module package is not a GFS specific software package, (and is only depended on by GFS specific software) why is this package in the GFS channel?  If this package was in the base channel, when installing GFS specific RPMs, (or any other dependent software package) yum will auto resolve the dependencies and install perl-Net-Telnet as needed.

Note that in RHEL5, this package was maintained in the RHEL5 base channels which worked great.

There are many non-RH, non-GFS software packages that could (and do) depend on perl-Net-Telnet.  Because perl-Net-Telnet is in the incorrect channel breaks yum dependencies for non GFS packages on RHEL6.  By placing this in a premium channel, this is now forcing customers to then have to maintain this package out of band from RHN and duplicate work for no reason.


Version-Release number of selected component (if applicable):
 Red Hat Enterprise Linux 6

How reproducible:
perl-Net-Telnet package is not available in standard rhel-x86_64-workstation-6 channel 

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 RHEL Program Management 2011-03-09 11:57:58 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.