Bug 750859

Summary: yum outputs Setting up messages even with -d 0/1
Product: [Fedora] Fedora Reporter: Orion Poplawski <orion>
Component: yumAssignee: Jan ONDREJ <ondrejj>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 16CC: coffeeman, ffesti, iny, james.antill, maxamillion, ondrejj, paskalis, pmatilai, tla, zpavlas
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: yum-3.4.3-7.fc16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-12 22:03:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
doneCommand(): change loglevel from INFO to INFO_2. none

Description Orion Poplawski 2011-11-02 15:28:52 UTC 
Description of problem:

yum outputs Setting up messages even with -d 0/1.  For years now I've run yum-cron with debug level set to 1.  This would send an email via the normal cron.daily reporting if packages were updated, but nothing if nothing was done.  Now I get:

/etc/cron.daily/0yum.cron:

Setting up Update Process
Setting up Yum Shell
Setting up Update Process

regardless.

# yum upgrade -d 0
Setting up Upgrade Process
# yum upgrade -d 1
Setting up Upgrade Process

Please limit these messages to debug level 2 or higher.

Version-Release number of selected component (if applicable):
yum-3.4.3-5.fc16.noarch
Comment 1 Zdeněk Pavlas 2011-11-18 10:55:43 UTC 
*** Bug 752323 has been marked as a duplicate of this bug. ***
Comment 2 Zdeněk Pavlas 2011-11-18 10:59:55 UTC 
Created attachment 534373 [details]
doneCommand(): change loglevel from INFO to INFO_2.
Comment 3 Zdeněk Pavlas 2011-11-18 11:02:32 UTC 
*** Bug 754937 has been marked as a duplicate of this bug. ***
Comment 4 Orion Poplawski 2011-11-18 20:36:03 UTC 
Works for me.  Ship it!
Comment 5 Zdeněk Pavlas 2011-11-24 15:59:38 UTC 
*** Bug 756512 has been marked as a duplicate of this bug. ***
Comment 6 Jan ONDREJ 2011-11-30 05:27:35 UTC 
Ping. Any volunteer, who can build this fix?
Comment 7 Fedora Update System 2011-12-09 19:21:15 UTC 
yum-3.4.3-7.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/yum-3.4.3-7.fc16
Comment 8 Fedora Update System 2011-12-10 20:09:19 UTC 
Package yum-3.4.3-7.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing yum-3.4.3-7.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-16950/yum-3.4.3-7.fc16
then log in and leave karma (feedback).
Comment 9 Fedora Update System 2011-12-12 22:03:50 UTC 
yum-3.4.3-7.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.