Description of problem: yum install vtk Dependencies Resolved =============================================================== Package Arch Version Repository Size =============================================================== Installing: vtk x86_64 5.6.0-36.fc15 rawhide 11 M Installing for dependencies: mesa-libOSMesa-devel x86_64 7.9-0.6.fc14 rawhide 38 k vtk-devel x86_64 5.6.0-36.fc15 rawhide 2.4 M vtk-java x86_64 5.6.0-36.fc15 rawhide 4.5 M vtk-python x86_64 5.6.0-36.fc15 rawhide 3.7 M vtk-tcl x86_64 5.6.0-36.fc15 rawhide 3.6 M Version-Release number of selected component (if applicable): 5.6.0 Additional info: %{_libdir}/libCosmo.so and %{_libdir}/libVPIC.so are not symbolic link, and should not be placed at -devel subpackage.
This is still a problem for vtk 5.6.1-1, and is extremely annoying when you trying to build a system without -devel packages installed, as installing vtk-devel pulls in a number of other -devel packages in turn.
Filed an issue upstream: http://public.kitware.com/Bug/view.php?id=11820 I'd like to see them sprout an soversion.
vtk-5.6.1-3.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/vtk-5.6.1-3.fc15
vtk-5.6.1-3.fc15 has been pushed to the Fedora 15 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 vtk'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/vtk-5.6.1-3.fc15
vtk-5.6.1-3.fc15, gdcm-2.0.16-13.fc15.1 has been pushed to the Fedora 15 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 vtk gdcm'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/gdcm-2.0.16-13.fc15.1,vtk-5.6.1-3.fc15
vtk-5.6.1-3.fc15, gdcm-2.0.16-13.fc15.1 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.