[ https://ovirt-jira.atlassian.net/browse/OVIRT-1441?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-1441: ------------------------------------- So again, I see 3 types of packages: 1. 3rd party packages for which an RPM is available for an official and reliable source (e.g. CentOS, Fedora) 2. 3rd party packages where there is no RPM avialable and we want to ship an RPM with oVirt 3. oVirt packages For the 1st case we setup the 3rd party repo in the '*release*.rpm'. For the 3rd case the package is usually built and managed by the CI systems. We seem to be dealing with the 2nd case here, the solution for that was to make an oVirt "adapter" source repo with a usual build-artifacts job that creates or downloads the RPM. One is runs, the rest works just like for packages of the 3rd case. Since we want to track and gate changes to oVirt, the "adapter" repo should be made so that is downloads a very specific version of the 3rd party package. That way getting an updated version of the upstream package requires a patch to the adapter repo which can be tracked and gated. See also discussion in OVIRT-1299. -- This message was sent by Atlassian JIRA (v1000.1045.3#100046)