some issues I need asistance with.

Fault · Unread post by **Fault** » Tue Apr 03, 2007 2:56 pm

issue a: I cannot get to atomic-bleeding. I just recieved a reply back from scott? about this issue, however I am unabled to find the atomic-release rpm he speaks of.

2 With this fixed download issue will it be easier to upgrade php4.3.9 and mysql 4.1.20? because I spent over a day trying to get everything installed after a centOS 4 install. But it is giving me a headache. mysql wouldnt install right and php5.1.x wouldnt install right, tried them both manually. php reported it was 5.2.1 however no php sites would work that I host except phpinfo

I just reimaged my server BACK to fc4 with plesk 8.0 but if someone gives good advice on how to install centOS4 with plesk 8.1.1 mysql5 and php5.1.x then Ill go that route again.

My main issue when installing php5.1.x was php 4.3.9 was still installed so that was prolyl my issue but if I yum remove it plesk is removed also =/ same with mysql 4.1.20

Unread post by **scott** » Tue Apr 03, 2007 5:47 pm

atomic-bleeding is the 0-day, unsupported channel. So as much as it pains me to do this, Im going to defer my involvement on anything -bleeding related to anyone else that wants to touch it.

That being said, AOOI is something I can support, and thats what you'd use to re-image your 1and1 box with CentOS4. Ive got a video tutorial of it in action on the front page of the website.

Fault · Unread post by **Fault** » Tue Apr 03, 2007 6:58 pm

well currently I am only using stuff from the one you support, testing and bleeding are disabled for the time being.

So I believe that gives me php 5.0.13?

Th eproblem I am currently having I am unsure if you support or not. it is the php4 configurator errors plesk and doesnt let it install.

Should I remove 5.0.13 and install 4.3.9 then install plesk and then upgrade to 5.0.13 from your repo?

Unread post by **scott** » Tue Apr 03, 2007 9:40 pm

Whats the error you're getting back? Basically what Im going to do is build whatever changes need to be made into 5.2.1. I suspect what we might be running into is a PSA issue where it just doesnt have the right packages to live nicely with a more modern php. Thats not a problem though, we can build around that if we have to.

BTW, is this a 1and1 box you're using?