"Could not find update match for php", Plesk 8.1,
"Could not find update match for php", Plesk 8.1,
Hello all.
I've spent a good part of the day googling and searching through the Plesk and ART forums but haven't had any luck.
I'm trying to upgrade PHP from 5.0.4 to 5.1.6 on a Fedora Core 4 box with Plesk 8.1. I run "yum update php" (after enabling the bleeding channel) and get: "Could not find update match for php"
I've tried everything that I've been able to find in the forums but can't get past that error. My yum.conf is as it was set up by running the "lynx -source http://3es.atomicrocketturtle.com/installers/atomic.sh | sh" command. I've tried adding the PSA 8.1 channel into the yum.conf but keep getting "Error: failure: repodata/repomd.xml from psa-8.1: [Errno 256] No more mirrors to try" when it's in there.
Any help would be very much appreciated. I'm completely stuck.
I've spent a good part of the day googling and searching through the Plesk and ART forums but haven't had any luck.
I'm trying to upgrade PHP from 5.0.4 to 5.1.6 on a Fedora Core 4 box with Plesk 8.1. I run "yum update php" (after enabling the bleeding channel) and get: "Could not find update match for php"
I've tried everything that I've been able to find in the forums but can't get past that error. My yum.conf is as it was set up by running the "lynx -source http://3es.atomicrocketturtle.com/installers/atomic.sh | sh" command. I've tried adding the PSA 8.1 channel into the yum.conf but keep getting "Error: failure: repodata/repomd.xml from psa-8.1: [Errno 256] No more mirrors to try" when it's in there.
Any help would be very much appreciated. I'm completely stuck.
-
- Long Time Forum Regular
- Posts: 2813
- Joined: Sat Aug 20, 2005 9:30 am
- Location: The Netherlands
What does your ART yum config for psa-8.1 look like? It should read something like this:
Code: Select all
baseurl=http://3es.atomicrocketturtle.com/atomic/psa-8.1/fedora/$releasever/$basearch/
Lemonbit Internet Dedicated Server Management
Thanks for the responses.
I did change the enabled on -bleeding to 1 (after installing with the lynx command as noted above), but might have messed something else up. My atomic.repo in my /yum.repo.d/ looks like:
If I remove the psa-8.1 I don't get any errors, but still get the "Could not find update match for php" error. With the psa-8.1 in there I get the following:
(As an aside, trying to paste in the Content Type line above (without the space I added) causes a nasty error that prevents posting or previewing. It's specifically the "Content Type". Anyway...)
I found this post but haven't had any luck there either.
Thanks again for your help.
I did change the enabled on -bleeding to 1 (after installing with the lynx command as noted above), but might have messed something else up. My atomic.repo in my /yum.repo.d/ looks like:
Code: Select all
# Stable channel
[atomic]
name=Atomic Rocket Turtle - $releasever - Atomic PSA-Compatible RPMS
baseurl=http://3es.atomicrocketturtle.com/atomic/art/$releasever/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY.art.txt
enabled=0
# Almost Stable, release candidates for [atomic]
[atomic-testing]
name=Atomic Rocket Turtle - $releasever - Atomic Testing PSA-Compatible RPMS
baseurl=http://3es.atomicrocketturtle.com/atomic-testing/art/$releasever/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY.art.txt
enabled=0
# Untested, Unstable, known buggy, and incomplete packages
[atomic-bleeding]
name=Atomic Rocket Turtle - $releasever - Atomic Bleeding PSA-Compatible RPMS
baseurl=http://3es.atomicrocketturtle.com/atomic-bleeding/art/$releasever/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY.art.txt
enabled=1
# I added this manually (was not installed by lynx/installer command):
[psa-8.1]
name=Atomic Rocket Turtle - $releasever - SW-Soft PSA 8.1 RPMS
baseurl=http://3es.atomicrocketturtle.com/atomic/psa-8.1/fedora/$releasever/$arch
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY.art.txt
enabled=1
Code: Select all
>: # yum update php
Setting up Update Process
Setting up repositories
http://3es.atomicrocketturtle.com/atomic/psa-8.1/fedora/4/ia32e/repodata/repomd.xml: [Errno 4] IOError: HTTP Error 404: Date: Tue, 13 Feb 2007 18:39:08 GMT
Server: NOYB
Content-Length: 323
Connection: close
Co ntent-Type: text/html; charset=iso-8859-1
Trying other mirror.
Cannot open/read repomd.xml file for repository: psa-8.1
failure: repodata/repomd.xml from psa-8.1: [Errno 256] No more mirrors to try.
Error: failure: repodata/repomd.xml from psa-8.1: [Errno 256] No more mirrors to try.
I found this post but haven't had any luck there either.
Thanks again for your help.
-
- Long Time Forum Regular
- Posts: 2813
- Joined: Sat Aug 20, 2005 9:30 am
- Location: The Netherlands
Apparently $arch evaluates to ia32e on your machine and there is no ia32e dir at that location. Shouldn't $arch be $basearch?
Lemonbit Internet Dedicated Server Management
Thanks for that. It helped, but I'm still getting the "Could not find update match for PHP" error.
Here's my output:
Thoughts? Thanks again. Everybody's help is greatly appreciated.
Here's my output:
Code: Select all
>: yum update php
Setting up Update Process
Setting up repositories
psa-8.1 100% |=========================| 951 B 00:00
extras 100% |=========================| 1.1 kB 00:00
updates-released 100% |=========================| 951 B 00:00
atomic-bleeding 100% |=========================| 951 B 00:00
base 100% |=========================| 1.1 kB 00:00
Reading repository metadata in from local files
primary.xml.gz 100% |=========================| 40 kB 00:00
psa-8.1 : ################################################## 173/173
Added 173 new packages, deleted 0 old in 0.41 seconds
primary.xml.gz 100% |=========================| 871 kB 00:02
extras : ################################################## 2810/2810
Added 7 new packages, deleted 7 old in 1.48 seconds
Could not find update match for php
No Packages marked for Update/Obsoletion
-
- Long Time Forum Regular
- Posts: 2813
- Joined: Sat Aug 20, 2005 9:30 am
- Location: The Netherlands
The php packages are not in the psa-8.1 channel, they are in the atomic channel, but I don't believe there are 64-bit packages there yet.
Also, I'd leave the atomic-stable channel enabled when enabling the -bleeding channel. And remember that nothing in the -bleeding channel is guaranteed to work: it's Scott's playground.
Also, I'd leave the atomic-stable channel enabled when enabling the -bleeding channel. And remember that nothing in the -bleeding channel is guaranteed to work: it's Scott's playground.
Lemonbit Internet Dedicated Server Management