[ 
https://issues.apache.org/jira/browse/CASSANDRA-17765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17625735#comment-17625735
 ] 

Florent SIEBERT commented on CASSANDRA-17765:
---------------------------------------------

Hi Brandon, thanks for your answer.

The RPM was provided by customer on a local repository so I'm not sure how he 
got it.

However, I just tried to add the official repository on a sandbox VM 
(https://cassandra.apache.org/_/download.html):
{noformat}
# cat <<EOF > /etc/yum.repos.d/cassandra.repo
[cassandra]
name=Apache Cassandra
baseurl=https://redhat.cassandra.apache.org/40x/
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://downloads.apache.org/cassandra/KEYS
EOF{noformat}
{noformat}
# yum install cassandra
[...]
Resolving Dependencies
--> Running transaction check
---> Package cassandra.noarch 0:4.0.7-1 will be installed
Error: Invalid version flag: or{noformat}
{noformat}
# yumdownloader cassandra
# rpm -qpf --requires cassandra-4.0.7-1.noarch.rpm | grep jre
warning: cassandra-4.0.7-1.noarch.rpm: Header V4 RSA/SHA256 Signature, key ID 
7e3e87cb: NOKEY
(jre-1.8.0 or jre-11){noformat}
Indeed, it's not the same rpm you mentionned:
{noformat}
# md5sum cassandra-4.0.7-1.noarch.rpm
2b5f85e027caee7e41419f3cb9e21c67  cassandra-4.0.7-1.noarch.rpm{noformat}
But how can we got the "noboolean" from the repository?

(Because of https://issues.apache.org/jira/browse/INFRA-23802, it's not very 
convenient to explore the repository)

> RPM Installation on centos 7 is broken by CASSANDRA-17669
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-17765
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17765
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Packaging
>            Reporter: Jeremiah Jordan
>            Assignee: Brandon Williams
>            Priority: Normal
>             Fix For: 4.0.6, 4.1-beta1, 4.1
>
>
> With CASSANDRA-17669 adding use of "or" in the dependencies for the RPM so it 
> can depend on java 8 or java 11 it broke installation on CentOS Linux 7.  
> This is bad because CentOS Linux 7 is the "current" release of CentOS Linux, 
> version 8 was EOL'ed in favor of the new pre-release distribution model being 
> used for CentOS Stream 8.
> I don't know what the best answer is here, maybe making a CentOS 7 specific 
> package that reverts back to just java 8 in the requirements?  But I think 
> should needs to be done.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to