[mirror-admin] missing file in 12-Alpha

[Carlos Carvalho]

Jesse Keating (jkeating at redhat.com) wrote on 23 August 2009 10:24:
 >On Sat, 2009-08-22 at 13:13 -0300, Carlos Carvalho wrote:
 >> Jigdo is *very* useful for full mirrors because they already have all
 >> packages and don't need to pull the same thing again in the iso. So
 >> please keep them.
 >
 >How many mirrors are actually using them?  So far, I've only head of
 >you.

Since you say below that you won't change it I had to run the normal
rsync. It pulled just the isos, almost 29GB, and took almost 5h. So
it's a significant hit.

 >Most mirrors I hear from don't want to take the time to do
 >something manual, they just want rsync to take care of everything, even
 >if it means some "wasted" bandwidth.  It means they can setup a cron job
 >and walk away, never having to look back and touch anything.

When you have a fast connection with upstream life is easy. Not the
case here however... Further, it's not difficult because it's
automated; I just put the exclude in the config, rsync, run the script
to create the isos, and remove the exclusion. The script does
everything, including pulling the timestamp/perms from upstream and
setting them so rsync won't try to update them.

 >> Would it be possible that a few files were changed after you created
 >> the jigdo/templates? Could you try to recreate them?
 >
 >I really can't think of any files that would have changed.
 >Unfortunately it's not easily possible for me to re-create the jigdo
 >files and re-upload them, in time for the release.  The working copy on
 >the compose system had to be scrubbed to make room to compose the live
 >images.  It seems really really stupid that Jigdo will know that it's
 >missing files, but won't tell you /which/ files its missing.  If I knew
 >which files, I might be able to "rescue" the files or something.

I think it wouldn't help because the newer version is the one that
should be on the isos. So you'd have to really re-create them.

--