Topic: Maintenance Team Announcement - Recent YUM issues

[mrjhb3]

The Maintenance Team is pleased to announce the current direction for the SME 6.x update/maintenance process:

Lately there has been some confusion about the update/maintenance process for SME 6.x.  This e-mail tries to clear up some of that confusion.

A new yum rpm has been created and uploaded to the updates area.  If you already have yum installed, you should be able to get the newest version, by doing a - yum update - at the command line.  If you don't have yum installed, here are some links to get it:

http://no.longer.valid/phpwiki/index.php/Maintenance%20Process

http://mirror.contribs.org/smeserver/releases/6.0.1/updates-testing-common/i386

In the etc/yum.conf you should now notice five update repos.  Here is how things are currently laid out:

[os] - contents Frozen - Base released OS files

[common-updates] - for common packages installable across all 6.x
   versions, eg FL ones, most e-smith packages

[updates] - for version specific updates

[updates-testing] - for version specific packages that need testing

[updates-testing-common] - for common packages needing testing that are
   installable across all 6.x version, eg FL ones, most e-smith
   packages


All production level updates will either be in the updates or updates-common directories.

There are quite a few new updates that need to be tested in the updates-testing-common area.  Currently you will need to manually modify your /etc/yum.conf file and remove the remarks (#) from this section. Then do a:

yum update
/sbin/e-smith/signal-event post-upgrade
/sbin/e-smith/signal-event reboot

Everyone is urged to install the latest yum rpm and help us in testing these updates so they can be moved to released status.

We know the call has gone out before, but we are making it again.
Currently, there are about seven of us trying keep up the maintenance process for all 3 SME 6 versions, not including the developers.  We could really use some help and we could also use some help with trying to close the outstanding bugs.  This may get better after the upcoming elections.

Thanks,

John H. Bennett III
On behalf of The Maintenance Team

[mrjhb3]

An issue that someone ran into while doing the update.

[Steve Bush:[
I ran yum update, which updated my version of yum.  The yum.conf didn't change. I then ran "/sbin/e-smith/signal-event post-upgrade" and again the yum.conf stayed the
same, so I took a look in the /etc directory and found the default file at
/etc/yum.conf.rpmnew.

So, if anyone has yum installed they mwill need to replace their yum.conf with the default
one.
[End Steve Bush]

Interesting to hear that.  I tested this a few times on my 6.5RC1 test box and didn't run into that issue.  Thanks for the heads up, I'll test some more and see what I missed.  We have been looking into templating this file (it's mostly done) and adding an event to expand the template.  Hopefully those changes will make it into the next revision, so noone runs into the issue you have described.

Thanks,

JB

[teis]

Thanks a lot for this update  

[roytotman]

I just recently installed the yum updates rpm on a 6.01 SME,
did yum update
and post install
rebooted , Now I have no Http service..
Any Idea's??
Roy...

[mrjhb3]

I just recently installed the yum updates rpm on a 6.01 SME,
did yum update
and post install
rebooted , Now I have no Http service..
Any Idea's??
Roy...

The instructions in the link and in previous posts state to do this:
yum update
/sbin/e-smith/signal-event post-upgrade
/sbin/e-smith/signal-event reboot

not a post-install.  If you did a post-install, I don't know what issues that causes.  Can you verify which event you ran?

JB

[roytotman]

I appollogize for beeing so vague and miss using terms,
to clarify, here is what I did
downloaded yum rpm to my server
installed rpm  via rpm -uvh
yum update
/sbin/e-smith/signal-event post-upgrade
/sbin/e-smith/signal-event reboot
I also un commented the section for updates-testing-common area
it went through it's automated header D/L
and I rebooted.
I tried accessing server-manager, No Luck
Pinged ok, I was able to SSh in with Putty ,
Server-manager would not run from the command line, I tried to restard Httpd via
/etc/init.d/httpd restart
Got Cannot find path specified....?
Stumped...
Could be related to unsuccessful upgrade to php5, the server worked fine after several reboots post failed php upgrade, probably just going to reinstall...

[mrjhb3]

I hope it is related to a conflict between php4 and php5.  The post-upgrade event will expand a lot of the templates, so if you didn't remove anything in templates/etc/php.ini, then there may be a conflict.

After you re-install, please post back your results of the yum update process.

Thanks,

John Bennett