Description of problem: icewm requires bluecurve-icon-theme. bluecurve-icon-theme requires bluecurve-cursor-theme. bluecurve-cursor-theme will not install because "Cannot install package bluecurve-cursor-theme-8.0.2-6.el6.noarch. It is obsoleted by installed package dmz-cursor-themes-0.4-4.el6.noarch". Version-Release number of selected component (if applicable): icewm.x86_64 0:1.3.7-1.el6 How reproducible: Always Steps to Reproduce: 1.yum install icewm 2.yum install http://dl.fedoraproject.org/pub/epel/6/x86_64/bluecurve-cursor-theme-8.0.2-6.el6.noarch.rpm 3. Actual results: For step 1: Resolving Dependencies --> Running transaction check ---> Package icewm.x86_64 0:1.3.7-1.el6 will be installed --> Processing Dependency: bluecurve-icon-theme for package: icewm-1.3.7-1.el6.x86_64 --> Running transaction check ---> Package bluecurve-icon-theme.noarch 0:8.0.2-6.el6 will be installed --> Processing Dependency: bluecurve-cursor-theme for package: bluecurve-icon-theme-8.0.2-6.el6.noarch --> Finished Dependency Resolution Error: Package: bluecurve-icon-theme-8.0.2-6.el6.noarch (epel) Requires: bluecurve-cursor-theme Available: bluecurve-cursor-theme-8.0.2-6.el6.noarch (epel) bluecurve-cursor-theme = 8.0.2-6.el6 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest For step 2: Examining /var/tmp/yum-root-w2z3Sl/bluecurve-cursor-theme-8.0.2-6.el6.noarch.rpm: bluecurve-cursor-theme-8.0.2-6.el6.noarch Cannot install package bluecurve-cursor-theme-8.0.2-6.el6.noarch. It is obsoleted by installed package dmz-cursor-themes-0.4-4.el6.noarch Error: Nothing to do Expected results: Installation of icewm and dependencies. Additional info:
I plan to issue a fixed build next week. Assigning the bug to me.
*** This bug has been marked as a duplicate of bug 768844 ***
icewm-1.3.7-3.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/icewm-1.3.7-3.el6
icewm-1.3.7-3.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.