Mirrors

From ArchWiki
Revision as of 07:01, 3 April 2010 by ZZyXx (Talk | contribs) (Combined listing by speed and status)

Jump to: navigation, search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.


Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어


External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Summary help replacing me
Updating and managing package mirrors
Related
pacman
reflector

Enabling a specific mirror

The preferred method is to uncomment the mirror in question in Template:Filename:

# Any
# Server = ftp://mirrors.kernel.org/archlinux/$repo/os/i686
  Server = http://mirrors.kernel.org/archlinux/$repo/os/i686

See #Mirror status and #List by speed for tools that help choosing mirrors.

Tip: Uncomment 5 favorite mirrors and place them at the top of the mirrorlist file. That way it's easy to find them and move them around if the first mirror on the list has problems. It also makes merging mirrorlist updates easier.

It is also possible to specify mirrors in Template:Filename. For the [core] repository, the default setup is:

[core]
Include = /etc/pacman.d/mirrorlist

To use the HostEurope mirror as a default mirror, add it before the Template:Codeline line:

[core]
Server = ftp://ftp.hosteurope.de/mirror/ftp.archlinux.org/core/os/i686
Include = /etc/pacman.d/mirrorlist

pacman will now try to connect to this mirror first. Proceed to do the same for [testing], [extra], and [community], if applicable.

Note: If mirrors have been stated directly in Template:Filename, remember to use the same mirror for all repositories. Otherwise packages that are incompatible to each other may be installed, like kernel26 from [core] and an older kernel module from [extra].

Mirror status

Check the status of the Arch mirrors and how updated they are by visiting: Mirrorcheck and/or Mirror status.

Optionally install Template:Package Official, an utility that generates a mirrorlist using Mirrorcheck's list. reflector is available in the community repo.

# pacman -S reflector

Or manually check how up-to-date a mirror is by:

  1. picking a server and browsing to "extra/os/";
  2. accesing http://www.archlinux.org/ in another browser tab or window; and
  3. comparing the last-modified date of the Template:Filename directory on the mirror to the [extra] date on the homepage, in the Package Repositories box to the right.

Sorting mirrors

If not using reflector, which has the ability to sort mirrors by both how updated they are and their speed, follow this demonstration of manual mirror sorting.

List by speed

Don't forget to take full advantage of using the local fastest mirror, which can be determined via the included python script, Template:Filename. Taking this in mind, use pacman to install Template:Package Official if not already present:

# pacman -S python 

Use Template:Codeline to switch to the Template:Filename directory:

# cd /etc/pacman.d

Backup the existing Template:Filename:

# cp mirrorlist mirrorlist.backup

Edit Template:Filename and uncomment mirrors for testing with rankmirrors:

# nano mirrorlist.backup

Optionally run the following Template:Codeline line to uncomment every mirror:

# sed '/^#\S/ s|#||' -i mirrorlist.backup

Finally, rank the mirrors. Operand Template:Codeline means only output the 6 fastest mirrors:

# rankmirrors -n 6 mirrorlist.backup > mirrorlist

Force pacman to refresh the package lists
After creating/editing Template:Filename, (manually or by using Template:Codeline) issue the following command:

# pacman -Syy
Tip: Passing two Template:Codeline or Template:Codeline flags forces pacman to refresh all package lists even if they are considered to be up to date. Issuing Template:Codeline whenever changing to a new mirror is good practice and will avoid possible issues.

Combined listing by speed and status

It is not a good idea to just use the fastest mirrors, since the fastest mirrors might be out of date. The preferred way would be to use #List by speed, then sorting those 6 fastest mirrors by their #Mirror status.

Simply visit either one or both #Mirror status links and sort them by the ones that are more up to date. Move the more up to date mirrors to the top of Template:Filename and if the mirrors are way out of date simply don't use those; repeat the process leaving out the outdated mirrors. So this ends up with a total of 6 mirrors that are sorted by speed and status, leaving out outdated mirrors.

When having mirror issues the above should be repeated. Or repeat once in a while even if not having mirror problems, to keep Template:Filename up to date.

using reflector

You can obtain reflector from the community repository:

# pacman -S reflector

It's recommended to have a backup of the mirrorlist:

# mv /etc/pacman.d/mirrorlist{,backup}

You can use reflector like this to retrieve the latest mirrorlist from the MirrorStatus page, filter the 8 most up-to-date mirrors, sort them by speed and overwrite the file /etc/pacman.d/mirrorlist:

# reflector -l 8 -r -o /etc/pacman.d/mirrorlist

Official mirrors

Note: This list is outdated; it is based on pacman-mirrorlist-20091206 and the latest release is 20100131.

Attention: Do not add new mirrors to the list below. If you want your mirror to be added to official list, file a feature request and wait for approval before listing it here. In the meantime add it to the #Unofficial mirrors list at the end of this page.

Global

Australia

Austria

Belgium

Brazil

Bulgaria

Canada

Chile

China

Czech Republic

Denmark

Estonia

Finland

France

Germany

Great Britain

Greece

Hungary

India

Indonesia

Ireland

Israel

Italy

Japan

Kazakhstan

Latvia

Lithuania

Netherlands

New Caledonia

Norway

Poland

Portugal

Romania

Russia

Spain

Sweden

Switzerland

Taiwan

Turkey

Ukraine

United States

Vietnam

Unofficial mirrors

These mirrors are not listed in Template:Filename.

Global

Belarus

Bulgaria

China

Germany

Great Britain

Malaysia

New Zealand

Norway

Poland

Russia

South Africa

Spain

United States

IPv6-ready mirrors

Troubleshooting

Out-of-sync mirrors: corrupted packages/file not found

Issues regarding out-of-sync mirrors pointed out in this news post may have already been sorted out for most users, but in the event that problems of this nature present themselves again, simply try to see if the packages are present in the [testing] repository.

After having synced with Template:Codeline, use this command:

# pacman -Ud $(pacman -Sup | tail -n +2 | sed -e 's,/\(core\|extra\)/,/testing/,' \
                                              -e 's,/\(community\)/,/\1-testing/,')

Doing so could help in any occasion were packages in the mirror haven't been synced to [core/extra], and are still residing in [testing]. It is perfectly safe to install from [testing] in this case since the packages are being matched by version and release numbers.

In any event, it is best to switch mirrors and sync with Template:Codeline than resorting to an alternate repository. However, all or some of the mirrors may at times be out-of-sync to some degree.

Using all mirrors

To emulate Template:Codelines behavior of going through the entire mirror list, use this script: Template:File