Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 80774

Summary:	rpm.errorSetCallback doesn't handle restoration of python threads
Product:	[Retired] Red Hat Raw Hide	Reporter:	Jeremy Katz <katzj>
Component:	rpm	Assignee:	Jeff Johnson <jbj>
Status:	CLOSED RAWHIDE	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.0
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-01-29 04:19:46 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:	79578, 80751

Description Jeremy Katz 2002-12-31 04:52:15 UTC

As we've previously discussed -- just filing here for tracking purposes

rpm.errorSetCallback doesn't handle restoring python threads correctly so can
get called into from unexpected contexts.  I'm fine with just replacing the
interface with passing an open file descriptor down similar to ts.scriptFd

Comment 1 Jeff Johnson 2003-01-13 15:37:09 UTC

Fixed in rpm-4.2-0.56.

Comment 2 Jeremy Katz 2003-01-23 00:57:35 UTC

As discussed, the fix doesn't seem to work

Comment 3 Jeremy Katz 2003-01-29 04:19:46 UTC

Have rpm.setLogFile now which looks reasonable to me