> --disablerepo=russianfedora-free-rawhide-source

The "exclude" option in fastestmirror plugin removes selected mirrors from all enabled repositories (it's not a "global" opt).  russianfedora-free-rawhide-source was disabled so the fastestmirror plugin didn't touch it.

> Enabling russianfedora-free-rawhide-source repository

yumdownloader notices that russianfedora-free-rawhide is enabled, so it enables *-source repo as well.  But the fastestmirror plugin has already run.  Just enable russianfedora-free-rawhide-source from the very beginning, and it should work as expected.

(In reply to comment #1)
> > --disablerepo=russianfedora-free-rawhide-source
> 
> The "exclude" option in fastestmirror plugin removes selected mirrors from all
> enabled repositories (it's not a "global" opt). 
> russianfedora-free-rawhide-source was disabled so the fastestmirror plugin
> didn't touch it.
This was stated as "and". So as you can see despite to "--disablerepo=russianfedora-free-rawhide-source" it was used in package search process.

Disable mirrors concerned to excluding yandex mirrors from all repos.
Fastestmirror plugin report what thay was excluded:
Excluding mirror: mirror.yandex.ru
Excluding mirror: spreader.yandex.net
...

but than yumdownloader fails from one of it:

Enabling russianfedora-free-rawhide-source repository
http://mirror.yandex.ru/fedora/russianfedora/russianfedora/free/fedora/development/rawhide/source/SRPMS/repodata/repomd.xml:
[Errno 14] curl#7 - "Couldn't connect"
Пробуем другое зеркало.
failure: repodata/repomd.xml from russianfedora-free-rawhide-source: [Errno
256] No more mirrors to try.

Yes, source repositories are usually disabled in their .repo files by default, so "--disablerepo=russianfedora-free-rawhide-source" has no effect.

The initialization order is:
1. use "enabled=0|1" from *.repo files
2. process "--{enable|disable}repo" commandline options
3. fastestmirror plugin runs and pings/orders/filters mirrors
4. "*-source" repos get enabled/disabled to match non-source repos
5. source packages are downloaded

If you want to use russianfedora-free-rawhide-source and have fastestmirror plugin to exclude some mirrors from it, use "--enablerepo=russianfedora-free-rawhide-source".

If you don't want to use this source repository, disable the corresponding non-source repo with "--disablerepo=russianfedora-free-rawhide".

> despite to "--disablerepo=russianfedora-free-rawhide-source" it was used in package search process.

See 4)

> concerned to excluding yandex mirrors from all repos.
> Fastestmirror plugin report what thay was excluded:
> Excluding mirror: mirror.yandex.ru
> Excluding mirror: spreader.yandex.net
> ..
>  * russianfedora-free-rawhide: ftp.us.unixeria.com

fastestmirror excludes mirrors from ENABLED repositories only.  The quoted messages just report that mirror.yandex.ru, spreader.yandex.net and some other mirrors were excluded from russianfedora-free-rawhide, and Yum will use ftp.us.unixeria.com as the "best" mirror for this repo.

I think swap 3 and 4 should resolve issue and allow fastestmirror plugin exclude repos there too?

*** This bug has been marked as a duplicate of bug 819229 ***

Sorry, closed wrong ticket.

This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.