<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 2 Jan 2017, at 13:52, Sandro Bonazzola <<a href="mailto:sbonazzo@redhat.com" class="">sbonazzo@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Mon, Jan 2, 2017 at 12:07 PM, Michal Skrivanek <span dir="ltr" class=""><<a href="mailto:michal.skrivanek@redhat.com" target="_blank" class="">michal.skrivanek@redhat.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><br class=""><div class=""><span class=""><blockquote type="cite" class=""><div class="">On 2 Jan 2017, at 12:01, Sandro Bonazzola <<a href="mailto:sbonazzo@redhat.com" target="_blank" class="">sbonazzo@redhat.com</a>> wrote:</div><br class="m_-7437885037108402238Apple-interchange-newline"><div class=""><div dir="ltr" class=""><br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Wed, Dec 28, 2016 at 9:55 AM, Gianluca Cecchi <span dir="ltr" class=""><<a href="mailto:gianluca.cecchi@gmail.com" target="_blank" class="">gianluca.cecchi@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr" class=""><span class="m_-7437885037108402238gmail-"><div class="gmail_extra"><div class="gmail_quote"><br class=""></div></div></span><div class="gmail_extra">As I wrote, no qemu package proposed. Because oVirt provided qemu is greater in version in respect with 7.3<br class=""></div><div class="gmail_extra">In fact, as I already wrote, I have now <br class=""><div class="">qemu-kvm-common-ev-2.3.0-31.el<wbr class="">7.16.1.x86_64</div><div class="">qemu-img-ev-2.3.0-31.el7.16.1.<wbr class="">x86_64<br class=""></div><div class="">qemu-kvm-ev-2.3.0-31.el7.16.1.<wbr class="">x86_64</div><div class="">qemu-kvm-tools-ev-2.3.0-31.el7<wbr class="">.16.1.x86_64</div></div></div></blockquote></div><br class="">Hi Gianluca, I added 2.6.0 to oVirt 4.0 repository at <a href="http://resources.ovirt.org/pub/ovirt-4.0/rpm/el7/" target="_blank" class="">http://resources.ovirt.org/<wbr class="">pub/ovirt-4.0/rpm/el7/</a>.</div><div class="gmail_extra">It was supposed to be published there with 4.0.6 GA coming ina few days but it has been already tested enough to be promoted to release repository.</div></div></div></blockquote><div class=""><br class=""></div></span>it would be best to remove it. We really do not want to get out of sync with platform</div></div></blockquote><div class=""><br class=""></div><div class="">Can you please tell me more about this? </div></div></div></div></div></blockquote><div><br class=""></div>we do not want to manually add platform-provided stuff in our repos. We should only put ovirt packages there, like ovirt-*, ioprocess and such. But everything else should be pulled in by external repos, even when it is us who maintain them. Otherwise we often run into conflicts e.g. when platform releases an update of a dependency and we do not release it at the same time in our repo.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class=""><br class=""></div><div class=""> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div class="">It is already causing problems since qemu-kvm-rhev package is 2.6.0-27 and the one you placed in <a href="http://resources.ovirt.org/" target="_blank" class="">resources.ovirt.org</a> is 2.6.0-27.1 (sure, it’s not a supported combination, but it complicates development)</div></div></blockquote><div class=""><br class=""></div><div class="">I'm not sure what's the issue you're describing here.</div><div class="">qemu-kvm-ev is 2.6.0-27.1 being 2.6.0-27 +2 patches (rebranding and dep fixing) so it's not the same release. Also qemu-kvm-ev is supposed to provide qemu-kvm-rhev.</div></div></div></div></div></blockquote><div><br class=""></div>yes, and when you have qemu-kvm-rhev with ovirt repos it will replace all -rhev packages with -ev because it thinks it’s newer. Not a big deal as indeed it is the same, but it confuses people…</div><div><br class=""></div><div>Thanks,</div><div>michal</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div class=""><br class=""><blockquote type="cite" class=""><div class=""><span class=""><div dir="ltr" class=""><div class="gmail_extra"><br class=""></div><div class="gmail_extra">For having a qemu-kvm-ev version always aligned with CentOS release I would suggest to run:</div><div class="gmail_extra">"yum install centos-release-qemu-ev" on your CentOS hosts.</div><div class="gmail_extra"><br class=""></div><div class="gmail_extra">If you decide to use CentOS VIrt SIG provided packages on your hosts (excluding the oVirt engine host which still require oVirt repositories) I would suggest to remove ovirt-release rpms and <span style="font-size:12.8px" class="">/etc/yum.repos.d/ovirt-*.</span><span style="font-size:12.8px" class="">r<wbr class="">epo and then run:</span></div><div class="gmail_extra"><span style="font-size:12.8px" class="">"yum install centos-release-<wbr class="">ovirt40".</span></div><div class="gmail_extra"><span style="font-size:12.8px" class=""><br class=""></span></div><div class="gmail_extra"><span style="font-size:12.8px" class="">this will add as dependencies:</span></div><div class="gmail_extra"><span style="font-size:12.8px" class=""><div class="gmail_extra">Requires: centos-release-virt-common</div><div class="gmail_extra">Requires: centos-release-qemu-ev</div><div class="gmail_extra">Requires: centos-release-gluster37</div><div class=""><br class=""></div></span></div><div class="gmail_extra">providing the latest gluster 3.7 and latest qemu-kvm-ev for your hosts.</div><div class="gmail_extra"><br class=""></div><div class="gmail_extra">Having both oVirt repos and Virt SIG repos enabled should still work being both the repos built from the same sources but it's not recommended.</div><div class="gmail_extra"><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div class="m_-7437885037108402238gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class="">Sandro Bonazzola<br class="">Better technology. Faster innovation. Powered by community collaboration.<br class="">See how it works at <a href="http://redhat.com/" target="_blank" class="">redhat.com</a></div></div></div></div></div></div></div></div>
</div></div></span><span class="">
______________________________<wbr class="">_________________<br class="">Users mailing list<br class=""><a href="mailto:Users@ovirt.org" target="_blank" class="">Users@ovirt.org</a><br class=""></span><a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank" class="">http://lists.ovirt.org/<wbr class="">mailman/listinfo/users</a><br class=""></div></blockquote></div><br class=""></div></blockquote></div><br class=""><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class="">Sandro Bonazzola<br class="">Better technology. Faster innovation. Powered by community collaboration.<br class="">See how it works at <a href="http://redhat.com/" target="_blank" class="">redhat.com</a></div></div></div></div></div></div></div></div>
</div></div>
</div></blockquote></div><br class=""></body></html>