Bug 370911
Summary: | yum-cron sends useless messages if yum-metadata-parser is installed | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Ville Skyttä <ville.skytta> |
Component: | yum | Assignee: | Jeff Sheltren <sheltren> |
Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | el5 | CC: | ahabig |
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: | 2007-12-06 14:12:39 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
Ville Skyttä
2007-11-08 08:39:51 UTC
yum-cron is already invoking yum with "-e 0 -d 0", which is the minimum possible verbosity level. The "Message:" output yum is giving strikes me as an informational level of message that yum shouldn't be sending to stdout at verbosity level 0. yum-cron cannot squelch stdout entirely, since we're asking it to output a list of needed updates. It also cannot ignore stderr, since we'd like to know when something fundamental is broken. So, it looks like this bug is really in yum-metadata-parser - it has an informational message which is not obeying the overall yum verbosity rules. Reassigning the bug to yum, as yum-metadata-parser isn't a bugzilla component of its own. Alec, yum in el5 is not maintained in EPEL, it is part of RHEL/CentOS proper. Ville, if you agree with Alec's assessment, I think re-opening this as a CentOS bug would be appropriate. Well, the EPEL yum-cron upgrades the CentOS one so chances are that we'll be seeing a ping pong effect if this is reported there. It's not a yum-cron issue, it's a yum one, likely upstream anyway regardless of the distribution. Part of yum simply has a debugging statement that's not listening to the verbosity flags, yum-cron makes us of those flags so notices the bug. The latest yum-cron for EL5 now comes from CentOS, so I'm moving the issue there. http://bugs.centos.org/view.php?id=2514 |