I just found out that the original email was mangled by my email client, so I am sending it again. You might know that recently we discovered a circular dependency between Graph and Geometry. Because of this I added a flag to depinst that causes it to detect dependency cycles and exit with an error. E.g. localy I get: $ python tools/boostdep/depinst/depinst.py graph -C Installing: config, headers, ../tools/boost_install, ../tools/build, ../tools/ cmake Installing: config, property_map, serialization, concept_check, iterator, unordered, optional, mpl, core, type_traits, static_assert, smart_ptr, assert, random, tuple, range, throw_exception, parameter, detail, foreach, move, utility, preprocessor, integer, container_hash, typeof, geometry, numeric/ conversion, multi_index, algorithm, bimap, array, math, spirit, lexical_cast, xpressive, any, property_tree, conversion, tti, function, regex Error: Dependency cycle detected: graph -> geometry -> graph I suggest we add jobs to our CI workflows that use the flag. Note that it's probably not a good idea to always use the flag, because then a cycle created by your dependency can break your CI jobs. If you are using boost-ci's common_install, the flag can be enabled by setting the environment variable DEPINST to "-C" or "--reject-cycles".