On Mon, 20 Feb 2017, GloboTech wrote:
> Greetings,
>
> I had no feedback regarding this:
Hm. I thought I had replied to this via our issue tracker, sorry if you did
not receive the mail.
Here's the gist:
On Mon, 13 Feb 2017, GloboTech wrote in [#UDP-945-18342]:
> No we are not using ftpsync for the mirror syncrhonization but a custom bash
> script calling rsync, here is an extract:
>
> [root@mirror2 ~]# cat /scripts/sync_debian.sh
> #!/bin/bash
>
> /usr/bin/rsync -aqzHv --delete mirror.csclub.uwaterloo.ca::debian/
> /data/www/Debian/debian/
> /usr/bin/rsync -aqzHv --delete mirror.csclub.uwaterloo.ca::debian-security/
> /data/www/Debian/debian-security/
> /usr/bin/rsync -aqzHv --delete mirror.csclub.uwaterloo.ca::debian-backports/
> /data/www/Debian/debian-backports/
> /bin/echo `date` >
> /data/www/Debian/debian/project/trace/debian.mirror.globo.tech
>
>
> I've now added a file in /project/trace folder called
> debian.mirror.globo.tech, this file contains the date once the script
> has completed.
Unfortunately, single-pass rsyncs as yours are not suitable for
correctly mirroring Debian as they do not ensure proper ordering of
metadata file updates (Packages, Release files) and .deb files.
(Thus, updates by users on stable will likely break if stable changed
and you currently update your mirror, as will installs by users of any
suite on mirror runs.)
Please use ftpsync.
Also, -backports is obsolete, you can remove it.
--
| .''`. ** Debian **
Peter Palfrader | : :' : The universal
https://www.palfrader.org/ | `. `' Operating System
| `- https://www.debian.org/
