DevHeads.net

mock slow to get new packages for Rawhide?

With the recent gcc 8 issues I've been trying to do some build tests on my
system but I keep getting
gcc-8.0.1-0.9.fc28 even after performing a --scrub=all instead of
gcc-8.0.1-0.13.fc28 which was built yesterday or even gcc-8.0.1-0.12.fc28
from the 9th...

What gives? It can't just be slow mirror propagation...

Thanks,
Richard

Comments

Re: mock slow to get new packages for Rawhide?

By Mikolaj Izdebski at 02/12/2018 - 08:44

On 02/12/2018 02:35 PM, Richard Shaw wrote:
Try with --enablerepo local.

There hasn't been any successful rawhide compose in a couple days.

Re: mock slow to get new packages for Rawhide?

By Richard Shaw at 02/12/2018 - 08:51

On Mon, Feb 12, 2018 at 7:44 AM, Mikolaj Izdebski < ... at redhat dot com>
wrote:

Ah! I didn't even think of it that way... So mock doesn't pull directly
from the buildroot. I guess most of the time that makes sense, you want to
have a (usually) known good snapshot or lots of builds would fail with the
normal Rawhide churn.

Thanks,
Richard

Re: mock slow to get new packages for Rawhide?

By Mikolaj Izdebski at 02/12/2018 - 08:56

On 02/12/2018 02:51 PM, Richard Shaw wrote:
Mock does pull from buildroot when you run it with "--enablerepo local"