Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 101563

Summary: pam src rpm BuildRequires flex
Product: [Retired] Red Hat Linux Beta Reporter: Leonard den Ottolander <leonard-rh-bugzilla>
Component: pamAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED RAWHIDE QA Contact: Jay Turner <jturner>
Severity: medium Docs Contact:
Priority: medium    
Version: beta1CC: leonard-rh-bugzilla, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-01-08 05:01:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 100644    

Description Leonard den Ottolander 2003-08-03 23:25:39 UTC
Description of problem:

The pam src is missing a BuildRequires for flex.


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

pam-0.77-2.src.rpm


How reproducible:

# rpm -e flex
# rpmbuild -ba pam.spec
Build fails
# rpm -i flex-2.5.4a-30.i386.rpm
# rpm -ba pam.spec
Build succeeds

Resolution:

Add a BuildRequires for flex to the SPEC file.

Comment 1 Leonard den Ottolander 2003-09-11 00:32:10 UTC
pam-0.77.3 still BuildRequires flex.


Comment 2 Nalin Dahyabhai 2003-10-23 18:18:43 UTC
Fixing in 0.77-15.

Comment 3 Leonard den Ottolander 2003-12-31 13:28:04 UTC
The My Bugs page tells me:

Open Issues: Retest (you reported this issue, it is now resolved and
you should verify it)

101563  Red Hat Linux Beta  MODIFIED  normal  pam src rpm
BuildRequires flex

As flex is added as a BuildPrereq to the SPEC file I see no need not
to close this bug. Or am I expected to close the bug myself?


Comment 4 Nalin Dahyabhai 2004-01-08 05:01:37 UTC
MODIFIED typically means "waiting for independent verification", at
which point AFAIK anyone can close it.  Since you say it's fixed, I'll
close it.  Thanks!