Bug 890855 - yum install eclipse - Error: - (@updates-testing)
Summary: yum install eclipse - Error: - (@updates-testing)
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Krzysztof Daniel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 890858 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-30 18:33 UTC by Flóki Pálsson
Modified: 2014-01-13 00:27 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-02 06:51:47 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Flóki Pálsson 2012-12-30 18:33:47 UTC 
Description of problem:
Can not instlla eclipse.

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


How reproducible:
always 

Steps to Reproduce:
1.  #  yum install eclipse
2.
3.
  
Actual results:
--> Finished Dependency Resolution
Error: Package: glibc-2.16-24.fc18.i686 (fedora)
           Requires: glibc-common = 2.16-24.fc18#
           Installed: glibc-common-2.16-28.fc18.x86_64 (@updates-testing)
               glibc-common = 2.16-28.fc18
           Available: glibc-common-2.16-24.fc18.x86_64 (fedora)
               glibc-common = 2.16-24.fc18
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest



Expected results:
eclipse installed

Additional info:
Grup install form yumex fails also
Comment 1 Krzysztof Daniel 2012-12-31 08:48:04 UTC 
*** Bug 890858 has been marked as a duplicate of this bug. ***
Comment 2 Krzysztof Daniel 2012-12-31 08:56:52 UTC 
Thanks for your bug report.

Are you able to install anything? If not, please reset those problematic pacakges:

yum downgrade glibc glibc-common and retry. This should help.
Comment 3 Flóki Pálsson 2013-01-01 18:13:26 UTC 
works now with yumex and updates-testing enabled.
Comment 4 Krzysztof Daniel 2013-01-02 06:51:47 UTC 
Thanks for your time. It was most probably an issue with mirroring - where not all packages were available in update-testing. This is quite common if frequent updates happen.
Note You need to log in before you can comment on or make changes to this bug.