Atomicorp

baseurl=http://3es.atomicrocketturtle.com/atomi ... eleasever/

That appears to be creating a problem (and this is a new thing) as it's pointing to:

http://3es.atomicrocketturtle.com/atomi ... repomd.xml: [Errno 4] IOError: HTTP Error 404: Not Found

What should I do?

There is no PSA 7.5 for Fedora Core 4, so thats a legitimate message

So what do I do?!

Yum (update) was working fine at the start of this week, then I try it today and this new error comes up. I've not manually changed or updated any softare (or Yum conf. files) at all since I last used Yum Update.

So.... what can I do?!

What OS are you running? If you're running FC4 you just shouldn't try to access a Plesk 7.5 repository, as there exists no Plesk 7.5 for FC4. If you're running RHEL or CentOS 4 you should change $releasever to 4ES (as stated in the instructions).

The point is, it was working fine until my last update, now I try and update and it's not working.

I thought $releasever was picked up from somewhere, I don't manually enter it anywhere as "4", I just use $releasever

This is from Plesk:

bind 9.2.4-2
coldfusion Component was not installed
coldfusion-support 2.96-132.7.2
courier-imap 3.0.8-rhel4.build75050824.12
drweb Component was not installed
drweb-qmail Component was not installed
frontpage 5.0.2.2634
httpd 2.0.52-22.ent.centos4
mailman 2.1.5.1-34.rhel4.2
mod_perl 1.99_16-4.centos4
mod_python 3.1.3-5.1
mysql 4.1.19-1.art.rhel4.art
perl-Apache-ASP 2.57-rhel4.build75050824.12
php 4.4.2-3.rhel4.art
postgresql-server 7.4.13-2.RHEL4.1
psa 7.5.4-rhel4.build75050824.12
psa-api-rpc 7.5.4-rhel4.build75050930.11
psa-bu 7.5.4-rhel4.build75050926.17
psa-horde 3.0.5-rhel4.build75050824.12
psa-imp 4.0.3-rhel4.build75050824.12
psa-logrotate 3.7-rhel4.build75050824.12
psa-manual-custom-skin-guide 7.5.4-rhel4.build75050824.12
psa-migration-manager 7.5.4-rhel4.build75050930.11
psa-proftpd 1.2.10-rhel4.build75050824.12
psa-qmail 1.03-rhel4.build75050824.12
psa-qmail-rblsmtpd 0.70-rhel4.build75050824.12
psa-spamassassin 7.5.4-rhel4.build75060118.18
psa-tomcat-configurator 7.5.4-rhel4.build75050824.12
psa-turba 2.0.3-rhel4.build75050926.17
samba Component was not installed
spamassassin 3.1.1-3.rhel4.art
SSHTerm 0.2.2-rhel4.build75050824.12
tomcat 4.1.24-full.2jpp

CPU GenuineIntel, Intel(R) Pentium(R) D CPU 3.00GHz
Version psa v7.5.4_build75060118.18 os_RedHat el4
OS Linux 2.6.16.11

Well, you have the RHEL4 version of Plesk 7.5 installed. If you're really running RHEL or CentOS you really should change $releasever to 4ES. Normally (using distro-specific repo's) you can just leave $releasever and yum will fill in that variable, but both FC4 and CentOS/RHEL4 will return 4 but they still need different packages, so Scott stuck all the RHEL/CentOS packages in a dir called 4ES.

Is this a new thing, as I say this has never cropped up before today, the Yum Update I did at the start of the week went swimmingly?

Should I overwrite $releasever with 4ES in the yum configuration file manually?

No, this is certainly not new. Yes, you should change it yourself. The instructions are at the bottom of every page on http://3es.atomicrocketturtle.com/.

How strange this has never been a problem before now then?

I have no idea.

Thanks for the help though, seems fine with 4ES.

You need to the same for any on my channels (atomic/atomic-testing/atomic-bleeding), otherwise you'll be pulling packages from FC4 on a CentOS4 box, which could result in all sorts of incompatibilities.

I just dont understand what changed during the past week that meant no errors turned into 404 error. But it's fine with 4ES entered now.