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

[20.03] slurm: 19.05.7.1 -> 19.05.8.1 #105995

Merged
merged 1 commit into from Dec 5, 2020

Conversation

markuskowa
Copy link
Member

Motivation for this change

Addresses CVE-2020-27745 and CVE-2020-27746.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@markuskowa
Copy link
Member Author

@GrahamcOfBorg test slurm

@markuskowa markuskowa merged commit 030e2ce into NixOS:release-20.03 Dec 5, 2020
@markuskowa markuskowa deleted the cve-slurm-20.03 branch December 5, 2020 18:39
@SuperSandro2000
Copy link
Member

20.03 is EOL and should not receive any updates anymore. Please backport only to 20.09.

@markuskowa
Copy link
Member Author

I actually disagree with that interpretation of EOL (or is there an RFC that says "one must not do back ports beyond EOL"?). Even though 20.03 has been announced to be retired end of November it is still shown as active on https://status.nixos.org/. From my experience people push back ports even beyond the EOL date to address critical security issues. Slurm is commonly used on HPC cluster. These systems have usually some inertia when it comes to upgrades.

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

2 participants