Bug 754413

Summary:	RFE: suppress "yum check" output
Product:	[Fedora] Fedora	Reporter:	Ian Collier <imc>
Component:	yum	Assignee:	Fedora Packaging Toolset Team <packaging-team>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	17	CC:	ffesti, james.antill, maxamillion, pmatilai, tla, zpavlas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-01-21 17:23:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Ian Collier 2011-11-16 12:28:54 UTC

So I've upgraded a Fedora 15 machine to 16 using the bootable media, and because of the number of extra packages that were installed under F15, there are now a ton of dependency problems.  This is expected, of course, and isn't a problem - I'm generally very good at solving dependencies.

The problem is that yum insists on telling me what all these broken dependencies are every time I use it.  So, suppose I want to know what's wrong with the foobar package and I type something like "yum update foorbar".  It gives me the real error message telling me why it couldn't update foobar, and then says "** Found 336 pre-existing rpmdb problem(s), 'yum check' output follows:" and now the true error has scrolled into oblivion.

I very much need it not to do that.  I've searched the man page for possible flags to turn this off, but didn't find anything, and even "-e 0 -d 0" still produces the output.

Comment 1 Fedora Admin XMLRPC Client 2012-04-27 15:25:40 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Fedora End Of Life 2013-01-16 16:46:37 UTC

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Ian Collier 2013-01-17 10:40:17 UTC

F17 still bugs me with this...

Comment 4 James Antill 2013-01-21 17:23:58 UTC

 This should be a very temporary problem, and having a way to turn it off will just encourage people to have it do that all the time. We already get enough bug reports asking why yum failed to do XYZ when looking at the "yum check" output says "XYZ is going to be a problem".