FC4 Plesk 8 And would like php 5.1.4

[audiopleb]

and everything works fine?

 

[Ronaldve]

Yes everyting works fine, no broken websites or other problems atm.

 

[audiopleb]

Sounds encouraging.

Dont suppose you errr.. would ummm sort of note down err... exactly what you did and umm... sort of tell me what to do could you?

Is that a cheeky thing to ask?

 

[Ronaldve]

I first added the atomic-bleeding repository to my yum config.
you have to do this in yum.conf or make a atomic-bleeding.repo file in /etc/yum.repos.d/.
You have to find out your self what way you are using.

you have to add this for example:
[atomic-bleeding]
name=Atomic Rocket Turtle - $releasever - Atomic bleeding RPMS
baseurl=http://3es.atomicrocketturtle.com/atomic-bleeding/art/$releasever/
enabled=1

Then on the commandline just do 'yum check-update' and see if php 5.1.6 is mentioned in the list of possible updates.

If so, you have to do 'yum update php*' to update.
If not, you have to check your yum config

When it's ready just do 'service httpd restart' and your done.

 

[audiopleb]

ahh

Right, great thank you. I'll have a bash at it now. Thank you.

 

[audiopleb]

i have done that and i get this

i have done that and i get this:

Repository extras is listed more than once in the configuration
Repository updates-released is listed more than once in the configuration
Repository base is listed more than once in the configuration
Setting up repositories
Reading repository metadata in from local files


Any ideas?

 

[JustinCarmony]

I get this message while trying to update:

Error: Missing Dependency: php <= 5.1.0 is needed by package php-sqlite2


What do you suggest?

Justin

 

[Ronaldve]

when you get messages like 'Repository extras is listed more than once in the configuration' it means you have more than one repo with the same name between the [ ] brackets.

You could try to exclude php-sqlite2 from the update. use 'yum update php* --exclude=php-sqlite2'
or do 'yum update php php-ldap php-mysql ...'with all the packages you want to update

 

[atomicturtle]

What you want to avoid is just pasting every channel on the page into your yum.conf. The only channels you want to add in are [atomic] and [atomic-bleeding].

Your version of php-sqlite2 is probably not going to be compatible with php 5.1, I recommend removing that before you try to upgrade php.

 

[audiopleb]

My stupid hosters set my box up weird

I have resolved all my problems.

The hosters had left duplicate entries for repos in conf and .repo files which is why yum was screwing up.

So i ran yum install php and it came back with the packages from atomic channel and said i could install it.

Then luckily i realised my server is x86_64 and stopped myself from installing the php 5.1.6 as it was for i386.

So predictably my question now is...does anyone have php 5.1.4 / 5.1.6 for x86_64 that would work on Fedora Core 4 with Plesk 8.0.

If i were a betting man i would say the answer is going to be no.

Thanks for all the help i have had from the people on this board. I really appreciate your time.

 

[atomicturtle]

Unfortunately I dont have a 64-bit box to do any development on at this time.

 

[waruna]

Need PHP, not MySQL

When I try this on FC4 with PLESK 8.0.1
It is going to upgrade MySQL to version 5.
I do not want to upgrade MySQL since it is not recommended with PLESK 8.
How can I upgrade php with out upgrading MySQL?

yum --enablerepo=atomic-bleeding update php

Dependencies Resolved

=============================================================================
Package Arch Version Repository Size
==============================================
Updating:
php i386 5.1.6-1.rhfc4.art atomic-bleeding 5.9 M
Installing for dependencies:
mysql-compat i386 5.0.24a-3.rhfc4.art atomic-bleeding 1.7 M
php-pdo i386 5.1.6-1.rhfc4.art atomic-bleeding 153 k
Updating for dependencies:
mysql i386 5.0.24a-3.rhfc4.art atomic-bleeding 3.9 M

mysql-server i386 5.0.24a-3.rhfc4.art atomic-bleeding 10 M
php-gd i386 5.1.6-1.rhfc4.art atomic-bleeding 315k
php-imap i386 5.1.6-1.rhfc4.art atomic-bleeding 104 k
php-mbstring i386 5.1.6-1.rhfc4.art atomic-bleeding 1.2 M
php-mysql i386 5.1.6-1.rhfc4.art atomic-bleeding 261 k
php-pear noarch 1:1.4.9-1.rhfc4.art atomic-bleeding 357 k
php-xml i386 5.1.6-1.rhfc4.art atomic-bleeding 289 k

=====================================

 

[Ronaldve]

I think this will work:
yum --enablerepo=atomic-bleeding update php --exclude=mysql

Though at my server I did not had to install MySQL 5 when updating to PHP 5.1.6

 

[atomicturtle]

I completely forgot that I'd been working on mysql 5.0 a few weeks ago

Although mysql 5 is in that channel, I did not link php 5.1.4 against it, so its perfectly safe to exclude that from the update.

 

[waruna]

Updating to php 5.1.6, not 5.1.4
safe to exclude mysql for it as well ?

PHP 5.2 released. When will we see it on ART.

Thanks.

 

[atomicturtle]

Already done, I just havent posted it to the archive yet.

 

[Ronaldve]

What are you waiting for then
Do you seen any chance of makeking an php-imagick package for php 5.2.x?

 

[fromvega]

In your homepage you said:

[atomic-bleeding] / [atomic-unstable] - untested, non-production packages with frequently zero testing, and known unresolvable compatibility issues created by ART. You shouldn't be here unless you are me.

So what does it mean? Does it mean that php5.1.6 package isn't stable?

Thank you!

 

[atomicturtle]

In a PSA environment, no its not stable.

It really depends on the package. The general rules are maintenance releases go into [atomic-testing] for testing. If all goes well, that will be published into [atomic].

Anything I feel like will break something, or that I have no experience with, will go into [atomic-bleeding]. I don't consider anything in atomic-bleeding the kind of thing I consider release-worthy at this time. For example, php and mysql in that channel are back ports from FC5 and FC6. There are known integration issues with PSA on both. They're stable in that they wont crash, and that they'll work fine (most likely) in a non-PSA environment. They're unstable in that PSA will not work with them 100%.

 

[Ronaldve]

In that case on a plesk server it maybe would be better to download the latest source from www.php.net and the pecl modules you want and compile it instead of using the RPM's?
Or don't you think so? what's your vision on this?