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
Bug
Firefox
First issue.
On this documentation page : https://docs.strangebee.com/cortex/download/#debian-ubuntu. You reference the following link : https://rpm.thehive-project.org/release/noarch which is not working. It's missing the "/" at the end to work : https://rpm.thehive-project.org/release/noarch/ .
Second Issue.
Once you access https://rpm.thehive-project.org/release/noarch/, none of the packages are accessible. When you click on a package you get redirected to https://rpm.thehive-project.org/repository/rpm.thehive-project.org/release/noarch/<package_name>. The URL should be https://rpm.thehive-project.org/release/noarch/<package_name>.
Review the configuration of you RPM repository.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
RPM repository does not work
Request Type
Bug
Work Environment
Firefox
Problem Description
First issue.
On this documentation page : https://docs.strangebee.com/cortex/download/#debian-ubuntu. You reference the following link : https://rpm.thehive-project.org/release/noarch which is not working. It's missing the "/" at the end to work : https://rpm.thehive-project.org/release/noarch/ .
Second Issue.
Once you access https://rpm.thehive-project.org/release/noarch/, none of the packages are accessible. When you click on a package you get redirected to https://rpm.thehive-project.org/repository/rpm.thehive-project.org/release/noarch/<package_name>. The URL should be https://rpm.thehive-project.org/release/noarch/<package_name>.
Possible Solutions
Review the configuration of you RPM repository.
The text was updated successfully, but these errors were encountered: