Both us and ds rpms were built. Is it possible to check why new version was
not published to the repo?

9 gru 2016 18:07 "Martin Perina" <[email protected]> napisaƂ(a):

> Piotr, are you able to publish new vdsm-jsonrpc-java 1.2.10 into
> ovirt-4.0-snapshot repo [1]? Or only someone from integration team can do
> that?
>
> Thanks
>
> Martin
>
> [1] http://plain.resources.ovirt.org/pub/ovirt-4.0-snapshot/rpm
>
>
> On Fri, Dec 9, 2016 at 4:54 PM, Yaniv Kaul <[email protected]> wrote:
>
>> See [1]:
>>
>> + yum install --nogpgcheck -y --downloaddir=/dev/shm ovirt-engine 
>> ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*'*13:55:25* Error: 
>> Package: 
>> ovirt-engine-backend-4.0.7-0.0.master.20161208233116.git3dff5ce.el7.centos.noarch
>>  (alocalsync)*13:55:25*            Requires: vdsm-jsonrpc-java >= 
>> 1.2.10*13:55:25*            Available: 
>> vdsm-jsonrpc-java-1.2.9-1.20161208102442.gite5c0c8e.el7.centos.noarch 
>> (alocalsync)*13:55:25*                vdsm-jsonrpc-java = 
>> 1.2.9-1.20161208102442.gite5c0c8e.el7.centos
>>
>>
>>
>>
>> [1] 
>> http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x86_64/319/console
>>
>>
>> _______________________________________________
>> Devel mailing list
>> [email protected]
>> http://lists.phx.ovirt.org/mailman/listinfo/devel
>>
>
>
_______________________________________________
Devel mailing list
[email protected]
http://lists.phx.ovirt.org/mailman/listinfo/devel

Reply via email to