I think this is a misuse of the mirrors feature because you don't actually provide any mirrors. The same effect can be achieved if you just put those urls in list into the urls parameter to the fetchurl.

I think this is a misuse of the mirrors feature because you don't actually provide any mirrors. The same effect can be achieved if you just put those urls in list into the urls parameter to the fetchurl.

Oh. Will try this instead! Not sure though if this will also work for: urlPrefix

@veprbl While using urls does work, I cannot get urlPrefixes to work. As far as I understood this should point to the prefix which was used for the successful download of the packagesList. Any help here would be greatly appreciated.

Most of the mirrors suffer from the same problem: Deprecated versions will just be replaced with directories containing the readme pointing to vault.centos.org: http://ftp.ussg.iu.edu/linux/centos/7.3.1611/

I did find some mirrors for centos-vault, will add these.

Figured while we previously used both centos-6/ and centos-7/, there is actually also a plain mirror.centos.org/centos, which holds both of them.
I think this is now a pretty clean solution, e.g. compare:

• https://archive.kernel.org/centos-vault/
• http://vault.centos.org
• http://mirror.centos.org/centos/

Most of the mirrors suffer from the same problem: Deprecated versions will just be replaced with directories containing the readme pointing to vault.centos.org:
http://ftp.ussg.iu.edu/linux/centos/7.3.1611/

Yes, I think this is a very standard strategy: most mirrors provide only current versions which are also most popular. Fewer mirrors will have enough resources to also mirror all of the releases.

Nice catch with centos-{6,7}/ to centos/, indeed.

What's next here?