Your message dated Thu, 24 Mar 2022 17:33:24 +0100
with message-id <[email protected]>
and subject line Re: Bug#1006811: mirror submission for mirror.parsdev.com
has caused the Debian Bug report #1006811,
regarding mirror submission for mirror.parsdev.com
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.)
--
1006811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006811
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.parsdev.com
Type: leaf
Archive-architecture: amd64 arm64 armhf i386
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: Parsdev <[email protected]>
Country: IR Iran, Islamic Republic of
Location: Tehran
Sponsor: ParsDev https://parsdev.com
Trace Url: http://mirror.parsdev.com/debian/project/trace/
Trace Url: http://mirror.parsdev.com/debian/project/trace/ftp-master.debian.org
Trace Url: http://mirror.parsdev.com/debian/project/trace/mirror.parsdev.com
--- End Message ---
--- Begin Message ---
Hi,
Our script detected some issues with the mirror:
o It seems your mirror is not up to date, having last updated on Sat, 05 Mar
2022 16:35:46 +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 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?
o Your mirror appears not to carry source packages.
To comply with the licenses of various pieces of software that you
distribute on that mirror, you will probably need to also include
sources.
To be listed as a Debian mirror in our mirror-list you MUST include
sources, e.g. by adding "source" as an included architecture in ftpsync.conf.
Feel free to resubmit once these are fixed.
Cheers,
Julien
On Sat, Mar 05, 2022 at 04:46:30PM +0000, Parsdev wrote:
> Package: mirrors
> Severity: wishlist
> User: [email protected]
> Usertags: mirror-submission
>
> Submission-Type: new
> Site: mirror.parsdev.com
> Type: leaf
> Archive-architecture: amd64 arm64 armhf i386
> Archive-http: /debian/
> Archive-rsync: debian/
> Maintainer: Parsdev <[email protected]>
> Country: IR Iran, Islamic Republic of
> Location: Tehran
> Sponsor: ParsDev https://parsdev.com
>
>
>
>
> Trace Url: http://mirror.parsdev.com/debian/project/trace/
> Trace Url:
> http://mirror.parsdev.com/debian/project/trace/ftp-master.debian.org
> Trace Url: http://mirror.parsdev.com/debian/project/trace/mirror.parsdev.com
>
--- End Message ---
