Created attachment 913792 [details] update boost/graph/dijkstra_shortest_paths.hpp to 1.55.0 Description of problem: prim_minimum_spanning_tree often throws a negative_edge exception even though the graph given to it only has positive edges. This is a known bug with 1.54.0, and fixed in 1.55.0: https://svn.boost.org/trac/boost/ticket/9012 https://svn.boost.org/trac/boost/ticket/9347 Version-Release number of selected component (if applicable): 1.54.0-9.fc20.x86_64 How reproducible: always Steps to Reproduce: 1.See https://svn.boost.org/trac/boost/ticket/9012 Actual results: negative_edge exception Expected results: minimum spanning tree result Additional info: The easiest solution is to upgrade boost/graph/dijkstra_shortest_paths.hpp to the version of 1.55.0, or at least the first two hunks (see attached patch)
boost-1.54.0-11.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/boost-1.54.0-11.fc20
Package boost-1.54.0-11.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 boost-1.54.0-11.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-0642/boost-1.54.0-11.fc20 then log in and leave karma (feedback).
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.