Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 229671 - No record of rpm warnings (rpmnew etc.) when updating with pup
No record of rpm warnings (rpmnew etc.) when updating with pup
Product: Fedora
Classification: Fedora
Component: pirut (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-02-22 12:32 EST by Kevin R. Page
Modified: 2014-01-21 17:57 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-09-12 14:24:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kevin R. Page 2007-02-22 12:32:50 EST
Description of problem:
The brave new world of pup and puplet is generally great, however, when using
pup to update I'm no longer informed of rpm warnings e.g. rpmnew/rpmsave files.

On machines I update myself, it would be useful for the pup UI to be able to
pass on these warnings.

On machines updated by less experienced users, which I keep an eye on via
logwatch - and if the pup UI is being kept intentionally simple - then it would
be useful for these warnings to be recorded in yum.log.

If so, perhaps this would be better filed against yum? I'll refile if this is
the consensus.

I notice that if I run pup from a terminal, the rpm warnings are shown there -
so I guess they may be coming from rpm/librpm and going to stderr rather than a
logging interface? So perhaps this goes right down to the rpm API?

Version-Release number of selected component (if applicable):
Comment 1 Seth Vidal 2007-08-03 15:44:18 EDT
reassigning to pirut - though this seems more like rpm.
Comment 2 Jeremy Katz 2007-09-12 14:24:46 EDT
Added in CVS for pirut (1.3.18 or so); going to try to push down to yum, though

Note You need to log in before you can comment on or make changes to this bug.