Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#20827 - {mirror} request to become an authorized mirror
Attached to Project:
Arch Linux
Opened by Filippov Roman (xFilx) - Sunday, 12 September 2010, 17:05 GMT
Last edited by Roman Kyrylych (Romashka) - Thursday, 30 September 2010, 09:20 GMT
Opened by Filippov Roman (xFilx) - Sunday, 12 September 2010, 17:05 GMT
Last edited by Roman Kyrylych (Romashka) - Thursday, 30 September 2010, 09:20 GMT
|
Detailshello, i want to become an authorized mirror
* Mirror domain name: opgsff.info * Geographical location of the mirror: Russia, Moscow * Supported access method: ftp * URLs for the above access methods: Server = ftp://opgsff.info/$repo/os/$arch * Name of tier 1 mirror i am syncing from: aarnet.edu.au (Australia) * An administrative contact email: sia6911@gmail.com |
This task depends upon
Closed by Roman Kyrylych (Romashka)
Thursday, 30 September 2010, 09:20 GMT
Reason for closing: Deferred
Thursday, 30 September 2010, 09:20 GMT
Reason for closing: Deferred
so I am unwilling to include the mirror in the official list,
however you are free to add it to the Unofficial list: http://wiki.archlinux.org/index.php/Mirrors#Russia
BTW, why there is "Наши спонсоры:" text above FOSS projects' logos?
I do understand your frustration about this, so let me explain the reasons.
We have almost 90 active mirrors in the official list at the moment. It used to be more, but recently we removed about 20 of them for being not up to date etc.
The higher is the number of mirrors - the higher are risks of a mirror compromise (FTR, there was a case already), because package signing is not implemented yet.
Since we have switched to 2-tier mirror scheme more mirrors become outdated, which clearly shows that some admins don't even know that their mirror is not synced anymore.
For some mirrors there is no known email address, or nobody ever replies to any email.
We will continue to remove such mirrors to make the mirroring infrastructure more reliable.
Having as many mirrors as possible is not our goal, having a trusted list is.
As for yandex.ru mirror - I know there were issues with it in the past, however I am not aware of any issues now.
According to http://www.archlinux.org/mirrors/status/ the mirror is syncing fine, and I see no problems with the directory structure either.
If you can point to any problem you (or some other users) have with yandex.ru mirror - please open a bugreport about that, or write to arch-mirrors mailing list.