On 15 October 2017 at 12:12, Yaniv Kaul <ykaul(a)redhat.com> wrote:
It is created from the external resources (defined in reposync), so if
there's a new dep or anything (a packages moved from 'base' to
or the other way around), it'll fail (this is why we've re-enabled the
external repos - since we've failed to keep up with the changes).
This is due to white-listing, one way to handle that is just ensure the
include and exclude lists are always identical between 'base' and
In CI we have an extra layer of point-in-time mirrors we can use to
actually isolate upstream repo changes from the system, but we didn't
implement the code to consider changes to these repos as separate change
streams yet. This, of course will only become useful once we prevent the
VMs from bypassing this and going directly to the upstream repos.
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
| TRIED. TESTED. TRUSTED. | redhat.com/trusted