Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

boost 1.67.0 #26605

Closed
wants to merge 29 commits into from
Closed

boost 1.67.0 #26605

wants to merge 29 commits into from

Conversation

commitay
Copy link
Contributor

  • Have you followed the guidelines for contributing?
  • Have you checked that there aren't other open pull requests for the same formula update/change?
  • Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
  • Does your build pass brew audit --strict <formula> (after doing brew install <formula>)?

boost-build doesn't have a 1.67.0 tag yet. https://github.com/boostorg/build/releases

@jbeich
Copy link

jbeich commented Apr 15, 2018

@ilovezfs
Copy link
Contributor

I think we can just ignore boost-build for now. I've filed an issue. boostorg/build#298

@commitay
Copy link
Contributor Author

@BrewTestBot test this please

@fxcoudert
Copy link
Member

boost-build “latest release” on their website clearly points to 2014.10

@henryiii
Copy link
Contributor

henryiii commented Apr 15, 2018

It looks like Boost Build 1.67 is now tagged. :)

@ilovezfs
Copy link
Contributor

@fxcoudert feel free to report that upstream.

@ilovezfs
Copy link
Contributor

osquery failure is preexisting osquery/osquery#4283

@ilovezfs ilovezfs closed this in fc650f2 Apr 17, 2018
@ilovezfs
Copy link
Contributor

Shipped!

@ilovezfs
Copy link
Contributor

ilovezfs commented Apr 17, 2018

Remaining revision bumps here:

And upscaledb homepage issue reported here: cruppstahl/upscaledb#112

@commitay commitay deleted the boost-1.67.0 branch April 17, 2018 18:29
@lock lock bot added the outdated PR was locked due to age label May 17, 2018
@lock lock bot locked as resolved and limited conversation to collaborators May 17, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
outdated PR was locked due to age
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants