Description of problem: Error: Package: evolution-sharp-0.21.1-7.fc14.x86_64 (rawhide) Requires: libecal-1.2.so.7()(64bit) Error: Package: evolution-sharp-0.21.1-7.fc14.x86_64 (rawhide) Requires: libebook-1.2.so.9()(64bit) You could try using --skip-broken to work around the problem Version-Release number of selected component (if applicable): evolution-sharp-0.21.1-7.fc14 How reproducible: always Steps to Reproduce: 1. yum install evolution-sharp
Updated evolution-sharp has been already built, I will release update for F14.
evolution-sharp-0.21.1-8.fc14 has been submitted as an update for Fedora 14. http://admin.fedoraproject.org/updates/evolution-sharp-0.21.1-8.fc14
(In reply to comment #1) > Updated evolution-sharp has been already built, I will release update for F14. After further inspection this build (evolution-sharp-0.21.1-8.fc14) is broken as well, unfortunately. It depends on libcamel-1.2.so.19 which is part of unpushed evolution-2.31.90-1.fc14. Raising severity to high because it's impossible to build other packages, like tasque, now (https://kojiweb.fedoraproject.org/koji/buildinfo?buildID=191743). And reassigning to maintainer for further inspection. In my opinion the best solution is to tag evolution-2.31.90-1.fc14 into dist-f14-override and problems should go away. Or rebuild evolution-sharp against older libraries.
evolution-sharp-0.21.1-9.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/evolution-sharp-0.21.1-9.fc14
evolution-sharp-0.21.1-9.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update evolution-sharp'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/evolution-sharp-0.21.1-9.fc14
evolution-sharp-0.21.1-9.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 631627 has been marked as a duplicate of this bug. ***