Bug 164289

Summary:	rpmbuild fails - popt not updated
Product:	[Fedora] Fedora	Reporter:	Sammy <umar>
Component:	rpm	Assignee:	Paul Nasrat <nobody+pnasrat>
Status:	CLOSED RAWHIDE	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	twaugh
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:	4.4.2-3	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-10-25 22:13:59 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:

Description Sammy 2005-07-26 16:26:54 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.4; Linux; X11; en_US) KHTML/3.4.2 (like Gecko)

Description of problem:
rpmbuild failed just before writing rpm's with the message: 
 
getOutputFrom(): Broken pipe 
 
ALSO: popt versioning went down so popt package was not updated by yum. I am not 
sure if these are related or not. 

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


How reproducible:
Didn't try

Steps to Reproduce:
1. update using yum 
2. popt not updated 
3. 
   

Additional info:

Comment 1 Paul Nasrat 2005-07-26 16:48:26 UTC

popt versioning unrelated, will be fixed in next rebuild.

Can you add to ~/.rpmmacros and try another build

%__perl_provides       /usr/lib/rpm/perl.prov
%__perl_requires       /usr/lib/rpm/perl.req

Comment 2 Robert Scheck 2005-07-27 09:54:21 UTC

[Off-Bugzilla] Paul, requires for popt is 1.10.1 anyway (rpm-4.4.2-2) - and 
wrong! Please change to 1.10.2, that the right popt version is always required 
by rpm...

Comment 3 Paul Nasrat 2005-07-27 12:13:06 UTC

Yup picked that up this morning - apologies for oversight. 4.4.2-3 building now
should be in next rawhide.

Comment 4 Jeff Johnson 2005-08-27 02:00:05 UTC

popt version is not the bug, either (or any recent) popt will do.

getOutputFrom() is the bug here.