Hi,
Yes, we have updated ftpsync on our mirror server
(opensource.nchc.org.tw or a.k.a free.nchc.org.tw), and is ready to
receive push mirror.
Now I'd like to ask the mirrors team where may we receive the push trigger?
Thank you very much.
Steven
On 3/24/2018 AM 11:49, Yao Wei wrote:
Hi,
You should update your ftpsync program first, which is here:
http://ftp.debian.org/debian/project/ftpsync/ftpsync-current.tar.gz
Also push mirror for ccTLD mirror seems to be necessary. You can
consider setting that up with mirrors.xtom.com.hk
<http://mirrors.xtom.com.hk> (this is what ftp.ntou.edu.tw
<http://ftp.ntou.edu.tw> do) or ask the mirrors team here for
receiving push from upstream.
Yao Wei
On Sat, 24 Mar 2018 at 09:28 Steven Shiau <ste...@nchc.org.tw
<mailto:ste...@nchc.org.tw>> wrote:
On 2018年03月14日 11:14, Yao Wei (魏銘廷) wrote:
> Package: mirrors
> Severity: wishlist
> X-Debbugs-CC: debian-mirr...@lists.debian.org
<mailto:debian-mirr...@lists.debian.org>, Steven Shiau
<ste...@nchc.org.tw <mailto:ste...@nchc.org.tw>>, Ceasar Sun
Chen-kai <cea...@nchc.org.tw <mailto:cea...@nchc.org.tw>>, Thomas
<tho...@nchc.org.tw <mailto:tho...@nchc.org.tw>>
>
> Hi,
>
> As stated in the debian-mirrors mailing list, NCHC wants to list
> ftp.tw.debian.org <http://ftp.tw.debian.org> as their primary
mirror:
>
> https://lists.debian.org/debian-mirrors/2018/03/msg00000.html
>
> Also, according to the mirror status webpage:
>
> https://mirror-master.debian.org/status/mirror-status.html
>
> NCHC needs to use ftpsync rather than typical rsync to sync the
mirror,
> because of lacking sitetrace.
Thanks. If we follow the doc
https://salsa.debian.org/mirror-team/archvsync/, is it a must to
receive
an update trigger for ftpsync? If so, which upstream do you recommend
and where is public key of that upstream?
Thank you very much.
Steven
>
> Yao Wei
--
Steven Shiau <steven _at_ stevenshiau org>
Public Key Server PGP Key ID: 4096R/163E3FB0
Fingerprint: EB1D D5BF 6F88 820B BCF5 356C 8E94 C9CD 163E 3FB0
--
Steven Shiau <steven _at_ stevenshiau org>
Public Key Server PGP Key ID: 4096R/163E3FB0
Fingerprint: EB1D D5BF 6F88 820B BCF5 356C 8E94 C9CD 163E 3FB0
