Package: mirrors
User: mirr...@packages.debian.org
Usertags: mirror-problem may-auto-close
Control: submitter -1 mirr...@debian.org

Hi!

I noticed that mirrors.xmission.com's mirrorrun frequency is somewhat weird.

This is the timestamps of tracefiles:
 2017-09-07 02:03:30+00
 2017-09-07 10:41:54+00
 2017-09-07 18:13:13+00
 2017-09-07 19:10:28+00
 2017-09-08 00:10:45+00
 2017-09-08 07:42:36+00
 2017-09-08 10:46:49+00
 2017-09-08 14:52:30+00
 2017-09-08 17:02:39+00
 2017-09-08 23:43:43+00
 2017-09-09 03:09:09+00
 2017-09-09 05:43:19+00
 2017-09-09 09:46:31+00
 2017-09-09 10:39:46+00
 2017-09-09 13:29:34+00
 2017-09-09 17:03:15+00
 2017-09-10 00:11:29+00
 2017-09-10 03:43:38+00
 2017-09-10 07:12:19+00
 2017-09-10 16:53:19+00
 2017-09-11 12:42:05+00
 2017-09-11 20:10:44+00
 2017-09-12 10:17:20+00
 2017-09-12 20:56:58+00
 2017-09-13 11:07:30+00
 2017-09-13 21:05:17+00

Status: 
https://mirror-master.debian.org/status/mirror-info/mirrors.xmission.com.html

The Debian archive updates four times a day.  Maybe you want to sync with that?


The latest ftpsync version has an ftpsync-cron wrapper that is designed to run
every half hour or hour or so, and which monitors upstream's tracefile and
triggers a mirrorun if upstream changed.  It's still experimental but maybe you
want to give it a try anyhow.

Switching to a modern ftpsync to mirror Debian would be appreciated (even
without using the -cron wrapper) as it ensures updates are done in the correct
order so apt clients don't get confused.   In particular, it processes
translations, contents, and more files that have been added to the archive in
recent years in the correct stage.  It also should produce trace files that
contain more information that is useful for us.

  http://ftp.debian.org/debian/project/ftpsync/ftpsync-current.tar.gz

Cheers,
-- 
                            |  .''`.       ** Debian **
      Peter Palfrader       | : :' :      The  universal
 https://www.palfrader.org/ | `. `'      Operating System
                            |   `-    https://www.debian.org/

Reply via email to