Adding [atomic] to yum.conf

[jeff35080]

Hello! After days of pouring over old threads I finally managed to get yum installed on my server and I'm almost ready to let it rock & roll and finally get my PHP updated, as well as other apps. I have tried searching for the answer to this question, which will seem simple and silly to many of you, but I just can't find the answer here (or have overlooked it). Can someone please tell me exactly what to add to my yum.conf file so that I will get the [atomic] channel and do I need to leave the settings for Red Hat that already exist in the yum.conf file?

Thanks in advance for any and all help. I'll gladly return the favor should I have any knowledge that I can share with others.

Jeff

[jeff35080]

Okay... I was just reading a thread and found this:

Code: Select all

# THIS CHANNEL CONTAINS MY PSA COMPATIBLE RPMS (php, mysql, qmail-scanner, etc) 
[atomic] 
name=Atomic Rocket Turtle - $releasever - Atomic PSA-Compatible RPMS 
baseurl=http://3es.atomicrocketturtle.com/atomic/art/$releasever/ 
baseurl=http://www.atomicrocketturtle.com/atomic/art/$releasever/ 

[atomic-app-vault] 
name=Atomic Rocket Turtle - $releasever - Atomic PSA App Vault RPMS 
baseurl=http://3es.atomicrocketturtle.com/atomic/app-vault/ 

[psa-7.0] 
name=Atomic Rocket Turtle - $releasever - SW-Soft PSA 7.0 RPMS 
baseurl=http://3es.atomicrocketturtle.com/atomic/psa-7.0/$releasever/ 
baseurl=http://www.atomicrocketturtle.com/atomic/psa-7.0/$releasever/ 

[psa-7.1] 
name=Atomic Rocket Turtle - $releasever - SW-Soft PSA 7.1 RPMS 
baseurl=http://3es.atomicrocketturtle.com/atomic/psa-7.1/$releasever/ 
baseurl=http://www.atomicrocketturtle.com/atomic/psa-7.1/$releasever/ 

[psa-7.5] 
name=Atomic Rocket Turtle - $releasever - SW-Soft PSA 7.5 RPMS 
baseurl=http://3es.atomicrocketturtle.com/atomic/psa-7.5/$releasever/ 
baseurl=http://www.atomicrocketturtle.com/atomic/psa-7.5/$releasever/ 

[base] 
name=Atomic Rocket Turtle - $releasever - Base OS RPMS mirror 
baseurl=http://3es.atomicrocketturtle.com/3rd-party/base/$releasever/ 

[updates] 
name=Atomic Rocket Turtle - $releasever - OS Update RPMS mirror 
baseurl=http://3es.atomicrocketturtle.com/3rd-party/updates/$releasever/ 

Is that the proper way to configure my .conf file?

[AragonM]

I can't really help you, but I can add that I have had a hard time figure this automated software stuff out myself. Not YUM specifically, but up2date on RHES3. I think we're expecting it to be more complicated than it is It seems to me you just add it to your config, and run YUM to install it. You might need to update the other packages on your sytem first. It would be great if someone who's benefited from the packages could write a HOW-TO for the whole process, which could them be made sticky in the forums. Something from configuring YUM, to bringing the system up to date, to adding the new packages. I figured it out from the information on here, but I wasn't very comfortable with my understanding of it all. It no one else does it, I'll try to do it after I'm happy enough with my process to do it on my production server. Only problem is I use up2date not YUM.

[jeff35080]

I'm comfortable working with Linux, although I'm not the typical *nix geek. I learn by doing but since this is a live server and I don't have a parallel machine to test with I have to make sure I don't screw-up anything or I could wipe out lots o' domains Anyways, someone like me could greatly benefit from someone listing a sample yum.conf file... one that someone like Scott says is acceptable. Anyways, I'm hoping someone is able to help me

[jeff35080]

Also FWIW, the server has Plesk 7.0.3 and is running Linux 2.4.20-021 if this helps

[jeff35080]

Anyone?

[phatPhrog]

This is our current yum.conf if it helps you.
We are on a Ples 7.5.4r Fedora Core 2 box, so if you are using any other configuration it will not work for you properly. (fedora channels)

Code: Select all

[main]
cachedir=/var/cache/yum
debuglevel=2
logfile=/var/log/yum.log
pkgpolicy=newest
distroverpkg=redhat-release
tolerant=1
exactarch=1
retries=20
enabled=1
gpgcheck=1
exclude=kernel*

[atomic]
name=Atomic Rocket Turtle - $releasever - Atomic PSA-Compatible RPMS
baseurl=http://3es.atomicrocketturtle.com/atomic/art/$releasever/
baseurl=http://www.atomicrocketturtle.com/atomic/art/$releasever/

[atomic-app-vault]
name=Atomic Rocket Turtle - $releasever - Atomic PSA App Vault RPMS
baseurl=http://3es.atomicrocketturtle.com/atomic/app-vault/

[psa-7.5]
name=Atomic Rocket Turtle - $releasever - SW-Soft PSA 7.5 RPMS
baseurl=http://3es.atomicrocketturtle.com/atomic/psa-7.5/$releasever/
baseurl=http://www.atomicrocketturtle.com/atomic/psa-7.5/$releasever/

[base]
name=Atomic Rocket Turtle - $releasever - Base OS RPMS mirror
baseurl=http://3es.atomicrocketturtle.com/3rd-party/base/$releasever/

[updates]
name=Atomic Rocket Turtle - $releasever - OS Update RPMS mirror
baseurl=http://3es.atomicrocketturtle.com/3rd-party/updates/$releasever/

[base]
gpgcheck=1
name=Fedora Core $releasever base
baseurl=http://download.fedoralegacy.org/fedora/$releasever/os/$basearch

[updates]
gpgcheck=1
name=Fedora Core $releasever updates
baseurl=http://download.fedoralegacy.org/fedora/$releasever/updates/$basearch

[legacy-utils]
gpgcheck=1
name=Fedora Legacy utilities for Fedora Core $releasever
baseurl=http://download.fedoralegacy.org/fedora/$releasever/legacy-utils/$basearch

#[updates-testing]
#name=Fedora Core $releasever - $basearch - Unreleased Updates
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/$releasever/$basearch/

#[development]
#name=Fedora Core $releasever - Development Tree
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/development/$basearch/

[scott]

Latest yum config info is always at the download page:
http://www.atomicrocketturtle.com/atomic/

[madsere]

Always?

I get a 401 error!

[breun]

Take a look at http://3es.atomicrocketturtle.com/atomic/ instead.

[scott]

Heh, yeah I did post that back in September of 05