On 2018/11/27 16:46, Boyuan Yang <by...@debian.org> wrote: > You must be using Debian Testing. This problem is fixed in Debian Unstable but > the yaml-cpp package hasn't migrate to Debian Testing yet.
Btw. the Debian patch which works around this bug is bad. It is wrapped in a #if BOOST_VERSION >= 106700 But the yaml-cpp code was wrong even for old versions; just other headers happened to already include <boost/next_prior.hpp> previously, but that is not guaranteed. While this works around the specific problem we saw (i.e. makes the problem invisible), the condition is not correct and should be removed to avoid fragility. The header needs to be included unconditionally because it uses boost::next(). Max
