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

ocproxy: 1.50 -> 1.60 #23368

Closed
wants to merge 1 commit into from
Closed

ocproxy: 1.50 -> 1.60 #23368

wants to merge 1 commit into from

Conversation

ndowens
Copy link
Contributor

@ndowens ndowens commented Mar 2, 2017

Motivation for this change

Update

Things done
  • Tested using sandboxing
    (nix.useSandbox on NixOS,
    or option build-use-sandbox in nix.conf
    on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • Linux
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

@Mic92
Copy link
Member

Mic92 commented Mar 2, 2017

ping @Joko

@joachifm
Copy link
Contributor

joachifm commented Mar 5, 2017

Meanwhile, 1.70 has been released. Per https://github.com/cernekee/ocproxy/blob/master/CHANGES the 1.50->1.70 delta looks pretty safe.

@ndowens
Copy link
Contributor Author

ndowens commented Mar 5, 2017 via email

};

buildInputs = [ autoconf automake libevent ];

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a heads up, there is some whitespace on the end of this line that doesn't need to be there. I fixed it for you :) Depending on your editor, it may have a plugin called "EditorConfig" which will do this automatically.

@grahamc
Copy link
Member

grahamc commented Mar 6, 2017

Merged in 3686e1b, thank you! Put in another PR for the 1.70 when you get a chance.

@grahamc grahamc closed this Mar 6, 2017
@ndowens
Copy link
Contributor Author

ndowens commented Mar 6, 2017

@grahamc as soon as I can 😀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants