Bug 652659 - pexpect is not found in RHEL6-repository
Summary: pexpect is not found in RHEL6-repository
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: redhat-release-server
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Andrew Thomas
QA Contact: Release Test Team
: 643299 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2010-11-12 13:35 UTC by Gerrit Slomma
Modified: 2018-11-14 16:39 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2011-05-19 12:55:22 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2011:0540 0 normal SHIPPED_LIVE redhat-release enhancement update for Red Hat Enterprise Linux 6.1 2011-05-18 17:44:50 UTC

Description Gerrit Slomma 2010-11-12 13:35:21 UTC
Description of problem:

pexpect is (still) not found in RHEL6-repository.

Version-Release number of selected component (if applicable):


How reproducible:

Everytime via rhn-package-search or via yum list pexpect with mounted RHEL6-server install-cd

Steps to Reproduce:
1. search for pexpect in rhn, getting only RHEL4 and RHEL5-packages

> https://rhn.redhat.com/network/software/packages/name_overview.pxt?package_name=pexpect&archIdList=520&archLabelList=x86_64&search_subscribed_channels=

2. browse for it via channel-package-browse, not there either
3. look into Packages-directory on the RHEL6-server install-cd, it is there!
4. source-package is there too!
> http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/os/SRPMS/pexpect-2.3-6.el6.src.rpm
Actual results:

No pexpect found

Expected results:

pexpect found

Additional info:

I hinted to this problem earlier in BUG 619566 for RHEL6-beta - but no one took me for real!

> https://bugzilla.redhat.com/show_bug.cgi?id=619566

Comment 2 Jan Friesse 2010-11-15 08:12:46 UTC
Pexpect is available in High Availability repository. Server repository itself doesn't contain it.

Closing bug as NOTABUG, because pexpect should be used only by fence-agents package.

Comment 3 Gerrit Slomma 2010-11-15 16:08:42 UTC
yumex from EPEL v6 has pexpect as a dependency, how to install this on a normal Server/Desktop?

Comment 4 Jan Friesse 2010-11-16 12:07:57 UTC
I'm changing component to distribution, because bug is not in pexpect but in distribution.

Main problem seems to be, that pexpect is only used by fence-agents package and this is why it is only in HA. yumex is not supported in RHEL, but there may be chance to use it on server by customers.

Comment 5 Siddharth Nagar 2010-11-17 18:27:42 UTC
*** Bug 643299 has been marked as a duplicate of this bug. ***

Comment 12 Mark Lamourine 2010-12-23 15:27:29 UTC
As a frequent python coder, I think pexpect should pretty certainly be included in the server repository.  Of course this is only my opinion.  What are the criteria for inclusion other than direct requirement by something else that is included?

Comment 15 Gerrit Slomma 2011-01-14 08:43:56 UTC
There seems to be an pexpect-2.3-6.el6.noarch.rpm on the RHEL6-Server-Install-CD, however it is not found in RHN?

Comment 16 Dennis Gregorovic 2011-01-14 19:33:08 UTC
(In reply to comment #15)
> There seems to be an pexpect-2.3-6.el6.noarch.rpm on the
> RHEL6-Server-Install-CD, however it is not found in RHN?

It's in RHN, but not in the base channel.  In RHEL 6.0, pexpect is only available through the High Availability channel.  The goal of this package is to move the package into the base channel.

Comment 19 Alexander Todorov 2011-02-07 12:38:28 UTC
# pwd

# find -name "pexpect*" | sort

For Server and Workstation variants pexpect is on the system-admin-tools group in comps.xml. For the other variants it is in the optional repo. Moving to VERIFIED.

Comment 20 errata-xmlrpc 2011-05-19 12:55:22 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.