On Mon, Sep 26, 2016 at 8:56 PM, Eric Smith <spacewar(a)gmail.com> wrote:
On Sat, Sep 24, 2016 at 3:10 AM, Dan Horák <dan(a)danny.cz>
> the maintainer doesn't need to care about builds in secondary kojis,
> the koji-shadow script (started periodically from cron or manually)
> takes a list of finished builds from primary koji and builds them in
> the same order using the same buildroots as were used in primary koji.
On Sat, Sep 24, 2016 at 8:06 AM, Peter Robinson <pbrobinson(a)gmail.com> wrote:
> No, it's not for an end user, but the shadow process already mentioned
> recreates the details of those overrides based on the information
> about the build stored in the primary database so the shadow process
> will automatically generate the overrides and all needed bits when it
> mirrors the builds over.
> Basically just leave anything to do with < F-26 alone and it'll be sorted
Thanks to both of you for explaining. It looks like what you described
happened fine for my packages, but dnf in my F24 aarch64 install isn't
finding the package updates. Must be a local configuration problem.
The updates do come a little later, if you mention the actual package
with an issue I can see where in the pipeline it is.