Bug 586709

Summary:	please provide a method to get the transaction stdout
Product:	[Fedora] Fedora	Reporter:	Richard Hughes <rhughes>
Component:	yum	Assignee:	Seth Vidal <skvidal>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	ffesti, james.antill, maxamillion, pmatilai, tim.lauridsen
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:	2010-04-28 08:58:22 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 Richard Hughes 2010-04-28 08:33:08 UTC

Description of problem:

In PackageKit we currently swallow all the stdout from the yum transaction and it's not available for the user. This is bad. It would be really useful to get the output of some pre and post scriptlets (for instance from the vmware package) and show them as messages like we do other non-critical things.

Additional info:

I really don't need stuff like "kernel ################################# [85/102]" but the scriptlet output like "database will be rebuilt on next-boot" would be useful. Thanks.

Comment 1 Tim Lauridsen 2010-04-28 08:58:22 UTC

You have to checkout the the scriptout function in the RPMCallback class.

This is how yum cli does it.

http://yum.baseurl.org/download/docs/yum-api/3.2.26/output-pysrc.html#YumCliRPMCallBack.scriptout

AFAIK the pk yum plugin has it own RPMCallback, so you just have to the store the scriptout messages and send them to the frontend.