Bug 1102978
| Summary: | Java-1.7.0-openjdk Yum Update Causes A Slew Of Errors. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Randy Berry <randyn3lrx> | 
| Component: | java-1.7.0-openjdk | Assignee: | jiri vanek <jvanek> | 
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | 
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | ahughes, dbhole, jerboaa, jvanek, omajid | 
| 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: | 2014-06-30 09:36:28 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
        
        
          Randy Berry
        
        
        
        
        
          2014-05-30 00:53:32 UTC
        
       It doesn't appear serious, but are you able to reproduce this? Nope can't reproduce. I tried yum reinstall, no errors, and yum remove but remove wanted to take out a ton of other packages so I didn't allow it. Nothing appears to be broken I was just thinking it might alarm someone to see all the errors on update. Although I haven't seen anyone report it in #fedora irc yet. I think that there was a fix added to the spec file to fix ordering that should prevent this. I am going to assign this to Jiri who can very and close this when he is back from PTO. Yes. The fix for this was really posted - since 1.7.0.55-2.4.7.0.fc20. The attached report seems to be an output from latest not patched rpms, but I will double check. However - it seems that there are certain condition - quite random to be honest - when OrderWithRequires do not help to fix the issue. *** This bug has been marked as a duplicate of bug 1111349 *** |