CentOS 5.7 Release Warning

[darmock]

Hi folks

Centos 5.7 has been release upstream I am afraid and if you do a yum update you will be the proud owner of centos 5.7 which is UNTESTED AND MAY BRICK YOUR SYSTEM.

Generally we like to test things prior to you all trying to use this however there it is. So for the brave souls who upgrade give it a try and let us know if you could.

BE PREPARED TO REINSTALL YOUR SYSTEM HOWEVER AND MAKE SURE YOU HAVE VERIFIED BACKUPS PRIOR TO EXPERIMENTING.

Once we have tested this out we will generate a new ISO and release PIAF 1757 and shelve further development of 1756.

BTW PIAF 2.0.6.1 is coming along and MAY enter alpha testing next month. Aside from centos 6.1 it brings some new security and encryption technology to the party.


best regards to all


Tom

 

[randy7376]

Tom,

Is there a way to prevent the initial install from going directly to CentOS 5.7?

Running a default Purple install from the PBXIAF 1.7.5.6.3 CD (23 July 2011) brings the system up to CentOS 5.7 without any special interaction.

In other words, new installs are at 5.7, by default, it would seem.

 

[darmock]

I will have to modify the payloads to do this I am afraid. I will look into how to accomplish this.

Now that you mention it yes it would install the 5.7 stream but it is still running with the 5.6 kernels as we by default do not allow the kernels to be upgraded. Usually we have some problems with the kernels as opposed to anything else. The fact that it installs the 5.7 rpms sans kenels during a new install and everything seems to work indicates that the 5.7 tree is benign. Will look at it soon as I can although I am in the midst of building a new PIAF dev machine so it will take a while. The old one was kind of tired and the hamsters all died........


Tom

 

[darmock]

For existing installs to prevent updating your version of centos to 5.7 do not run yum update either from the command line or as part of update-source.

You can also edit the

/etc/yum.repos.d/CentOS-Base.repo file and add to the lines that start with

exclude=

add the following at the end of these lines

centos-release*

When it is safe you can remove this entry and then do a yum update from within update-source which is the only recommended way of accomplishing this process.


We will be modifying all of the payloads shortly so this line is added for new installs of all colors.


Tom

 

[darmock]

Well cant find anything wrong with 5.7 at the moment. We are updating a number of our programs to take advantage of 5.7 and PIAF 1757 ISO is well on the way to alpha testing.

For the moment 5.7 looks fine. However I would wait till our 5.7 iso comes out along with the updated programs to be sure.


Tom

 

[jucha]

I tryint to udate from 1.8.0 to 1.8.5

After yum update. No warning to update to 5.7

I am getting
make: *** [menuselect.makeopts] Error 255



Added asterisk info to registry
<<>> Running make
menuselect/menuselect --check-deps menuselect.makeopts
<<>> Running make install
menuselect/menuselect --check-deps menuselect.makeopts
<<>> Now checking to see if asterisk compiled correctly
EXPERIMENTAL BUILD VERIFICATION
<<>>ERROR Asterisk purple seems to have failed to compile!
This install will continue but you may have to hand
compile Asterisk! Please check the /var/log/update-source.log
Press ENTER to continue! PLEASE NOTE THIS NOTIFICATION MAY BE
IN ERROR AS THIS IS AN EXPERIMENTAL TEST

 

[darmock]

R U using update-source? If so and it is failing try the OPTIONAL make menuconfig and ensure you enable all of the cdr stuff then save things.

Also we have no control over yum update so there is no solution for the warning

Tom

 

[ErikU]

I updated by accident and there doesn't seem to be any problem.