Description of problem: Current version of dragonegg needs the previous version of GCC. Therefore, if drangonegg is installed, you can't update to the latest GCC. Version-Release number of selected component (if applicable): dragonegg 3.4-0.4.rc0 (needs gcc = 4.8.3-1) How reproducible: try to update gcc when dragonegg is already installed. Steps to Reproduce: 1. yum update 2. 3. Actual results: Error: Package: dragonegg-3.4-0.4.rc0.fc20.x86_64 (@updates) Requires: gcc = 4.8.3-1.fc20 Removing: gcc-4.8.3-1.fc20.x86_64 (@updates) gcc = 4.8.3-1.fc20 Updated By: gcc-4.8.3-7.fc20.x86_64 (updates) gcc = 4.8.3-7.fc20 Available: gcc-4.8.2-1.fc20.x86_64 (fedora) gcc = 4.8.2-1.fc20 Expected results: Expected to be able to install the new gcc.... Additional info: Perhaps dragonegg's dependancy on gcc should be >= instead of =?
The dragonegg package requires the exact version of gcc it was built against. Using a ">=" dependency won't work. I'm not aware of any way to resolve this other than that if you want to upgrade gcc, and there isn't a corresponding dragonegg package (which there presently isn't, due to missing GCC headers, Bug #1094531), remove dragonegg.
No, Bug #1094531 is about gcc 4.9. The bug here is about the regular update from 4.8.3-1 to gcc-4.8.3-7 which simply missed triggering a rebuild for the depending package dragonegg. How can this even happen? The gcc update to 4.8.3-1 was bundled correctly: gcc-4.8.3-1.fc20,libtool-2.4.2-24.fc20,gcc-python-plugin-0.12-16.fc20,dragonegg-3.4-0.4.rc0.fc20 The gcc update to 4.8.3-7 updated gcc only. So either the update is botched (by missing the dependencies), or dragonegg should require gcc-4.8.3-? rather than a specific spec version.
A simple rebuild is really all that is needed: http://koji.fedoraproject.org/koji/taskinfo?taskID=7646741
Created attachment 939912 [details] spec file with gcc package dependency bump
dragonegg-3.4-0.5.rc0.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/dragonegg-3.4-0.5.rc0.fc20
> or dragonegg should require gcc-4.8.3-? rather than a specific spec version. Won't work. Dragonegg *must* be build for the specific gcc build.
Package dragonegg-3.4-0.5.rc0.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing dragonegg-3.4-0.5.rc0.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-11504/dragonegg-3.4-0.5.rc0.fc20 then log in and leave karma (feedback).
This is now happening on FC19. Do I need to open a new bug for FC19? Error: Package: dragonegg-3.3-2.fc19.x86_64 (@updates) Requires: gcc = 4.8.3-1.fc19 Removing: gcc-4.8.3-1.fc19.x86_64 (@updates) gcc = 4.8.3-1.fc19 Updated By: gcc-4.8.3-7.fc19.x86_64 (updates) gcc = 4.8.3-7.fc19 Available: gcc-4.8.1-1.fc19.x86_64 (fedora) gcc = 4.8.1-1.fc19 You could try using --skip-broken to work around the problem
dragonegg-3.3-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/dragonegg-3.3-3.fc19
dragonegg-3.4-0.5.rc0.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
dragonegg-3.3-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
This is now happening on F21: ERROR with transaction check vs depsolve: gcc = 4.8.3-7.fc20 is needed by (installed) dragonegg-3.4-0.5.rc0.fc20.i686 ** Found 3 pre-existing rpmdb problem(s), 'yum check' output follows: dragonegg-3.4-0.5.rc0.fc20.i686 has missing requires of gcc = ('0', '4.8.3', '7.fc20') dragonegg-3.4-0.5.rc0.fc20.i686 has missing requires of libLLVM-3.4.so
Dragonegg is not available for F21 due to bug #1094531. Remove dragonegg first ("rpm -e dragonegg" or perhaps "yum remove dragonegg"), then update gcc.