Hi,
so this is exactly the issue why we should have ovirt-engine-4.1.0 branch
even before 1st RC build.
Unfortunately
https://gerrit.ovirt.org/#/c/71001/ was merged by Tal, even
though it was targeted for 4.1.1.
So we have 2 options:
1. Revert the patch and rebuild engine again (safer, but time consuming)
2. Hope that we will not cause any huge issue (it probably won't, but you
know how it goes) and release 4.1.0 with vdsm-jsonrpc-java 1.3.8
And I really hope that there were not merged any other patches targeted for
4.1.1
Martin
On Thu, Jan 26, 2017 at 8:24 AM, Sandro Bonazzola <sbonazzo(a)redhat.com>
wrote:
*00:00:44.789* package: ovirt-engine-backend-4.1.0.3-1.fc24.noarch
from check-custom-fc24*00:00:44.789* unresolved deps: *00:00:44.789*
vdsm-jsonrpc-java >= 0:1.3.8
[sbonazzo@sbonazzo vdsm-jsonrpc-java] [vdsm-jsonrpc-java:ovirt-4.1]$ git
tag --list |grep 1.3
v1.3.3
v1.3.4
v1.3.5
v1.3.6
v1.3.7
We really need a test in check-patch.sh which build the rpms and install
them so we can detect these errors earlier.
Piotr please provide vdsm-jsonrpc-java v.1.3.8, thanks
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at
redhat.com
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel