[JIRA] (OVIRT-1893) Remove ovirt-ansible-disaster-recovery-1.1 upstream version to install version 0.1 instead

Tuesday, 20 February 2018

This is a multi-part message in MIME format...

------------=_1519137694-17807-279
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

    [
https://ovirt-jira.atlassian.net/browse/OVIRT-1893?page=com.atlassian.jir...
] 

Maor Lipchuk commented on OVIRT-1893:
-------------------------------------

We thought about building a newer build
of ovirt-ansible-disaster-recovery-1.1 so it will be installed instead of
the 1.1, but we first need first to solve an issue in the repo.
It could be great if the 1.1 build will be removed since it is currently
broken.

Regards,
Maor

On Tue, Feb 20, 2018 at 4:29 PM, eyal edri (oVirt JIRA) <

...
 Remove ovirt-ansible-disaster-recovery-1.1 upstream version to
install version 0.1 instead

------------------------------------------------------------------------------------------

                 Key: OVIRT-1893
                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1893
             Project: oVirt - virtualization made easy
          Issue Type: By-EMAIL
            Reporter: Maor Lipchuk
            Assignee: infra

 Hi all,
 It seems that ovirt-ansible-disaster-recovery repo installed from upstream
 [1] is installed with version 1.1 [2]:
 ovirt-ansible-disaster-recovery-1.1 is broken, because of a bug which was
 already fixed [3] in ovirt-ansible-disaster-recovery 0.1.
 The thing is that the release which automatically installed is 1.1 although
 the fix is available in ovirt-ansible-disaster-recovery 0.1.
 Is there a way to do something about it, could we remove the 1.1 versions,
 so 0.1 will be installed instead?
 [1] http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm
 [2]
 ovirt-ansible-disaster-recovery-1.1.0-0.1.master.20180104150940.el7.centos.noarch
 [3] https://github.com/oVirt/ovirt-ansible-disaster-recovery/pull/4
 Regards,
 Maor 

--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100080)

------------=_1519137694-17807-279
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<pre>[
https://ovirt-jira.atlassian.net/browse/OVIRT-1893?page=com.atlassian.jir...
]</pre>
<h3>Maor Lipchuk commented on OVIRT-1893:</h3>
<p>We thought about building a newer build of ovirt-ansible-disaster-recovery-1.1 so
it will be installed instead of the 1.1, but we first need first to solve an issue in the
repo. It could be great if the 1.1 build will be removed since it is currently
broken.</p>
<p>Regards, Maor</p>
<p>On Tue, Feb 20, 2018 at 4:29 PM, eyal edri (oVirt JIRA) &lt;</p>
<blockquote><h3>Remove ovirt-ansible-disaster-recovery-1.1 upstream version to
install version 0.1 instead</h3>
<pre>     Key: OVIRT-1893
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1893
 Project: oVirt - virtualization made easy
         Issue Type: By-EMAIL
Reporter: Maor Lipchuk
Assignee: infra</pre>
<p>Hi all, It seems that ovirt-ansible-disaster-recovery repo installed from
upstream [1] is installed with version 1.1 [2]: ovirt-ansible-disaster-recovery-1.1 is
broken, because of a bug which was already fixed [3] in ovirt-ansible-disaster-recovery
0.1. The thing is that the release which automatically installed is 1.1 although the fix
is available in ovirt-ansible-disaster-recovery 0.1. Is there a way to do something about
it, could we remove the 1.1 versions, so 0.1 will be installed instead? [1] <a
href="http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.r...
[2] ovirt-ansible-disaster-recovery-1.1.0-0.1.master.20180104150940.el7.centos.noarch [3]
<a
href="https://github.com/oVirt/ovirt-ansible-disaster-recovery/pull/...
Regards, Maor</p></blockquote>
<p>&mdash; This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100080)</p>

------------=_1519137694-17807-279--

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011