currently GCC 4.6.1 is in updates-testing
on local build-machines the update fails because libtool requires GCC 4.5.0
please rebuild it for 4.6.1, i did this today on my test-buildmachine and currently all my local maintained packages are rebuilt with GCC 4.6..1
It seems libtool has been built against GCC 4.6.1 in F16 but not F15. This lack of an update in F15 is blocking update of GCC.
what does mean "it seems" and "blocks"?
[root@testserver:~]$ rpm -qa | grep libtool
[root@testserver:~]$ rpm -qa | grep gcc
The current libtool package in F15 has a hard dependency on GCC 4.6.0. GCC has been updated to 4.6.1 but the packages cannot be upgraded if one has libtool installed because of the hard dependency on GCC 4.6.0. The libtool package in F16 has its dependency on GCC 4.6.1.
How is this normally resolved for libtool?
i don't know, but i guess libtool should be rebuilt with the new deps and pushed to updates-testing at the same time as GCC what did not happen, so currently "updates-testing" is broken while all works fine, this is only a dep-problem
Here's the error I just received while trying to update on F15.
Error: Package: libtool-2.4-4.fc15.x86_64 (@/libtool-2.4-4.fc15.x86_64)
Requires: gcc = 4.6.0
Removing: gcc-4.6.0-10.fc15.x86_64 (@updates-testing)
gcc = 4.6.0-10.fc15
Updated By: gcc-4.6.1-8.fc15.x86_64 (updates-testing)
gcc = 4.6.1-8.fc15
Available: gcc-4.6.0-6.fc15.x86_64 (fedora)
gcc = 4.6.0-6.fc15
new libtool-2.4-6.fc15 is on its way to f15-updates-testing