Repositories Available Repositories for CentOS There are several repositories provided by CentOS and other 3rd party developers that offer software packages that are not included in the default base and updates repositories. These repositories have varying levels of stability, support and cooperation within the CentOS community. A line containing one of these options is recommended for each repository in each. This allows the administrator to more clearly specify whether a repository is or is not used for packages.
After any edits of these files, in order to clear any cached information, and to make sure the changes are immediately recognized, as root run: This repository is shipped with CentOS and is enabled by default. This repo will change CentOS so that it is not exactly like the upstream provider's content. They have not been tested by the upstream provider and are not available in the upstream products.
This repository is shipped with CentOS but is not enabled by default. Popular packages from this repository include: CentOS-Fasttrack - Bugfix and enhancement updates are issued from time to time between update sets that may be rolled into the next update set by the upstream provider. No repo config is provided by default. Tools like oprofile, crash, and systemtap require debuginfo packages. These packages are found at http: This repository only has content in the time period between an upstream release and the official CentOS release.
It should be considered beta quality, and is not recommended for production servers. Having said that, it may be something you do want since it often contains security fixes from the newer point release that have been built but not yet released.
The content of this repo is exactly what will be made publicly available when the ISO images have been built and tested. The idea is to provide sysadmins with the content of the new point release to use on running servers without needing to wait the extra week or two for the ISO images to be made available. It contains newer versions of various programs that can be installed alongside existing older packages and invoked by using the scl command. At the time of writing, the repository contains packages for devtoolset 3, 4 and 6 no idea what happened to devtoolset-5 , a couple of newer git versions, httpd24 2.
Many of these are also supplied by other repos as drop-in replacements for the distro versions and you may want to review a relatively unbiased comparison of how SCL differs from those other repositories here Third Party Repositories WARNING: These repositories are not provided nor supported by CentOS.
The CentOS project has no control over these sites. Many have their own mailing lists, IRC channels, issue trackers, etc. If you are considering using a 3rd Party Repository, then you should seriously consider how to prevent unintended 'updates' from these side archives from over-writing some core part of CentOS. One approach is to only enable these archives from time to time, and generally leave them disabled.
Community Approved Repositories These repositories are frequently recommended by the community, are usually well maintained and provide a substantial number of additional packages to CentOS.
They are still not associated with CentOS but are independent. The above warnings about updates and priorities should still be heeded. Packages should not replace base, although there have been issues around point releases in the past. The epel-release package is included in the CentOS Extras repository that is enabled by default. Support available on Freenode in epel, on mailing lists , and its issue tracker. Newer kernels are also available. Please see the site for additional details.
NET Repositories - see http: This repo is for CentOS 6 only. May replace base packages if the "backports" repo is enabled. A repo config is available at: As of May 2nd when last checked, the main repo had no packages that had been updated in or and only two packages from the testing repo where updated after so care should be taken with this one as you may be using packages with known security vulnerabilities. Do not attempt to use this repo on CentOS 7, it will not work.
It contains a lot of graphical programs such as Ardour, but also text based apps like Cone. Requires EPEL and should not overwrite base.
It is sponsored by internal work at Rackspace but officially unsupported. See their Client Usage Guide to install the ius-release package to configure the repo.
See their FAQ which frankly discusses pros and cons. It is designed to be used in combination with the EPEL repository. Full details can be found on the home page. Again, this is not for use on CentOS 7. GhettoForge - see http: Packages that overwrite base should only be in the [gf-plus] repository.
Please see the usage section of the GhettoForge wiki for information on how to maintain sanity when using the gf-plus packages. The goal is to provide high quality packages for Enterprise Linux releases 6 and 7 that are not presently in the base EL package sets nor in other third-party repositories. RPMfusion Repository - See http: Known to replace base packages. Mailing list for RPMfusion users. Some users have reported success with these packages but caution is advised.
Be aware that only samba versions up to 4. EL5, 6, and 7 yum repositories are available. They have their own support resources to which any Trinity questions should be directed. Remi Repository - See http: He's also got an FAQ at http: Note that this is a collection of repos, and using the -safe series will ensure that nothing from the base CentOS Linux distro is overwritten or replaced. However, be aware that this repo does not play nicely with other third party repos - for example, Remi's packages contain Obsoletes: This may not be the desired behaviour and you should be careful with enabling this repo for that reason.
Known Problem Repositories These repositories are known to cause issues due to large scale of replacement of base packages with little or no warning. Use extreme caution if you choose to use these repositories, and consider using an alternative above. Atomic Repo - See https: Some additional packages that may not be available elsewhere include hunspell, snort, and zabbix.
They also provide Plesk. Atomic will replace many core packages as configured when installed. Many CentOS users have had problems after enabling this repo, as a forum search will reveal.
Even removing packages installed from this repository may leave the system in an unusable state. Enabled by default, contains lots of packages that overwrite base packages. That includes various system libraries including libcurl and will break yum as soon as it's installed!
Be particularly careful about the City-Fan repo as they enable their repo by default when installed. City-Fan will replace many core packages as configured when installed and those packages often have a different structure than the CentOS ones making them difficult if not impossible to remove cleanly.
Do NOT do this. A person asked in the IRC channel about some external third-party 'yum' additional repository instructions. It is a bad idea to follow some external documents. A couple of examples of incorrect repo configs: Use of hard-coded version and architecture: Compare this, to the more proper: The 'hard coded' approach limits it to only be 'correct' for CentOS 4 on an i platform.
Mixing Fedora repositories with CentOS oriented repositories: Fedora repositories are not likely to be compatible with CentOS. Repositories for other Enterprise Linux distros derived from the same upstream sources are more likely to be compatible, but should still be used with care. Using the wrong version of a repository for your version of CentOS! When installing a repo, please make sure it is for the proper version, otherwise unexpected behavior will occur. Please do NOT follow such examples.
Use a critical eye and some thought to see what is proposed before adding to and possibly breaking your system's 'yum' configuration.