[ovirt-devel] broken master: removal of release in spec requirements

[Francesco Romani]

----- Original Message -----
> From: "Nir Soffer" <nsoffer at redhat.com>
> To: "Yaniv Bronheim" <ybronhei at redhat.com>
> Cc: "devel" <devel at ovirt.org>, "Francesco Romani" <fromani at redhat.com>, "Yevgeny Zaspitsky" <yzaspits at redhat.com>
> Sent: Monday, August 29, 2016 12:14:49 PM
> Subject: Re: broken master: removal of release in spec requirements
> 
> On Sun, Aug 28, 2016 at 3:17 PM, Yaniv Bronheim <ybronhei at redhat.com> wrote:
> >
> > Hi,
> >
> > In https://gerrit.ovirt.org/#/c/62672 we removed the release from vdsm*
> > requirements. Although it sounds reasonable and quite safe, it was not.
> > In development env it causes mixup of versions when upgrading.
> 
> 
> I think this change was unneeded, as vdsm builds for different
> architectures use the *same* release:
> 
>     name-major.minor.bugfix-release.offset.githash
> 
> Unlike other packages using:
> 
>     name-major.minor.bugfix-release.timestamp.githash
> 
> So I don't see why this patch was needed.
> 
> Additionally, vdsm sub packages are tightly coupled, and using a package
> from different commit is *not* supported, as internal apis may always change.
> 
> So we should revert this patch.

Alright, here it is:

https://gerrit.ovirt.org/#/c/62922/1

bests,

-- 
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani