Hi Adam,
Thanks for the review. Both points are now addressed.
INFO_MAINTAINER was simply never set in our ftpsync.conf, so ftpsync did
not emit the line at all. It is set now, along with the other optional
fields:
Maintainer: Max <noc@ihost.md>
Sponsor: iHost <https://ihost.md/>
Country: MD
Location: Chisinau
Throughput: 10Gb
Agreed, and changed. We now sync from ftp.uni-sofia.bg, the site
currently backing ftp.bg.debian.org, so the trace reports the real
upstream:
Upstream-mirror: ftp.uni-sofia.bg
Both changes are live and a full ftpsync run has completed since, so the
current trace file should pass your checks:
http://mirror.ihost.md/debian/project/trace/mirror.ihost.md
For reference, the mirror details are unchanged from the original
submission:
Site: mirror.ihost.md
HTTP: http://mirror.ihost.md/debian/
HTTPS: https://mirror.ihost.md/debian/
rsync: rsync://mirror.ihost.md/debian
Architectures: amd64 arm64 source
Country: MD (Moldova)
Location: Chisinau, AS43588
Bandwidth: 10 Gbit/s
Updates: ftpsync, 4x daily
Contact: noc@ihost.md
This is currently the only up-to-date Debian mirror in Moldova.
Two things we would be glad to hear your opinion on, but which should
not hold up this submission:
1. We also mirror debian-cd on the same host and would be happy to be
listed for it:
http://mirror.ihost.md/debian-cd/
rsync://mirror.ihost.md/debian-cd
Should that go through this bug, or separately to
debian-cd@lists.debian.org?
2. If the mirror team ever finds it useful, we would be willing to pull
from one of the syncproxies instead: the host sits on a 10 Gbit/s
port and we already let other sites mirror from us over rsync. We are
equally happy to remain a leaf mirror pulling from ftp.uni-sofia.bg
if that is preferred.
Regards,
Maxim Macovei | Chief Executive Officer
a: 3 Tighina Street, MD2001, Chisinau, Moldova
p: +(373) 78 666-999
Control: tags -1 + moreinfo
Our automated checks noticed some issues with your setup:
o The trace file at
http://mirror.ihost.md/debian/project/trace/mirror.ihost.md
is missing some required information.
We expect at least the Maintainer and Upstream-mirror values to be
filled in, and your trace file is missing one or both of them.
o We recommend mirrors not sync directly from service aliases such as
ftp.<CC>.debian.org (only HTTP is guaranteed to be available at
ftp.<CC> sites). Maybe change your config to sync from
the site currently backing the ftp.<CC>.debian.org service you sync
from?
Regards,
Adam