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

Dependency errors #13

Open
nshafer opened this issue Sep 28, 2021 · 0 comments
Open

Dependency errors #13

nshafer opened this issue Sep 28, 2021 · 0 comments

Comments

@nshafer
Copy link

nshafer commented Sep 28, 2021

I am getting the following warnings after installing EasySSL 1.3, and doing a deps.get or deps.compile

==> easy_ssl
Compiling 1 file (.ex)
warning: :crypto.hash/2 defined in application :crypto is used by the current application but the current application does not depend on :crypto. To fix this, you must do one of:

  1. If :crypto is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :crypto is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :crypto, you may optionally skip this warning by adding [xref: [exclude: [:crypto]]] to your "def project" in mix.exs

  lib/easy_ssl.ex:201: EasySSL.fingerprint_cert/1

warning: :public_key.pkix_decode_cert/2 defined in application :public_key is used by the current application but the current application does not depend on :public_key. To fix this, you must do one of:

  1. If :public_key is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :public_key is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :public_key, you may optionally skip this warning by adding [xref: [exclude: [:public_key]]] to your "def project" in mix.exs

  lib/easy_ssl.ex:76: EasySSL.parse_der/2

warning: :public_key.pkix_sign_types/1 defined in application :public_key is used by the current application but the current application does not depend on :public_key. To fix this, you must do one of:

  1. If :public_key is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs

  2. If :public_key is a dependency, make sure it is listed under "def deps" in your mix.exs

  3. In case you don't want to add a requirement to :public_key, you may optionally skip this warning by adding [xref: [exclude: [:public_key]]] to your "def project" in mix.exs

  lib/easy_ssl.ex:273: EasySSL.parse_signature_algo/1

Generated easy_ssl app

This is with:

elixir          1.12.3-otp-24
erlang          24.1

If I put xref: [exclude: [:crypto, :public_key]] in the mix.exs project() function, the warnings go away. I have no idea if this module actually needs those applications to be running.. my guess is not. If that's the case, I can create a PR with this fix.

Thanks,
Nate

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

No branches or pull requests

1 participant