Good afternoon folks.
Earlier today, I started upgrading a few of our servers to 5.4 based on input from the list. So far, all has gone well. I have about 6 servers (not very many, but still) that need to be upgraded. Instead of taking precious bits from the mirrors for each upgrade, I was curious if I could rsync the 5.4 directory from a local mirror, and configure yum to use that repo, if it would upgrade without issues?
Would I need anything other than the 5.4 folders to do the upgrade?
-jonathan
Jonathan Moore wrote:
Good afternoon folks.
Earlier today, I started upgrading a few of our servers to 5.4 based on input from the list. So far, all has gone well. I have about 6 servers (not very many, but still) that need to be upgraded. Instead of taking precious bits from the mirrors for each upgrade, I was curious if I could rsync the 5.4 directory from a local mirror, and configure yum to use that repo, if it would upgrade without issues?
Would I need anything other than the 5.4 folders to do the upgrade?
-jonathan _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Try this http://www.howtoforge.com/creating_a_local_yum_repository_centos HTH
On Thu, Oct 22, 2009 at 11:21 PM, Rob Kampen rkampen@kampensonline.com wrote:
Try this http://www.howtoforge.com/creating_a_local_yum_repository_centos
What I was really looking for was a little more detail on exactly what I *must* have from the mirror to successfully upgrade.
Would excluding everything up to the 5.4 folder be enough? Do I need 5.3, 5.2 etc to upgrade?
On a side not, is there anything like apt-cacher for yum?
-jonathan
Jonathan Moore wrote:
On Thu, Oct 22, 2009 at 11:21 PM, Rob Kampen rkampen@kampensonline.com wrote:
Try this http://www.howtoforge.com/creating_a_local_yum_repository_centos
What I was really looking for was a little more detail on exactly what I *must* have from the mirror to successfully upgrade.
Would excluding everything up to the 5.4 folder be enough? Do I need 5.3, 5.2 etc to upgrade?
you need the /5.4/ directory and the /5/ symlink. everything else under /5.*/ are place holders with a readme file.
you can exclude the SRPM directories if you want to save space and transfer time.
On 10/23/2009 06:10 PM, Jonathan Moore wrote:
What I was really looking for was a little more detail on exactly what I *must* have from the mirror to successfully upgrade.
If you want to download the minimum number of packages, the easiest answer is: use a proxy server.
export http_proxy=http://proxy.foo.com:8888 yum upgrade
Or, if you have some type of shared storage (NFS, perhaps), you can configure yum to keep its cache directory there. Configure all of your systems to use the same cache directory and to keep cache.
2009/10/25 Gordon Messmer yinyang@eburg.com:
On 10/23/2009 06:10 PM, Jonathan Moore wrote:
What I was really looking for was a little more detail on exactly what I *must* have from the mirror to successfully upgrade.
If you want to download the minimum number of packages, the easiest answer is: use a proxy server.
export http_proxy=http://proxy.foo.com:8888 yum upgrade
I'm on the same situation and I use IntelligentMirror and squid to cache all the rpm packages regardless of the mirror. Also I set up the mirror line on the /etc/yum.conf One word of warning if you want to go to the same route: you have to setup 2 different mirrors for x86_64 and i386 arch., because there are i386 packages built for the x86_64 platform that have the same name but different checksum/content than the one for i386.
HTH Lorenzo
Do you mean upgrade the CentOS from the ISO?
On Fri, Oct 23, 2009 at 5:24 AM, Jonathan Moore supermegatron@gmail.comwrote:
Good afternoon folks.
Earlier today, I started upgrading a few of our servers to 5.4 based on input from the list. So far, all has gone well. I have about 6 servers (not very many, but still) that need to be upgraded. Instead of taking precious bits from the mirrors for each upgrade, I was curious if I could rsync the 5.4 directory from a local mirror, and configure yum to use that repo, if it would upgrade without issues?
Would I need anything other than the 5.4 folders to do the upgrade?
-jonathan _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Hello,
I thought I'd wait a little while before upgrading to 5.4, but am running into the following errors:
-> Finished Dependency Resolution lvm2-2.02.46-8.el5.i386 from base has depsolving problems --> Missing Dependency: device-mapper >= 1.02.32-1 is needed by package lvm2-2.02.46-8.el5.i386 (base) mkinitrd-5.1.19.6-54.i386 from base has depsolving problems --> Missing Dependency: device-mapper-multipath >= 0.4.7-9 is needed by package mkinitrd-5.1.19.6-54.i386 (base) lvm2-2.02.46-8.el5.i386 from base has depsolving problems --> Missing Dependency: device-mapper-event is needed by package lvm2-2.02.46-8.el5.i386 (base) Error: Missing Dependency: device-mapper-multipath >= 0.4.7-9 is needed by package mkinitrd-5.1.19.6-54.i386 (base) Error: Missing Dependency: device-mapper-event is needed by package lvm2-2.02.46-8.el5.i386 (base) Error: Missing Dependency: device-mapper >= 1.02.32-1 is needed by package lvm2-2.02.46-8.el5.i386 (base)
It would appear that these packages do exist, although earlier versions:
# rpm -q device-mapper device-mapper-1.02.13-1.el5
Any thoughts would be appreaicated.
Regards,
Rohan.
Rohan Gilchrist wrote:
Hello,
I thought I'd wait a little while before upgrading to 5.4, but am running into the following errors:
-> Finished Dependency Resolution lvm2-2.02.46-8.el5.i386 from base has depsolving problems --> Missing Dependency: device-mapper >= 1.02.32-1 is needed by package lvm2-2.02.46-8.el5.i386 (base) mkinitrd-5.1.19.6-54.i386 from base has depsolving problems --> Missing Dependency: device-mapper-multipath >= 0.4.7-9 is needed by package mkinitrd-5.1.19.6-54.i386 (base) lvm2-2.02.46-8.el5.i386 from base has depsolving problems --> Missing Dependency: device-mapper-event is needed by package lvm2-2.02.46-8.el5.i386 (base) Error: Missing Dependency: device-mapper-multipath >= 0.4.7-9 is needed by package mkinitrd-5.1.19.6-54.i386 (base) Error: Missing Dependency: device-mapper-event is needed by package lvm2-2.02.46-8.el5.i386 (base) Error: Missing Dependency: device-mapper >= 1.02.32-1 is needed by package lvm2-2.02.46-8.el5.i386 (base)
It would appear that these packages do exist, although earlier versions:
# rpm -q device-mapper device-mapper-1.02.13-1.el5
Any thoughts would be appreaicated.
Regards,
Rohan.
1. Did you follow the procedure in the 5.4 Release Notes (repeated in the release announcement)?
2. Perhaps the repo(s) you're using is/are broken. My DVD contains (among otherstuf) lvm2-2.02.46-8.el5.i386.rpm and device-mapper-1.02.13.1.el5.i386.rpm so that that particular dependency would be resolved easily enough.
Robert wrote:
- Did you follow the procedure in the 5.4 Release Notes (repeated in
the release announcement)?
See, this is a problem.... I shouldn't have to know about special procedures in release notes to be able to do `yum update` at any arbitrary time
what about users who aren't even on these lists?
Hmm no. Time to read the notes. Thanks for your help!
On Sat, 24 Oct 2009, Robert wrote:
Rohan Gilchrist wrote:
Hello,
I thought I'd wait a little while before upgrading to 5.4, but am running into the following errors:
-> Finished Dependency Resolution lvm2-2.02.46-8.el5.i386 from base has depsolving problems --> Missing Dependency: device-mapper >= 1.02.32-1 is needed by package lvm2-2.02.46-8.el5.i386 (base) mkinitrd-5.1.19.6-54.i386 from base has depsolving problems --> Missing Dependency: device-mapper-multipath >= 0.4.7-9 is needed by package mkinitrd-5.1.19.6-54.i386 (base) lvm2-2.02.46-8.el5.i386 from base has depsolving problems --> Missing Dependency: device-mapper-event is needed by package lvm2-2.02.46-8.el5.i386 (base) Error: Missing Dependency: device-mapper-multipath >= 0.4.7-9 is needed by package mkinitrd-5.1.19.6-54.i386 (base) Error: Missing Dependency: device-mapper-event is needed by package lvm2-2.02.46-8.el5.i386 (base) Error: Missing Dependency: device-mapper >= 1.02.32-1 is needed by package lvm2-2.02.46-8.el5.i386 (base)
It would appear that these packages do exist, although earlier versions:
# rpm -q device-mapper device-mapper-1.02.13-1.el5
Any thoughts would be appreaicated.
Regards,
Rohan.
- Did you follow the procedure in the 5.4 Release Notes (repeated in
the release announcement)?
- Perhaps the repo(s) you're using is/are broken. My DVD contains
(among otherstuf) lvm2-2.02.46-8.el5.i386.rpm and device-mapper-1.02.13.1.el5.i386.rpm so that that particular dependency would be resolved easily enough.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 10/24/2009 05:09 PM Rohan Gilchrist wrote:
Hello,
I thought I'd wait a little while before upgrading to 5.4, but am running into the following errors:
-> Finished Dependency Resolution lvm2-2.02.46-8.el5.i386 from base has depsolving problems --> Missing Dependency: device-mapper >= 1.02.32-1 is needed by package lvm2-2.02.46-8.el5.i386 (base) mkinitrd-5.1.19.6-54.i386 from base has depsolving problems --> Missing Dependency: device-mapper-multipath >= 0.4.7-9 is needed by package mkinitrd-5.1.19.6-54.i386 (base) lvm2-2.02.46-8.el5.i386 from base has depsolving problems --> Missing Dependency: device-mapper-event is needed by package lvm2-2.02.46-8.el5.i386 (base) Error: Missing Dependency: device-mapper-multipath >= 0.4.7-9 is needed by package mkinitrd-5.1.19.6-54.i386 (base) Error: Missing Dependency: device-mapper-event is needed by package lvm2-2.02.46-8.el5.i386 (base) Error: Missing Dependency: device-mapper >= 1.02.32-1 is needed by package lvm2-2.02.46-8.el5.i386 (base)
It would appear that these packages do exist, although earlier versions:
# rpm -q device-mapper device-mapper-1.02.13-1.el5
Any thoughts would be appreaicated.
Regards,
Rohan.
I had some similar problems with my update, not with the same packages as you, but with yum claiming that dependencies needed to be installed-- dependencies which *were* already installed. All I did was a "yum reinstall ..." on those dependencies and that fixed it. In your case "yum reinstall device-mapper" etc. might fix it. Hope so. Let us know.
-
Gordon Messmer -
John R Pierce -
Jonathan Moore -
ken -
Lorenzo Quatrini -
Majian -
Rob Kampen -
Robert -
Rohan Gilchrist