On Fri, Apr 22, 2016 at 04:04:17AM +0300, Anssi Johansson wrote: > 22.4.2016, 0.48, Chuck Anderson kirjoitti: > >>You could also try without --delay-updates, which also triggers this > >>requirement to know the full file list in advance. > > > >But not using --delay-updates means that the yum repo could be in an > >inconsistent/nonfuctional state until the sync finishes. That isn't > >good for a public mirror. > > If also using --delete-delay, the files to be deleted will be > deleted only at the end of sync, reducing the chances of anything > breaking. Although I see your point, I believe the base repositories > (os, updates, extras, fasttrack etc) would end up getting synced in > such a sequence that yum won't get confused. The repodata directory > tends to get synced last, and it is not harmful if there are .rpm > files on the mirror that are not yet referenced in the repodata. "tends to get synced last" isn't something to rely on. Instead, you could sync everything except the repodata, then do a 2nd sync of just the repodata.