Bug 586709 - please provide a method to get the transaction stdout
Summary: please provide a method to get the transaction stdout
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: yum   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-28 08:33 UTC by Richard Hughes
Modified: 2014-01-21 23:14 UTC (History)
5 users (show)

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: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.