You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Jan Kupec (Jira)" <ji...@apache.org> on 2019/09/03 15:56:00 UTC
[jira] [Updated] (IGNITE-12139) RPM for 2.7.5 release built from
incorrect version
[ https://issues.apache.org/jira/browse/IGNITE-12139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Kupec updated IGNITE-12139:
-------------------------------
Description:
The {{apache-ignite-2.7.5}} RPM found in the [official RPM repository|https://ignite.apache.org/download.cgi#rpm-package] has been built from commit *{{c9521338}}*, which is several weeks of development away from the head of the {{ignite-2.7.5}} release branch (*{{be4f2a15}}*) and apparently contains incompatible changes.
Is this a result of a human error or an error in the automated build system? Can this easily be fixed?
was:
The {{apache-ignite-2.7.5}} RPM found in the [official RPM repository|https://ignite.apache.org/download.cgi#rpm-package] has been built from commit *{{c9521338}}*, which is several weeks of development away from the head of the {{ignite-2.7.5}} release branch (*{{be4f2a15}}*) and apparently contains incompatible changes.
Is this a result of a human error or an error in the automated build system? Can this be easily fixed?
> RPM for 2.7.5 release built from incorrect version
> --------------------------------------------------
>
> Key: IGNITE-12139
> URL: https://issues.apache.org/jira/browse/IGNITE-12139
> Project: Ignite
> Issue Type: Bug
> Components: build
> Affects Versions: 2.7.5
> Reporter: Jan Kupec
> Priority: Minor
>
> The {{apache-ignite-2.7.5}} RPM found in the [official RPM repository|https://ignite.apache.org/download.cgi#rpm-package] has been built from commit *{{c9521338}}*, which is several weeks of development away from the head of the {{ignite-2.7.5}} release branch (*{{be4f2a15}}*) and apparently contains incompatible changes.
> Is this a result of a human error or an error in the automated build system? Can this easily be fixed?
--
This message was sent by Atlassian Jira
(v8.3.2#803003)