We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I use the manual installation method of Erlang and RabbitMQ on RHEL8 described in https://www.rabbitmq.com/install-rpm.html#downloads. To install Erlang, I use the direct download from https://github.com/rabbitmq/erlang-rpm/releases. Now I want to verify the downloaded Erlang rpm file with gpg and the RabbitMQ release signing key, as described in https://www.rabbitmq.com/signatures.html#checking-signatures. But I am missing the signature file for the Erlang rpm file: the release page on Github (https://github.com/rabbitmq/erlang-rpm/releases) includes only the rpm files, no *.asc files. Is there any possibility to provide the signature files?
The text was updated successfully, but these errors were encountered:
The documentation only mentions that we sign RabbitMQ packages, not Erlang ones (at this time). We've made a note of your request, thanks.
Sorry, something went wrong.
michaelklishin
lukebakken
No branches or pull requests
Hi,
I use the manual installation method of Erlang and RabbitMQ on RHEL8 described in https://www.rabbitmq.com/install-rpm.html#downloads. To install Erlang, I use the direct download from https://github.com/rabbitmq/erlang-rpm/releases. Now I want to verify the downloaded Erlang rpm file with gpg and the RabbitMQ release signing key, as described in https://www.rabbitmq.com/signatures.html#checking-signatures. But I am missing the signature file for the Erlang rpm file: the release page on Github (https://github.com/rabbitmq/erlang-rpm/releases) includes only the rpm files, no *.asc files. Is there any possibility to provide the signature files?
The text was updated successfully, but these errors were encountered: