On 04/04/2012 06:53 AM, zxq9 wrote:
On 04/04/2012 03:31 PM, Eero Volotinen wrote:
yum --releasever=6.2 update did the trick.
2012/4/4 Eero Volotinen<[email protected]>:
tried normal "redhat way update", without any success:
yum upgrade
Setting up Upgrade Process
No Packages marked for Update
sorry for noise to the list..
Hi Eero,
I believe that using --releasever=N doesn't make a permanenent change.
You will need to set your release version to 6.2, 6x or 6rolling if
you want to be pulling from the 6.2 repos the next time you run yum --
otherwise you'll be puzzled why you're not getting updates.
I'm unsure if there is a more elegant solution, but I think the only
place to make that change permanent is by doing something like:
sed --in-place=.bak -e "s/6.1/6x/" /etc/redhat-release
Or do the equivalent by hand. But that might be a crude hack --
Someone else here please pipe up if there is a better way.
Or there is always:
alias yum="yum --releasever=6x"
Cheers
-z
I use the instructions in the URL below and tweaked the process a bit
for some local issues I have. I found that on some systems the rather
long list of packages it wants to update can cause yum to get a bit
confused. So I loop through the alphabet one letter at a time running
"yum -y --releasever=6.2 update a\*", then b\*, c\* etc. That keeps yum
happy. After that the only packages left are a few with capital letters
or numerals at the beginning of the package name. Also had an issue
with autofs, so I grab a copy of the new autofs rpm and update it
locally before beginning the process.
https://www.scientificlinux.org/documentation/howto/upgrade.6x
--
Stephen Berg
Systems Administrator
NRL Code: 7320
Office: 228-688-5738
[email protected]
