-
Notifications
You must be signed in to change notification settings - Fork 0
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
Documentation feedback on /docs/install/redhat.rst (SUSE support) #72
Comments
@matriv suggested:
|
There is a corresponding setting, right. It is called |
ProblemWhen adding
SolutionPublic key must be imported upfront.
zypper parameter References
Details
|
CrateDB on SUSE in a nutshell. Use that config in [cratedb-ce-stable]
name=CrateDB RPM package repository - $basearch - Stable
baseurl=https://cdn.crate.io/downloads/yum/7/$basearch
enabled=0
gpgcheck=1
repo_gpgcheck=0
gpgkey=https://cdn.crate.io/downloads/yum/RPM-GPG-KEY-crate
autorefresh=1
type=rpm-md
[cratedb-ce-testing]
name=CrateDB RPM package repository - $basearch - Testing
baseurl=https://cdn.crate.io/downloads/yum/testing/7/$basearch
enabled=0
gpgcheck=1
repo_gpgcheck=0
gpgkey=https://cdn.crate.io/downloads/yum/RPM-GPG-KEY-crate
autorefresh=1
type=rpm-md Use that command to import the public GPG key, in order to make signature validation work. rpm --import https://cdn.crate.io/downloads/yum/RPM-GPG-KEY-crate Finally, use those commands to install and start CrateDB. zypper --plus-content=cratedb-ce-stable install -y crate
systemctl start crate |
Thx a lot @amotl, see: https://github.com/crate/distribute/pull/680 |
Excellent. Thanks for adding software tests! |
Hi again. Coming from GH-71, we wanted to report that installation on SUSE and derivates fails with an error about signing.
Problem
The text was updated successfully, but these errors were encountered: