files needed for yum

mything · Unread post by **mything** » Mon Apr 03, 2006 10:33 am

hi, i am all new to linux, plesk. i am using plesk 7.5.4 with fedora core2. i would like to update mysql, but from my reading i see i need yum. yum is not pre-install, but i have been looking on this site for the correct yum but i see different types, which one do i need? what directory do i put this file on my server? can someone pls help thanks.

breun · Unread post by **breun** » Mon Apr 03, 2006 3:49 pm

Since you're running FC2 you'll need to get FC2's yum.

breun's ten magic steps to get yum installed on FC2 and update MySQL to 4.1.x

1. Go to http://download.fedoralegacy.org/fedora/2/os/i386/
2. Get the location of the yum rpm (right click -> copy location)
3. Log onto your server (ssh root@ip).
4. Download the rpm by running 'wget location-of-file', i.e.:
wget http://download.fedoralegacy.org/fedora ... noarch.rpm
5. Try to install the rpm: rpm -Uvh *.rpm
6. The last step will probably fail saying you'll need some more packages on which yum depends. Get these rpm files by looking up the locations of the dependencies at either http://download.fedoralegacy.org/fedora/2/updates/i386/ or, if it's not in that location, the webpage from step 1. Use wget to download them to your server. Then go to step 5 again. The dependencies you downloaded may need some dependencies in return also, so you might need to repeat this process a couple of times (~4 times or so).
7. When the installation is done, you can remove the rpm files you downloaded: rm -f *.rpm
8. Install ART's GPG key: rpm --import http://www.atomicrocketturtle.com/RPM-GPG-KEY.art.txt
9. Add the following to /etc/yum.conf:
[atomic]
name=Atomic Rocket Turtle - $releasever - Atomic PSA-Compatible RPMS
baseurl=http://3es.atomicrocketturtle.com/atomi ... eleasever/
10. Run this command to update mysql: yum update mysql and then restart mysqld: service mysqld restart

So there. I know resolving those dependencies isn't a fun job, but that's exactly why you're installing yum: yum will take care of that from now on.

arisk · Unread post by **arisk** » Tue Apr 04, 2006 4:46 pm

Great tutorial.
I am in the same position (noob) and looking to do the same thing (install yum to update php*) with Plesk 7.5.4 inside a Virtuozzo VPS running Centos4.

Where can I get yum for Centos4 (4.2)?
I suppose I follow the other steps verbatim then?

Will there be issues since this is inside VZ?

Thanks in advance.
This is a great site and a great service.

mything · Unread post by **mything** » Tue Apr 04, 2006 5:02 pm

thank you for your reply. i followed your step but i have a dependcy problem. i get this error libxml2>=2.6.15 is needed by (installed) libxslt-1.1.12-2. i can not find the dependcy libxml2>=2.6.15. does this file exists some where thanks.

breun · Unread post by **breun** » Tue Apr 04, 2006 5:22 pm

arisk wrote:I am in the same position (noob) and looking to do the same thing (install yum to update php*) with Plesk 7.5.4 inside a Virtuozzo VPS running Centos4.

Where can I get yum for Centos4 (4.2)?

Take your pick from the CentOS mirror list and then navigate

- into the latest version for your base version (you're running CentOS 4, so go into the 4.3 dir)
- into the 'os' dir
- into the 'i386' dir (or pick another architecture if you're not on 32-bit intel compatible)
- into the 'CentOS' dir
- into the 'RPMS' dir

If you'd pick the kernel.org mirror you'd end up here:
http://mirrors.kernel.org/centos/4.3/os ... ntOS/RPMS/

I suppose I follow the other steps verbatim then?

Yes. Only change '$releasever' to '4ES' in step 9 (as is noted in ART's install instructions).

Will there be issues since this is inside VZ?

I don't know, there may be. I don't use vservers myself, but I have done yum installs on vservers before. It should work, but sometimes they do the strangest things to vservers.

breun · Unread post by **breun** » Tue Apr 04, 2006 5:31 pm

mything wrote:thank you for your reply. i followed your step but i have a dependcy problem. i get this error libxml2>=2.6.15 is needed by (installed) libxslt-1.1.12-2. i can not find the dependcy libxml2>=2.6.15. does this file exists some where thanks.

Ah yes. Something I forgot. First look in the updates directory for dependencies: http://download.fedoralegacy.org/fedora/2/updates/i386/

If it's not in the updates dir, then check the os dir (the link I mention above).

mything · Unread post by **mything** » Tue Apr 04, 2006 5:39 pm

breun wrote:
mything wrote:thank you for your reply. i followed your step but i have a dependcy problem. i get this error libxml2>=2.6.15 is needed by (installed) libxslt-1.1.12-2. i can not find the dependcy libxml2>=2.6.15. does this file exists some where thanks.
Ah yes. Something I forgot. First look in the updates directory for dependencies: http://download.fedoralegacy.org/fedora/2/updates/i386/

If it's not in the updates dir, then check the os dir (the link I mention above).

i found libxml2>=2.6.16-2 will this one work with the installed libxslt-1.1.12-2 cuz i didn't see the earlier version 2.6.15.thanks

arisk · Unread post by **arisk** » Tue Apr 04, 2006 7:12 pm

a million thanks breun.
I was able to install yum with little trouble.

I modified my yum.conf with the following:

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

replacing all instances of $releasever with 4ES as I understood the instructions.

I should be ok now, e? (fingers crossed)

I have one additonal question if its not too much trouble.
I was unable to use wget or a direct import of the GPG KEY, instead had to download locally then ftp to my server.
Does this hint to something misconfigured on my machine?

arisk · Unread post by **arisk** » Tue Apr 04, 2006 7:30 pm

It probably does....

[root@vps101 /]# yum update php
Setting up Update Process
Setting up repositories
Cannot find a valid baseurl for repo: update
Error: Cannot find a valid baseurl for repo: update

Any ideas?

BTW: Should I go ahead and add the swsoft channel?
thanks again.
-a

mything · Unread post by **mything** » Tue Apr 04, 2006 8:21 pm

thank you breun i finally got it going. your help was appreciated especially since i am a newbie.

breun · Unread post by **breun** » Wed Apr 05, 2006 3:45 am

arisk wrote:I modified my yum.conf with the following:

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

replacing all instances of $releasever with 4ES as I understood the instructions.

I should be ok now, e? (fingers crossed)

It looks okay. Only replace '$releasever' in the [atomic] section, not in the other sections of /etc/yum.conf.

I have one additonal question if its not too much trouble.
I was unable to use wget or a direct import of the GPG KEY, instead had to download locally then ftp to my server.
Does this hint to something misconfigured on my machine?

Maybe, why were you unable to use wget or do a direct import? Did you get any error messages?

breun · Unread post by **breun** » Wed Apr 05, 2006 3:52 am

arisk wrote:It probably does....

[root@vps101 /]# yum update php
Setting up Update Process
Setting up repositories
Cannot find a valid baseurl for repo: update
Error: Cannot find a valid baseurl for repo: update

Any ideas?

Well, apparently yum can't find a valid baseurl for Fedora's [update] repository. What does the [update] section in your yum.conf look like?

BTW, if you're running a legacy version of Fedora Core (all versions up to FC3 are currently no longer being maintained by Red Hat, but have been transferred to Fedora Legacy), check if you have Fedora Legacy's repositories installed so you'll get the security fixes they provide. Instructions for installing the Fedora Legacy repositories are available at http://www.fedoralegacy.org/docs/

arisk · Unread post by **arisk** » Thu Apr 06, 2006 5:43 am

Ok. to double check first, was I correct in changing $releasever to 4ES in the name entry for ART's atomic channel?

I am on Centos4.

The base repo is in CentOS-base.repo file located in yum.repos.d directory.
Which uses a mirrorlist thing where it finds the closest mirror depending on location.

When this failed I resorted to using the baseurl that was commented out in the above repo file as backup.

(BTW: Would you recommend I add ART's base channel to the yum.conf?
Is this recommended? Will it conflict with the above from Centos? Should I comment out the channels or delete/rename the file?)

It seems it was the same issue with wget, and curl, etc.
I could not resolve any host.
Commenting out my resolv.conf entries seems to have fixed that now though.
Thanks again.
-a

breun · Unread post by **breun** » Thu Apr 06, 2006 5:53 am

arisk wrote:Ok. to double check first, was I correct in changing $releasever to 4ES in the name entry for ART's atomic channel?

I am on Centos4.

Yes, if you're on CentOS 4 or RHEL 4 you need to put in 4ES. 3ES for CentOS 3 or RHEL 3.

The base repo is in CentOS-base.repo file located in yum.repos.d directory.
Which uses a mirrorlist thing where it finds the closest mirror depending on location.

When this failed I resorted to using the baseurl that was commented out in the above repo file as backup.

And that worked? Either all those mirrors were down (unlikely) or your server doesn't know how to resolve (no proper DNS setup).

(BTW: Would you recommend I add ART's base channel to the yum.conf?
Is this recommended? Will it conflict with the above from Centos? Should I comment out the channels or delete/rename the file?)

I usually create an atomicrocketturtle.repo file in /etc/yum.repos.d/. However the yum.repos.d system was not yet available on FC2 and older, so you'll need to add the sections to /etc/yum.conf directly. It doesn't matter where you add it actually, it's just easier to maintain if you use separate files in /etc/yum.repos.d/.

It seems it was the same issue with wget, and curl, etc.
I could not resolve any host.
Commenting out my resolv.conf entries seems to have fixed that now though.

You need to make sure the entries in /etc/resolv.conf are IP addresses of nameservers that will do resolving for you. Usually your ISP nameservers for instance. I usually put 127.0.0.1 in there too, so your server can also use the local nameserver (unless you disabled it) for lookups.