boost 1.84

[iMichka]

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

[SMillerDev]

Shall I close #158705 then?

[iMichka]

Sorry, I missed #158705, my bad :(. Your's did not have the "long build" label, and as I did not see boost 1.84 in the long builds, I did not check for it in the other pull requests. I can push my changes to your pull request if you want, or we can close your's, as you wish.

[Porkepix]

Is it normal if every builds fails that it still tests the dependents?
I guess no long build conflict can be removed anyway, to allow for spdlog when this one will be run.

[SMillerDev]

The python failure makes no sense since it seems to be using C++14 on our side.

[iMichka]

I have a bunch of patches ready, will push as soon as I made significant progress, as not to pollute the long build queue too early.

[iMichka]

@iMichka Doesn't the build failing for fastnetmon on 12-x86_64 and 13-x86_64 not only the dependencies testing means it'll need some bottle rebuild after merge, though?

It's all good, no bottles were lost. Only dspdfviewer which I have added in #161046