[mirror-admin] quick-fedora-mirror (Was: fullfiletimelist broken??)

[Chuck Anderson]

On Tue, May 17, 2016 at 04:27:13PM -0500, Jason L Tibbitts III wrote:
> >>>>> "KF" == Kevin Fenzi <kevin at scrye.com> writes:
> 
> KF> Sorry for the confusion here. I really hope you can take a look at
> KF> the script that tibbs has come up with (when ready) and provide
> KF> feedback.
> 
> For reference, we're talking about https://pagure.io/quick-fedora-mirror
> Some info and docs are there in the overview.

This concerns me:

    # We want to delete any files, symlinks or directories which exist
    # locally but which don't exist on the server.  If we do this
    # here, before the transfer, the directory mtimes will be correct
    # after the transfer.

Since deletes are being done before the rsync run, the repo will be in
an inconsistent state during the time period between these deletes and
the full rsync run.  Perhaps that is why you have this comment in
there:

       # XXX push these deletes down until after the big rsync run

Am I correct in assuming that if the deletes are moved to after the
big rsync run, that will cause directory mtimes to be wrong, which is
why they were moved to before the big rsync run in the first place?
And that it is critical that directory mtimes be correct after the
rsync transfer?

In order to reconcile these two opposing goals (keep mtimes correct,
don't delete before the rsync so we maintain repo consistency), how
about the following strategy:

- do the deletes after the full big rsync
- manually fixup the mtimes after the deletions, using the alldirs lists

--