#369380 fixes the build.

Rebased for the build fix.

@tobim The next staging-next is imminent, do you think this is worth trying? I’ve seen some projects patch for Boost 1.87 already and it seems like the substantive breaking changes are restricted to a couple libraries so I’m hopeful it won’t be too painful.

(But of course we could wait untlil the Python split is done and do both in one cycle as well.)

While I'd like to have the latest version as the default, I don't think working on the related fixups for this bump can be a priority for me at the moment.

That said, don't let me or the boost_python split hold you back if you want to go for it.

No worries – just wanted to check in case you thought the ecosystem definitely wouldn’t be ready for it. I’m happy to coordinate bumping boost186 back where necessary if all else fails, so I’ll give it a go :)

Bisect says 8a80b63 boost: boost186 -> boost187 broke kea build in staging as:

$ nix build --no-link -f. -L kea
...
kea> In file included from io_endpoint.cc:12:
kea> ../../../src/lib/asiolink/tcp_endpoint.h: In constructor 'isc::asiolink::TCPEndpoint::TCPEndpoint(const isc::asiolink::IOAddress&, short unsigned int)':
kea> ../../../src/lib/asiolink/tcp_endpoint.h:45:74: error: 'from_string' is not a member of 'boost::asio::ip::address'
kea>    45 |             new boost::asio::ip::tcp::endpoint(boost::asio::ip::address::from_string(address.toText()),
kea>       |                                                                          ^~~~~~~~~~~

Thanks! I can’t find any upstream fix or distro patches (we’re tracking ahead of other distros for once), so it’ll probably need pinning for now unless the fix is super simple. I’ll try to look at it in the next couple of days (but feel free to ping me if I forget, or just pin it to boost186).

wesnoth fails to build against boost187 in master. Proposed the pin as:

• wesnoth: pin to boost-1.86.0 #375266