scott wrote:
Did you install yum on your VPS through my installer?
No. I tried to, by running
Code:
wget -q -O - http://www.atomicorp.com/installers/atomic.sh |sh
but it didn't actually set up any repo's in /etc/yum.repos.d. I have moved/backed up the default repos, so they're not being used at all.
Since that didn't seem to be working, I manually created asl.repo, which contains:
Code:
[atomic]
name=Atomic Rocket Turtle - $releasever - Atomic PSA-Compatible RPMS
baseurl=http://3es.atomicrocketturtle.com/atomic/art/$releasever/
When I do yum install pyzor, I get the following:
Code:
[root@vps ~]# yum install pyzor
Setting up Install Process
Setting up repositories
atomic 100% |=========================| 951 B 00:00
Reading repository metadata in from local files
Parsing package install arguments
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package pyzor.noarch 0:0.4.0-5.rhfc4.art set to be updated
--> Running transaction check
--> Processing Dependency: python(abi) = 2.4 for package: pyzor
--> Finished Dependency Resolution
Error: Missing Dependency: python(abi) = 2.4 is needed by package pyzor
I'm installing pyzor because I'm trying to get spamassassin/qmail/clamAV up and running, by doing the installs mentioned
in this thread. I had some problems with spamassassin, so I figured I would at least try the rest. Trying to update spamassassin gives me the following errors:
Code:
Error: Missing Dependency: perl-IO-Socket-SSL is needed by package spamassassin
Error: Missing Dependency: libcrypto.so.5 is needed by package spamassassin
Error: Missing Dependency: libssl.so.5 is needed by package spamassassin
Error: Missing Dependency: perl(:MODULE_COMPAT_5.8.6) is needed by package spamassassin
Error: Missing Dependency: libssl.so.5 is needed by package perl-Net-SSLeay
Error: Missing Dependency: libcrypto.so.5 is needed by package perl-Net-SSLeay
Any idea how to fix these? Before I switched my yum repo to ART, I was able to do a full yum update. Could those packages be causing these problems? Or is it an issue of yum being incorrectly configured?
Thanks for your help,
Josh