<rant>stupid recaptcha.... lost the lot... start again</rant>
Having breathed deeply for a minute or two, I'll try again.
Hi Mary
Thanks for the reply. Yes I have been through all the instructions on a 7.51 server today. The end result is that I now have a shiny 7.6 server and not the souped up 8.0 server I was expecting.
My question is because I am trying to review and work out if the reason for not getting an 8.0 upgrade is my misunderstanding or an issue or perhaps that one of the steps did not work as expected. To me it is not yet a bug report as I cannot provide anything other than the following.
Given your copy of the steps from that wiki page, I've entered some comments where I think my issue sits.
Starting from here:
db yum_repositories print | grep '^sme' | cut -d= -f1 | while read repo
do
db yum_repositories setprop $repo MirrorList \
http://distro.ibiblio.org/pub/linux/distributions/smeserver/mirrorlist/$repo-8
done
/etc/e-smith/events/actions/generic_template_expand yum-modify
** TH: I would expect at the end of this step that the repo's are set for 8.0 (both CentOS and SME)
#db yum_repositories print
shows that the -7 repo's for SME are all now -8 but
the CentOS repo's are all set for
http://vault.centos.org/4.9/ (which is correct for 7.6 I think, but not for 8.0)
I have compared to my 8.0 server which shows
http://mirrorlist.centos.org**
yum --enablerepo '*' clean all
yum --disablerepo '*' \
$(echo --enablerepo\ sme{os,updates,extras,addons}) \
upgrade
** this step above also appears to only call on the SME repo's and not the CentOS ones, so I am not clear what part the CentOS repo's play in getting me to 8.0 or not as is the case at the moment.
rm -f /var/lib/rpm/__db.00*
(Note zeros not O's)
rpm --rebuilddb
mv /home/e-smith/db/yum_repositories /home/e-smith/db/yum_repositories.pre8
/etc/e-smith/events/actions/initialize-default-databases
signal-event post-upgrade
signal-event reboot
** Or am I simply missing something painfully obvious?
Thanks
Tony
6 Replies
5961 Views