Your message dated Fri, 22 Mar 2024 16:31:00 +0000
with message-id
<2a341b80a1548463c5aefd6a1eb9de9f0963fa20.ca...@adam-barratt.org.uk>
and subject line Re: Bug#1064393: mirror submission for mirror.neftm.ru
has caused the Debian Bug report #1064393,
regarding mirror submission for mirror.neftm.ru
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.)
--
1064393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064393
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mirrors
Severity: wishlist
User: [email protected]
Usertags: mirror-submission
Submission-Type: new
Site: mirror.neftm.ru
Archive-architecture: amd64
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: https://neftm.ru <[email protected]>
Country: RU Russian Federation
Location: Moscow
Trace Url: http://mirror.neftm.ru/debian/project/trace/
Trace Url: http://mirror.neftm.ru/debian/project/trace/ftp-master.debian.org
Trace Url: http://mirror.neftm.ru/debian/project/trace/mirror.neftm.ru
--- End Message ---
--- Begin Message ---
Hi,
On Wed, 2024-02-21 at 13:14 +0000, https://neftm.ru wrote:
> Submission-Type: new
> Site: mirror.neftm.ru
> Archive-architecture: amd64
Our automated checks noticed some issues with your mirror:
o It seems your mirror is not up to date, having last updated on Fri, 01 Mar
2024 08:59:28 +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://mirror.neftm.ru/debian/project/trace/mirror.neftm.ru
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?
The current state of your mirror is confusing - you appear to have some
files that were updated today, but your tracefile at
https://mirror.neftm.ru/debian/project/trace/mirror.neftm.ru says:
Fri Mar 1 08:59:28 UTC 2024
Date: Fri, 01 Mar 2024 08:59:28 +0000
Date-Started: Fri, 01 Mar 2024 08:55:26 +0000
Archive serial: 2024030102
which is very out of date now.
As an additional query, is there a reason that you only mirror amd64
packages? In general, users will expect mirrors to carry all
architectures.
I'm going to close this request now, but please feel free to resubmit
in future.
Regards,
Adam
--- End Message ---
