Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1688336

Summary: Packaging `expect` binary in `whois-mkpasswd` package breaks testing
Product: [Fedora] Fedora Reporter: Siteshwar Vashisht <svashisht>
Component: whoisAssignee: Petr Pisar <ppisar>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: ppisar
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-14 08:39:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Siteshwar Vashisht 2019-03-13 15:01:42 UTC
Description of problem:
Some packages uses `expect` utility to test commandline tools. Packaging `expect` in whois package breaks testing of such packages. For e.g. It broke testing of ksh package in upstream

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

How reproducible:

Steps to Reproduce:
1. Try to install `expect` when `whois-mkpasswd` package is installed.

Actual results:
Problem: problem with installed package whois-mkpasswd-5.4.1-1.fc29.x86_64
  - package whois-mkpasswd-5.4.1-1.fc29.x86_64 conflicts with expect provided by expect-5.45.4-5.fc29.x86_64
  - conflicting requests

Expected results:
Installing `expect` should work.

Additional info:
It was probably broken by

We are using f29 docker image to do our builds and `whois-mkpasswd` is installed by default on these images.

Comment 1 Petr Pisar 2019-03-14 08:39:48 UTC

*** This bug has been marked as a duplicate of bug 1687870 ***