Bug 447459

Summary: Strange messages in /var/log/yum.log
Product: [Fedora] Fedora Reporter: Philip Ashmore <contact>
Component: yumAssignee: Seth Vidal <skvidal>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 8CC: ffesti, james.antill, jhutar, katzj, pmatilai, tim.lauridsen
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-09-03 13:30:29 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:
Attachments:
Description Flags
yum.log none

Description Philip Ashmore 2008-05-19 23:39:59 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.14) Gecko/20080416 Fedora/2.0.0.14-1.fc8 Firefox/2.0.0.14

Description of problem:
While inspecting /var/log/yum.log after a recent installation/update I noticed a long list consisting of
May 19 18:11:40 libedit: ts_done name in te is rarian-compat should be libedit
May 19 18:11:41 lohit-fonts-hindi: ts_done name in te is libedit should be lohit-fonts-hindi
May 19 18:11:42 kdeaccessibility: ts_done name in te is lohit-fonts-hindi should be kdeaccessibility
...
May 19 18:21:54 glx-utils: ts_done name in te is libsmbios-libs should be glx-utils
May 19 18:21:55 rpm-python: ts_done name in te is glx-utils should be rpm-python
May 19 18:21:55 libxml2-python: ts_done name in te is rpm-python should be libxml2-python
May 19 18:21:56 htdig: ts_done name in te is libxml2-python should be htdig


Version-Release number of selected component (if applicable):
yum-3.2.8-2.fc8.rpm

How reproducible:
Didn't try


Steps to Reproduce:
1.Install from KDE live CD
2.download updates to local repo
3.update via pup

Actual Results:
I got the messages in /var/log/yum.log

Expected Results:
Not that.

Additional info:
Comment 1 Philip Ashmore 2008-05-19 23:41:02 UTC 
Created attachment 306031 [details]
yum.log
Comment 2 Jan Hutař 2008-08-06 12:03:03 UTC 
Maybe this is same issue as in bug 307541?
Comment 3 seth vidal 2008-09-03 13:30:29 UTC 
yes it is the same bug. The message coming out in the log is how we let the client know what has happened. So it's not a wrong or bad message.