Your message dated Fri, 22 Mar 2024 16:38:55 +0000
with message-id
<42f177b5accc7a0380ebd9e3a1db19ca46b76c85.ca...@adam-barratt.org.uk>
and subject line Re: Bug#1062780: mirror listing update for debianmirror.nkn.in
has caused the Debian Bug report #1062780,
regarding mirror listing update for debianmirror.nkn.in
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1062780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062780
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mirrors
Severity: minor
User: [email protected]
Usertags: mirror-list
Submission-Type: update
Site: debianmirror.nkn.in
Archive-architecture: amd64 arm64
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: S.Gopinath <[email protected]>
Country: IN India
Comment: There was a problem in IPv6 earlier and this is now rectified. Please
update it
Trace Url: http://debianmirror.nkn.in/debian/project/trace/
Trace Url: http://debianmirror.nkn.in/debian/project/trace/ftp-master.debian.org
Trace Url: http://debianmirror.nkn.in/debian/project/trace/debianmirror.nkn.in
--- End Message ---
--- Begin Message ---
Hi,
On Sat, 2024-02-03 at 09:47 +0000, S.Gopinath wrote:
> Site: debianmirror.nkn.in
> Archive-architecture: amd64 arm64
> Archive-http: /debian/
> Archive-rsync: debian/
> Maintainer: S.Gopinath <[email protected]>
> Country: IN India
Our automated checks noticed some issues with your mirror:
o It seems your mirror is not up to date, having last updated on Wed, 06 Mar
2024 20:37:08 +0000
o The latest ftpsync versions come with a wrapper script called
ftpsync-cron, which is intended to be run out of cron every hour or so
(at a randomish offset). The script monitors your upstream mirror,
and if there was an update triggers a full sync using ftpsync.
You might want to give it a try.
NOTE: This requires having your upstream mirror name set correctly to
a specific mirror which is also correctly configured (and thus has a
trace file in /debian/project/trace with its name).
o The trace file at
http://debianmirror.nkn.in/debian/project/trace/debianmirror.nkn.in
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?
I'm going to close this request now, but please feel free to resubmit
in future.
As an additional note, is there a reason that you only mirror amd64 and
arm64? In general, users will expect mirrors to carry all
architectures.
Regards,
Adam
--- End Message ---
