Hi,
I try to upgrade a 5.0 desktop to 5.1. Some packages give me errors. Most important the kernel and e2fsprogs:
[root@scarbo9 ~]# yum update kernel Loading "allowdowngrade" plugin Loading "installonlyn" plugin Loading "fastestmirror" plugin Setting up Update Process Setting up repositories extras 100% |=========================| 1.1 kB 00:00 updates 100% |=========================| 951 B 00:00 base 100% |=========================| 1.1 kB 00:00 addons 100% |=========================| 951 B 00:00 Loading mirror speeds from cached hostfile Reading repository metadata in from local files Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package kernel.x86_64 0:2.6.18-53.1.4.el5 set to be installed --> Running transaction check --> Processing Conflict: kernel conflicts e2fsprogs < 1.37-4 --> Restarting Dependency Resolution with new changes. --> Populating transaction set with selected packages. Please wait. ---> Package e2fsprogs.x86_64 0:1.39-10.el5 set to be updated --> Running transaction check --> Processing Conflict: kernel conflicts e2fsprogs < 1.37-4 Error: No Package Matching kernel.x86_64
I'm a little bit confused about this error. Any hints?
regards, Andreas
Andreas Kuntzagk wrote:
[root@scarbo9 ~]# yum update kernel
try running a yum update or a : yum update kernel e2fsprogs, so they both get updated in the same transaction.
Loading "allowdowngrade" plugin
this might be whats causing the kernel package to not get updated..
Loading mirror speeds from cached hostfile I'm a little bit confused about this error. Any hints?
[root@scarbo9 ~]# yum update kernel
try running a yum update or a : yum update kernel e2fsprogs, so they both get updated in the same transaction.
Did that - to no avail. Shouldn't package dependencies take care for them to update in the same transaction?
Loading "allowdowngrade" plugin
this might be whats causing the kernel package to not get updated..
Disabled all yum plugins to make sure, didn't help.
Andreas
Andreas Kuntzagk wrote:
[root@scarbo9 ~]# yum update kernel
try running a yum update or a : yum update kernel e2fsprogs, so they both get updated in the same transaction.
Did that - to no avail. Shouldn't package dependencies take care for them to update in the same transaction?
Loading "allowdowngrade" plugin
this might be whats causing the kernel package to not get updated..
Disabled all yum plugins to make sure, didn't help.
Andreas
I can only think of 2 things ...
The mirror that you are pointed to is not updated. Are you pointing to your own mirror or the default ones.
This is normally caused when someone has the 5.0 BASE repo and the 5.1 updates repo. That _WILL_NOT_WORK_ .... as both base and updates are different for 5.0 and 5.1.
You have to point to /5.1/os/ AND /5.1/updates/ ... can not point to /5.0/os and /5.1/updates/ (5.1 as a whole is a tree ... it can not be mixed and matched with 5.0.)
If that is NOT the problem (ie, you are using mirrors from our "mirrorlist=" list or mirror.centos.org as your "baseurl=" in CentOS-Base.repo) then do:
yum clean all
yum -d3 upgrade kernel
That should give you some more detail about the error.
Thanks, Johnny Hughes
Andreas Kuntzagk wrote:
[root@scarbo9 ~]# yum update kernel
try running a yum update or a : yum update kernel e2fsprogs, so they both get updated in the same transaction.
Did that - to no avail. Shouldn't package dependencies take care for them to update in the same transaction?
Loading "allowdowngrade" plugin
this might be whats causing the kernel package to not get updated..
Disabled all yum plugins to make sure, didn't help.
The mirror that you are pointed to is not updated. Are you pointing to your own mirror or the default ones.
This is normally caused when someone has the 5.0 BASE repo and the 5.1 updates repo. That _WILL_NOT_WORK_ .... as both base and updates are different for 5.0 and 5.1.
You have to point to /5.1/os/ AND /5.1/updates/ ... can not point to /5.0/os and /5.1/updates/ (5.1 as a whole is a tree ... it can not be mixed and matched with 5.0.)
AFAIR I never changed the mirror settings after install from DVD. The lines in CentOS-Base.repo look like
[base] name=CentOS-$releasever - Base mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&rep... #baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
So baseurl is commented out. But changing this does not help.
If that is NOT the problem (ie, you are using mirrors from our "mirrorlist=" list or mirror.centos.org as your "baseurl=" in CentOS-Base.repo) then do:
yum clean all
yum -d3 upgrade kernel
That should give you some more detail about the error.
I can't see anything useful:
Reading Local RPMDB Building updates object Resolving Dependencies 1198137677.12 --> Populating transaction set with selected packages. Please wait. ---> Downloading header for kernel to pack into transaction set. kernel-2.6.18-53.1.4.el5. 100% |=========================| 249 kB 00:00 ---> Package kernel.x86_64 0:2.6.18-53.1.4.el5 set to be installed --> Running transaction check # of Deps = 1 --> Processing Conflict: kernel conflicts e2fsprogs < 1.37-4 --> Restarting Dependency Resolution with new changes. ---> Loop Number: 2 --> Populating transaction set with selected packages. Please wait. ---> Downloading header for e2fsprogs to pack into transaction set. e2fsprogs-1.39-10.el5.x86 100% |=========================| 25 kB 00:00 ---> Package e2fsprogs.x86_64 0:1.39-10.el5 set to be updated --> Running transaction check # of Deps = 3 --> Processing Conflict: kernel conflicts e2fsprogs < 1.37-4 Error: No Package Matching kernel.x86_64
regards, Andreas
Andreas Kuntzagk wrote:
---> Package e2fsprogs.x86_64 0:1.39-10.el5 set to be updated --> Running transaction check # of Deps = 3 --> Processing Conflict: kernel conflicts e2fsprogs < 1.37-4 Error: No Package Matching kernel.x86_64
run your yum update with -d7 and pastebin.ca the output ( make sure to set expire to never or > 7 days), and pastebin the url here. make sure you include _ALL_ of the yum output not just snippets of it.
afaict, you have something broken on your setup, or an exclude or plugin is causing issues there.
Hi,
run your yum update with -d7 and pastebin.ca the output ( make sure to set expire to never or > 7 days), and pastebin the url here. make sure you include _ALL_ of the yum output not just snippets of it.
Don't know what pastebin.ca is. Did not find that on this machine. So I'm attaching yum output here.
afaict, you have something broken on your setup, or an exclude or plugin is causing issues there.
AFAIK I have no excludes and disabled all plugins.
Andreas
Andreas Kuntzagk wrote:
AFAIK I have no excludes and disabled all plugins.
are you sure you dont have an exclude for i386 pkgs ? pastebin.ca, google knows all about it.
--- Andreas Kuntzagk andreas.kuntzagk@mdc-berlin.de wrote:
Hi,
run your yum update with -d7 and pastebin.ca the
output ( make sure to
set expire to never or > 7 days), and pastebin the
url here. make sure
you include _ALL_ of the yum output not just
snippets of it.
Don't know what pastebin.ca is. Did not find that on this machine. So I'm attaching yum output here.
afaict, you have something broken on your setup,
or an exclude or plugin
is causing issues there.
AFAIK I have no excludes and disabled all plugins.
Andreas
Hello Andreas,
pastebin.ca is not a program on your server, it is a website that you can paste output too and it will give you a link to paste it to where ever you need to post the info. This will prevent from having a large email as you have done. hope this makes sense.
regards
steven
Hi,
I finally solved my update problems by using rpm command. I found that I had 2 versions of e2fsprogs installed, one ending with EL4. Don't know where this came from, because there was never a EL4 on this machine. But when I removed it, yum update run fine.
Thanks, Andreas
Andreas Kuntzagk wrote:
Hi,
I finally solved my update problems by using rpm command. I found that I had 2 versions of e2fsprogs installed, one ending with EL4. Don't know where this came from, because there was never a EL4 on this machine. But when I removed it, yum update run fine.
thats the i386 package that seemed to be getting excluded, based on your paste earlier in the thread.
I finally solved my update problems by using rpm command. I found that I had 2 versions of e2fsprogs installed, one ending with EL4. Don't know where this came from, because there was never a EL4 on this machine. But when I removed it, yum update run fine.
thats the i386 package that seemed to be getting excluded, based on your paste earlier in the thread.
Sorry, I don't get your message. Do you mean I somehow manage to exclude the i386 package from updating and that caused my problems? But how did I exclude it? I did not specify an exclude on command line or config file either.
Please enlighten me further. (This thing has helped me already to get better knowledge of yum :-)
Andreas
-
Andreas Kuntzagk -
Johnny Hughes -
Karanbir Singh -
Steven Vishoot