Bug 1114122 - vast numbers of errors in yum update
Summary: vast numbers of errors in yum update
Keywords:
Status: CLOSED DUPLICATE of bug 1111349
Alias: None
Product: Fedora
Classification: Fedora
Component: java-1.7.0-openjdk
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: jiri vanek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-27 19:38 UTC by Tom Horsley
Modified: 2014-06-30 09:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-30 09:40:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.