Bug 1275114

Summary: eclipse-ecf-core >= 3.11.0-1 needed by eclipse-platform-1:4.5.1-2.fc22.x86_64
Product: [Fedora] Fedora Reporter: Jim Swain <jim.swain>
Component: eclipseAssignee: Mat Booth <mat.booth>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: akurtako, andjrobins, eclipse-sig, jerboaa, jim.swain, krzysztof.daniel, mat.booth, rgrunber
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-26 21:23:50 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:
Attachments:
Description Flags
eclipse error log none

Description Jim Swain 2015-10-26 00:12:34 UTC
Created attachment 1086336 [details]
eclipse error log

Description of problem:
eclipse-platform-1:4.5.1-2.fc22.x86_64 requires eclipse-ecf-core >= 3.11.0-1 and repositories only provide eclipse-ecf-core 3.10.1-1.fc22


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. use fedup --network 22 (from f21)
2. fedup.log reports
WARNING: problems were encountered during transaction test:
  broken dependencies
    eclipse-platform-1:4.5.1-2.fc22.x86_64 requires eclipse-platform-1:4.5.1-2.fc22.x86_64
3. attempt dnf update eclipse-platform freports
Error: nothing provides eclipse-ecf-core >= 3.11.0-1 needed by eclipse-platform-1:4.5.1-2.fc22.x86_64


Actual results:
eclipse terminates with error log (attached)


Expected results:
eclipse runs


Additional info:

Comment 1 Alexander Kurtakov 2015-10-26 07:23:28 UTC
Mat, this one is yours

Comment 2 Mat Booth 2015-10-26 09:18:02 UTC
A bug in Bodhi (the Fedora updates system) has meant that it failed to push all necesssary updates simultaneously

This should be resolved with the next updates push.

Sorry for the inconvenience  :-(

Comment 3 Jim Swain 2015-10-26 21:16:26 UTC
Issue resolved with update push of 2015.10.26. Update received and applied at 13:15 PDST