Your message dated Thu, 24 Mar 2022 17:15:14 +0100
with message-id <YjyZEoC/[email protected]>
and subject line Re: Bug#1003451: mirror submission for mirror.ihost.md
has caused the Debian Bug report #1003451,
regarding mirror submission for mirror.ihost.md
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.)


-- 
1003451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003451
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.ihost.md
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: iHost NOC <[email protected]>
Country: MD Moldova
Location: Chisinau
Sponsor: iHost https://ihost.md/
Comment: Web Hosting and Cloud since 2009




Trace Url: http://mirror.ihost.md/debian/project/trace/
Trace Url: http://mirror.ihost.md/debian/project/trace/ftp-master.debian.org
Trace Url: http://mirror.ihost.md/debian/project/trace/mirror.ihost.md

--- End Message ---
--- Begin Message ---
Hi,

there are some issues with the mirror:

o It seems your mirror is not up to date, having last updated on Tue, 16 Mar 
2021 11:00:11 +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
  tracefile in /debian/project/trace with its name).

o The tracefile 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 tracefile 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>.d.o sites).  Maybe change your config to sync from
  the site currently backing the ftp.<CC>.debian.org service you sync
  from?

Feel free to resubmit once this is fixed.

Cheers,
Julien

On Mon, Jan 10, 2022 at 11:52:11AM +0000, iHost NOC wrote:
> Package: mirrors
> Severity: wishlist
> User: [email protected]
> Usertags: mirror-submission
> 
> Submission-Type: new
> Site: mirror.ihost.md
> Type: leaf
> Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 
> kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
> Archive-http: /debian/
> Archive-rsync: debian/
> Maintainer: iHost NOC <[email protected]>
> Country: MD Moldova
> Location: Chisinau
> Sponsor: iHost https://ihost.md/
> Comment: Web Hosting and Cloud since 2009
> 
> 
> 
> 
> Trace Url: http://mirror.ihost.md/debian/project/trace/
> Trace Url: http://mirror.ihost.md/debian/project/trace/ftp-master.debian.org
> Trace Url: http://mirror.ihost.md/debian/project/trace/mirror.ihost.md
> 

--- End Message ---

Reply via email to