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

mesos: Fix insecure Maven domain #78703

Closed
wants to merge 1 commit into from

Conversation

jpgu-epam
Copy link

@jpgu-epam jpgu-epam commented Jan 28, 2020

Motivation for this change

Maven insecure domain was changed.
Closes: #78702

Things done

Fix Maven insecure domain for mesos derivation.

  • 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.

@ikervagyok
Copy link
Contributor

@jpgu-epam why not simply change http to https? Would be a better fix in the long run.

@jpgu-epam
Copy link
Author

@jpgu-epam why not simply change http to https? Would be a better fix in the long run.

I agree with you but I don't know what this can affects, because why wasn't it over https already?

My guess here is we are trying to include those environments without https support.

@veprbl
Copy link
Member

veprbl commented Jan 28, 2020

@jpgu-epam Please target the "master" branch instead of "nixos-19.09".

@jpgu-epam
Copy link
Author

Closed on favor of #78764

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

4 participants