687
edits
Changes
Jump to navigation
Jump to search
Line 29:
Line 29: − + − Unless you are an expert with yum you are highly encouraged to reset your yum repository configuration to the defaults using the instructions found at [[:AddingSoftware#Restoring_Default_Yum_Repositories]].+ − + + + + + + + + + +
Updating from SME 7.1.x or earlier (view source)
Revision as of 18:50, 19 August 2007
, 18:50, 19 August 2007→Ensuring the correct yum repository configuration
==Cleanup Tasks==
==Cleanup Tasks==
===Ensuring the correct yum repository configuration===
==='''Ensuring the correct yum repository configuration'''===
'''IMPORTANT: All SME systems installed from ANY ISO prior to 7.2 need to have the yum repository configuration corrected!'''
SME updates assume that the default repositories are enabled, and that any 3rd party repositories you may have configured are
The ''default'' yum repository configuration changed with the release of SME version 7.1.1 in order to allow installation of unmodified and non-conflicting CentOS packages directly from the CentOS repositories.
The SME update process ''does not'' reconfigure your yum repositories automatically in order to preserve any existing custom configurations you have created. This means:
* Even if your server now says it is running SME 7.1.3 your system may not be up to date, and you may be missing vital updates from the CentOS repositories that will only be installed after correcting your yum repository configuration!
* You will STILL need to correct your yum repository configuration even after ''updating'' from the 7.2 CD.
* A new install from the SME 7.2 CD is the ''only''
Therefore, unless you are an expert with yum and have made specific sme-related customizations for some reason, you '''must''' reset your yum repository configuration to the SME defaults using the instructions found at [[:AddingSoftware#Restoring_Default_Yum_Repositories]] or your yum updates '''will''' fail sooner or later.
All SME updates assume that the default repositories are enabled, and that any 3rd party repositories you may have configured are
* disabled by default
* disabled by default
* created with appropriate "Exclude" paramaters
* created with appropriate "Exclude" paramaters