Bug 1114122

Summary: vast numbers of errors in yum update
Product: [Fedora] Fedora Reporter: Tom Horsley <horsley1953>
Component: java-1.7.0-openjdkAssignee: jiri vanek <jvanek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: ahughes, dbhole, jerboaa, jvanek, omajid
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: 2014-06-30 09:40:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tom Horsley 2014-06-27 19:38:42 UTC 
Description of problem:
Did a yum update this morning, and got a gazillion lines
of this nonsense:

  Cleanup    : 1:java-1.7.0-openjdk-devel-1.7.0.60-2.4.7.4.fc20.x86_64    43/56 
warning: file /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.4.fc20.x86_64/tapset/jstack-1.7.0.60-2.4.7.4.fc20.stp: remove failed: No such file or directory
warning: file /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.4.fc20.x86_64/tapset/hotspot_jni-1.7.0.60-2.4.7.4.fc20.stp: remove failed: No such file or directory
...
warning: file /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.4.fc20.x86_64/LICENSE: remove failed: No such file or directory
warning: file /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.4.fc20.x86_64/ASSEMBLY_EXCEPTION: remove failed: No such file or directory


Version-Release number of selected component (if applicable):
The version I have now after the update is:
java-1.7.0-openjdk-devel-1.7.0.60-2.5.0.1.fc20.x86_64

The previous version was:
java-1.7.0-openjdk-devel-1.7.0.60-2.4.7.4.fc20.x86_64

How reproducible:
Just ran yum update this once.

Steps to Reproduce:
1.yum update
2.
3.

Actual results:
spewing of lots of errors

Expected results:
nice and quiet

Additional info:
Comment 1 jiri vanek 2014-06-30 09:40:16 UTC 

*** This bug has been marked as a duplicate of bug 1111349 ***