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

oraclejdk: 8u111, 8u112 -> 8u121 [Critical security fix] #21968

Merged
merged 1 commit into from Jan 18, 2017

Conversation

taku0
Copy link
Contributor

@taku0 taku0 commented Jan 18, 2017

Motivation for this change
  • Critical security fix
  • Other updates

http://www.oracle.com/technetwork/security-advisory/cpujan2017-2881727.html#AppendixJAVA
http://www.oracle.com/technetwork/java/javase/8u121-relnotes-3315208.html

Note that PSU (8u122) is not released. It is identical to CPU version.

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.

@mention-bot
Copy link

@taku0, thanks for your PR! By analyzing the history of the files in this pull request, we identified @NeQuissimus and @thoughtpolice to be potential reviewers.

@@ -1,9 +1,9 @@
import ./jdk-linux-base.nix {
productVersion = "8";
patchVersion = "112";
patchVersion = "121";
Copy link
Member

Choose a reason for hiding this comment

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

Do you happen to know why there is no 122 this time around?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Member

Choose a reason for hiding this comment

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

yep, I was just curious...

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