Hi all,
We have added yum 2.4.3 updates for CentOS 3 and 4 to the CentOS testing repository. These packages introduce the following changes:
* CentOS 4: yum now requires the yum-metadata-parser package. This is a backport of the yum C metadata parser, and provides an significant performance increase over the Python metadata parser.
* CentOS 3: this is the first release of yum 2.4 for CentOS 3, and we plan to provide this as an optional upgrade through the CentOSPlus repository. We have added code to yum 2.4 for default kernel handling (as setting the default kernel after kernel updates was handled by yum 2.0). Additionally, the package also requires the yum C metadata parser.
Please test these RPMs, and provide feedback. We are especially interested in stress testing of the new components (default kernel handling on CentOS 3, and the C metadata parser on CentOS 3 and 4).
Information on using the CentOS Testing repository can be found on the CentOS Wiki at:
http://wiki.centos.org/Repositories
Thanks, Daniel
On 5/10/07, Daniel de Kok daniel@centos.org wrote:
Hi all,
We have added yum 2.4.3 updates for CentOS 3 and 4 to the CentOS testing repository. These packages introduce the following changes:
- CentOS 4: yum now requires the yum-metadata-parser package. This is a backport of the yum C metadata parser, and provides an significant performance increase over the Python metadata parser.
Hi Daniel,
Tried your new yum on couple of C4 i386 boxes. It is significantly faster than the previous version. Here is the output of a 'yum check-update' :
BEFORE
Reading repository metadata in from local files primary.xml.gz 100% |=========================| 134 kB 00:00 update : ################################################## 393/393 Added 393 new packages, deleted 0 old in 7.98 seconds primary.xml.gz 100% |=========================| 510 kB 00:00 base : ################################################## 1500/1500 Added 1500 new packages, deleted 0 old in 22.19 seconds primary.xml.gz 100% |=========================| 100 kB 00:00 centosplus: ################################################## 356/356 Added 356 new packages, deleted 0 old in 5.09 seconds primary.xml.gz 100% |=========================| 157 B 00:00 Added 0 new packages, deleted 0 old in 0.01 seconds primary.xml.gz 100% |=========================| 35 kB 00:00 extras : ################################################## 139/139 Added 139 new packages, deleted 0 old in 1.61 seconds
AFTER
Reading repository metadata in from local files primary.xml.gz 100% |=========================| 134 kB 00:00 update : ################################################## 393/393 primary.xml.gz 100% |=========================| 510 kB 00:00 base : ################################################## 1500/1500 primary.xml.gz 100% |=========================| 100 kB 00:00 centosplus: ################################################## 356/356 primary.xml.gz 100% |=========================| 157 B 00:00 primary.xml.gz 100% |=========================| 35 kB 00:00 extras : ################################################## 139/139
The total time from the "before" run was 36.88 seconds. It was < 5 seconds "after" the update. By the way, why is it that the updated version does not show info like the number of packages and the elapsed time?
Akemi
Hi Akemi,
On Thu, 2007-05-10 at 18:13 -0700, Akemi Yagi wrote:
Tried your new yum on couple of C4 i386 boxes. It is significantly faster than the previous version. Here is the output of a 'yum check-update' :
Thanks for testing this!
The total time from the "before" run was 36.88 seconds. It was < 5 seconds "after" the update. By the way, why is it that the updated version does not show info like the number of packages and the elapsed time?
This was disabled by a patch from Fedora. The reason seems to be to avoid tree compose breakage.
Thanks, Daniel
I'll try it on my CentOS boxes in next days. I hope to get the same good results as Akemi. Indeed I think the C meta-data parser was a _needed_ improvement in YUM. The tradicional python-based meta-data parser manager is very slow; too much slow sometimes.
I'll post here my times ouputs soon.
Original Message:
We have added yum 2.4.3 updates for CentOS 3 and 4 to the CentOS testing repository. These packages introduce the following changes:
* CentOS 4: yum now requires the yum-metadata-parser package. This is a backport of the yum C metadata parser, and provides an significant performance increase over the Python metadata parser.
* CentOS 3: this is the first release of yum 2.4 for CentOS 3, and we plan to provide this as an optional upgrade through the CentOSPlus repository. We have added code to yum 2.4 for default kernel handling (as setting the default kernel after kernel updates was handled by yum 2.0). Additionally, the package also requires the yum C metadata parser.
Please test these RPMs, and provide feedback. We are especially interested in stress testing of the new components (default kernel handling on CentOS 3, and the C metadata parser on CentOS 3 and 4).
========================================================================
The new yum loaded easily and properly on C4. Am very impressed with the TREMENDOUS increase in speed!
On Thu, 10 May 2007, Daniel de Kok wrote:
We have added yum 2.4.3 updates for CentOS 3 and 4 to the CentOS testing repository. These packages introduce the following changes:
CentOS 4: yum now requires the yum-metadata-parser package. This is a backport of the yum C metadata parser, and provides an significant performance increase over the Python metadata parser.
CentOS 3: this is the first release of yum 2.4 for CentOS 3, and we plan to provide this as an optional upgrade through the CentOSPlus repository. We have added code to yum 2.4 for default kernel handling (as setting the default kernel after kernel updates was handled by yum 2.0). Additionally, the package also requires the yum C metadata parser.
I'm both surprised and pleased :)
Thank you Daniel !
-- dag wieers, dag@wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]
On 5/10/07, Daniel de Kok daniel@centos.org wrote:
Hi all,
We have added yum 2.4.3 updates for CentOS 3 and 4 to the CentOS testing repository. These packages introduce the following changes:
Have folks had a chance to test these on x86_64 boxen as well?
So far the response seems to have been overwhelmingly positive for the c4 series. Anyone out there using the centos3 yum updates?
Jim Perrin wrote:
On 5/10/07, Daniel de Kok daniel@centos.org wrote: So far the response seems to have been overwhelmingly positive for the c4 series. Anyone out there using the centos3 yum updates?
I am, it was very simple to setup, it honoured my previous yum.conf.
updating, listing and installing was really fast compared with the old yum... real real fast... The original yum on centos3 is quite slow... this new one does the job in a blink.
I installed it on 2 CentOS-3 servers today. I will report any problem, if found.
regards epe
On Thu, 2007-05-10 at 21:56 +0200, Daniel de Kok wrote:
Hi all,
We have added yum 2.4.3 updates for CentOS 3 and 4 to the CentOS testing repository. C<snip>
Information on using the CentOS Testing repository can be found on the CentOS Wiki at:
http://wiki.centos.org/Repositories
Thanks, Daniel
<snip sig stuff>
Installed just fine. Converted cache format from version 6 to 10 fine. Updated two packages from rpmforge. Seems "peppier". NP to report.
HTH -- Bill
On Thu, 10 May 2007 21:56:09 +0200 Daniel de Kok daniel@centos.org wrote:
- CentOS 3: this is the first release of yum 2.4 for CentOS 3, and we plan to provide this as an optional upgrade through the CentOSPlus repository. We have added code to yum 2.4 for default kernel handling (as setting the default kernel after kernel updates was handled by yum 2.0). Additionally, the package also requires the yum C metadata parser.
Any folks out there who have tested this on CentOS 3 yet? We'd really like to get some feedback on how well this works, especially with the new kernel update handling.
-- Daniel
On 5/16/07, Daniel de Kok daniel@centos.org wrote:
On Thu, 10 May 2007 21:56:09 +0200 Daniel de Kok daniel@centos.org wrote:
- CentOS 3: this is the first release of yum 2.4 for CentOS 3, and we plan to provide this as an optional upgrade through the CentOSPlus repository. We have added code to yum 2.4 for default kernel handling (as setting the default kernel after kernel updates was handled by yum 2.0). Additionally, the package also requires the yum C metadata parser.
Any folks out there who have tested this on CentOS 3 yet? We'd really like to get some feedback on how well this works, especially with the new kernel update handling.
-- Daniel
Just wanted to make sure you did not miss this post earlier in this thread:
http://lists.centos.org/pipermail/centos-devel/2007-May/003583.html
Ing. Ernesto Pérez Estévez tested it on 2 CentOS-3 servers...
Akemi
Daniel de Kok wrote:
On Thu, 10 May 2007 21:56:09 +0200 Daniel de Kok daniel@centos.org wrote: Any folks out there who have tested this on CentOS 3 yet? We'd really like to get some feedback on how well this works, especially with the new kernel update handling.
Hi, sorry, I sent the following mail from a different address, and I guess it got defferred by mailman, here it goes again, it is regarding CentOS 3 and the new yum (actually the new sqlite):
MailScanner uses perl-DBD-SQLite to create a spamassassin cache database
To upgrade my yum (dev.centos.org repos) in my CentOS-3 I had to upgrade sqlite as well.
After that MailScanner refused to start because of an error:
In Debugging mode, not forking... /usr/bin/perl: relocation error: /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/auto/DBD/SQLite/SQLite.so: undefined symbol: dbd_st_finish
Then I got perl-DBD-SQlite SRC.RPM from rpmforge, and recompiled it with the new sqlite :
sqlite-3.3.6-2 sqlite-devel-3.3.6-2
And installed (updated) this newly recompiled perl-DBD-SQLite, it now works.
My suggestion is: to offer perl-DBD-SQLite's rpms in the dev.centos.org rpms, otherwise perl-DBD-SQLite will stay behind, compiled for the original sqlite and it will fail to work.
regards epe
Ing. Ernesto Pérez Estévez wrote:
MailScanner uses perl-DBD-SQLite to create a spamassassin cache database In Debugging mode, not forking... /usr/bin/perl: relocation error: /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/auto/DBD/SQLite/SQLite.so: undefined symbol: dbd_st_finish
thats a reflection of the really bad way MailScanner is packaged up. iirc, it actually builds most of the rpms it needs at install time - so the fix there is going to be to reinstall MailScanner.
My suggestion is: to offer perl-DBD-SQLite's rpms in the dev.centos.org rpms, otherwise perl-DBD-SQLite will stay behind, compiled for the original sqlite and it will fail to work.
I dont think thats a good idea at all, if the perl-DBD-SQLite installed already on your machine is going to no longer work, its dep chain should reflect that and let you know.
- KB
On Thu, 2007-05-17 at 01:22 +0200, Daniel de Kok wrote:
On Thu, 10 May 2007 21:56:09 +0200 Daniel de Kok daniel@centos.org wrote:
- CentOS 3: this is the first release of yum 2.4 for CentOS 3, and we plan to provide this as an optional upgrade through the CentOSPlus repository. We have added code to yum 2.4 for default kernel handling (as setting the default kernel after kernel updates was handled by yum 2.0). Additionally, the package also requires the yum C metadata parser.
Any folks out there who have tested this on CentOS 3 yet? We'd really like to get some feedback on how well this works, especially with the new kernel update handling.
-- Daniel
Daniel,
As you know (though I can also post to this list) ...
I did test this on a real install of i386 and x86_64 for CentOS-3, including kernel upgrades.
I also did stand up 2 other VMWare VM's (one of each C3 i386 and x86_64) for detailed testing (group installs, etc.).
It did have WorksForMe(TM) status on those 4 machines.
Thanks, Johnny Hughes
Daniel de Kok wrote:
On Thu, 10 May 2007 21:56:09 +0200 Daniel de Kok daniel@centos.org wrote:
- CentOS 3: this is the first release of yum 2.4 for CentOS 3, and we plan to provide this as an optional upgrade through the CentOSPlus repository. We have added code to yum 2.4 for default kernel handling (as setting the default kernel after kernel updates was handled by yum 2.0). Additionally, the package also requires the yum C metadata parser.
Any folks out there who have tested this on CentOS 3 yet? We'd really like to get some feedback on how well this works, especially with the new kernel update handling.
-- Daniel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
I got this after upgrading on my C3 box.
# yum update Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 24, in ? import cli File "/usr/share/yum-cli/cli.py", line 27, in ? from optparse import OptionParser ImportError: No module named optparse
On 5/17/07, Linux Rockz LinuxRockz@gmail.com wrote:
I got this after upgrading on my C3 box.
# yum update Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 24, in ? import cli File "/usr/share/yum-cli/cli.py", line 27, in ? from optparse import OptionParser ImportError: No module named optparse
Hmm. I've updated 10 CentOS 3 servers now without a hitch. I'm guessing something didn't get updated as python can't find the optparse module. Here's a snip from my yum.log for the upgrade:
May 17 10:58:06 Dep Installed: python-sqlite 1.1.7-1.2.1.i386 May 17 10:58:06 Dep Installed: sqlite 3.3.6-2.i386 May 17 10:58:06 Dep Installed: python-elementtree 1.2.6-5.el3.centos.i386 May 17 10:58:06 Dep Installed: yum-metadata-parser 1.1.0-2.el3.centos.i386 May 17 10:58:06 Dep Installed: python-urlgrabber 2.9.8-2.noarch May 17 10:58:06 Dep Installed: centos-yumconf 3-2.noarch May 17 10:58:06 Updated: yum 2.4.3-4.el3.centos.noarch
Grant McChesney wrote:
On 5/17/07, *Linux Rockz* <LinuxRockz@gmail.com mailto:LinuxRockz@gmail.com> wrote:
I got this after upgrading on my C3 box. # yum update Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 24, in ? import cli File "/usr/share/yum-cli/cli.py", line 27, in ? from optparse import OptionParser ImportError: No module named optparseHmm. I've updated 10 CentOS 3 servers now without a hitch. I'm guessing something didn't get updated as python can't find the optparse module. Here's a snip from my yum.log for the upgrade:
May 17 10:58:06 Dep Installed: python-sqlite 1.1.7-1.2.1.i386 May 17 10:58:06 Dep Installed: sqlite 3.3.6-2.i386 May 17 10:58:06 Dep Installed: python-elementtree 1.2.6-5.el3.centos.i386 May 17 10:58:06 Dep Installed: yum-metadata-parser 1.1.0-2.el3.centos.i386 May 17 10:58:06 Dep Installed: python-urlgrabber 2.9.8-2.noarch May 17 10:58:06 Dep Installed: centos-yumconf 3-2.noarch May 17 10:58:06 Updated: yum 2.4.3-4.el3.centos.noarch
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
I have all those packages installed ....
On Thu, 2007-05-17 at 17:25 -0500, Linux Rockz wrote:
I got this after upgrading on my C3 box.
# yum update Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 24, in ? import cli File "/usr/share/yum-cli/cli.py", line 27, in ? from optparse import OptionParser ImportError: No module named optparse
This module is part of the python-optik package that is a requirement for yum 2.4. Is python-optik installed?
-- Daniel
Daniel de Kok wrote:
On Thu, 2007-05-17 at 17:25 -0500, Linux Rockz wrote:
I got this after upgrading on my C3 box.
# yum update Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 24, in ? import cli File "/usr/share/yum-cli/cli.py", line 27, in ? from optparse import OptionParser ImportError: No module named optparse
This module is part of the python-optik package that is a requirement for yum 2.4. Is python-optik installed?
-- Daniel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
It was not installed. Shouldn't that be a req. dep then?
On Fri, 2007-05-18 at 07:33 -0500, Linux Rockz wrote:
Daniel de Kok wrote:
On Thu, 2007-05-17 at 17:25 -0500, Linux Rockz wrote:
I got this after upgrading on my C3 box.
# yum update Traceback (most recent call last): File "/usr/bin/yum", line 28, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 24, in ? import cli File "/usr/share/yum-cli/cli.py", line 27, in ? from optparse import OptionParser ImportError: No module named optparse
This module is part of the python-optik package that is a requirement for yum 2.4. Is python-optik installed?
-- Daniel
It was not installed. Shouldn't that be a req. dep then?
It should be, yes .... looks like something that we need to add to the combined spec file.
Thanks, Johnny Hughes
Daniel de Kok wrote:
On Fri, 2007-05-18 at 07:33 -0500, Linux Rockz wrote:
It was not installed. Shouldn't that be a req. dep then?
It is:
$ rpm -qRp yum-2.4.3-4.el3.centos.noarch.rpm | grep 'optik' python-optik
-- Daniel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
So how did yum get installed without complaining about the missing python-optik?
On Fri, 2007-05-18 at 18:52 -0500, Linux Rockz wrote:
So how did yum get installed without complaining about the missing python-optik?
--- # yum update yum [...] I will do the following: [update: yum 2.4.3-4.el3.centos.noarch] I will install/upgrade these to satisfy the dependencies: [deps: python-optik 1.4.1-2.noarch] [deps: python-sqlite 1.1.7-1.2.1.i386] [deps: sqlite 3.3.6-2.i386] [deps: python-elementtree 1.2.6-5.el3.centos.i386] [deps: yum-metadata-parser 1.1.0-2.el3.centos.i386] [deps: python-urlgrabber 2.9.8-2.noarch] [deps: centos-yumconf 3-2.noarch] [...] ---
Forgive me for asking, but did you install the yum update with "rpm --nodeps"?
-- Daniel
Daniel de Kok wrote:
On Fri, 2007-05-18 at 18:52 -0500, Linux Rockz wrote:
So how did yum get installed without complaining about the missing python-optik?
# yum update yum [...] I will do the following: [update: yum 2.4.3-4.el3.centos.noarch] I will install/upgrade these to satisfy the dependencies: [deps: python-optik 1.4.1-2.noarch] [deps: python-sqlite 1.1.7-1.2.1.i386] [deps: sqlite 3.3.6-2.i386] [deps: python-elementtree 1.2.6-5.el3.centos.i386] [deps: yum-metadata-parser 1.1.0-2.el3.centos.i386] [deps: python-urlgrabber 2.9.8-2.noarch] [deps: centos-yumconf 3-2.noarch] [...]
Forgive me for asking, but did you install the yum update with "rpm --nodeps"?
-- Daniel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
nope ;) Downloaded all the rpms and did rpm -Uvh *.rpm
On Sun, 2007-05-20 at 11:24 -0500, Linux Rockz wrote:
Daniel de Kok wrote:
On Fri, 2007-05-18 at 18:52 -0500, Linux Rockz wrote:
So how did yum get installed without complaining about the missing python-optik?
# yum update yum [...] I will do the following: [update: yum 2.4.3-4.el3.centos.noarch] I will install/upgrade these to satisfy the dependencies: [deps: python-optik 1.4.1-2.noarch] [deps: python-sqlite 1.1.7-1.2.1.i386] [deps: sqlite 3.3.6-2.i386] [deps: python-elementtree 1.2.6-5.el3.centos.i386] [deps: yum-metadata-parser 1.1.0-2.el3.centos.i386] [deps: python-urlgrabber 2.9.8-2.noarch] [deps: centos-yumconf 3-2.noarch] [...]
Forgive me for asking, but did you install the yum update with "rpm --nodeps"?
nope ;) Downloaded all the rpms and did rpm -Uvh *.rpm
Hmmm, did it happen to install python2.3 as a dependency? This package has a provides for python-optik, "blocking" the python-optik package from CentOS base being installed.
I just filed a bug for this:
http://bugs.centos.org/view.php?id=2152
-- Daniel
Daniel de Kok wrote:
Hmmm, did it happen to install python2.3 as a dependency? This package has a provides for python-optik, "blocking" the python-optik package from CentOS base being installed.
I just filed a bug for this:
Not related to this issue, but I have found a server where the new yum does not update default kernels correctly ("Could not determine the default kernel!). The only thing I see that could cause this, is that the server does not have a boot partition, so this is grub.conf (after manually updating default to 0):
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have no /boot partition. This means that # all kernel and initrd paths are relative to /, eg. # root (hd0,0) # kernel /boot/vmlinuz-version ro root=/dev/hda2 # initrd /boot/initrd-version.img #boot=/dev/sda default=0 timeout=5 #splashimage=(hd0,0)/grub/splash.xpm.gz title CentOS (2.4.21-50.EL) root (hd0,0) kernel /boot/vmlinuz-2.4.21-50.EL ro root=LABEL=/ initrd /boot/initrd-2.4.21-50.EL.img title CentOS (2.4.21-47.EL) root (hd0,0) kernel /boot/vmlinuz-2.4.21-47.EL ro root=LABEL=/ initrd /boot/initrd-2.4.21-47.EL.img
Is it possible that not having a boot partition is the reason for this failure? Otherwise I could try to look more closely.
Best Regards Michael Paesold
On Mon, 2007-06-18 at 12:58 +0200, Michael Paesold wrote:
Not related to this issue, but I have found a server where the new yum does not update default kernels correctly ("Could not determine the default kernel!). The only thing I see that could cause this, is that the server does not have a boot partition, so this is grub.conf (after manually updating default to 0):
What does
/sbin/grubby --grub --default-kernel
say?
-- Daniel
Daniel de Kok wrote:
On Mon, 2007-06-18 at 12:58 +0200, Michael Paesold wrote:
Not related to this issue, but I have found a server where the new yum does not update default kernels correctly ("Could not determine the default kernel!). The only thing I see that could cause this, is that the server does not have a boot partition, so this is grub.conf (after manually updating default to 0):
What does
/sbin/grubby --grub --default-kernel
say?
# /sbin/grubby --grub --default-kernel /boot/vmlinuz-2.4.21-50.EL
(i.e. the correct one according to the current grub.conf file)
Btw. I cannot say with 100% certainty that this was working before, so perhaps there was already a bug in the old yum. I just don't have much time to test downgrading to the old yum now. Still I can't remember that I had such an issue before on any CentOS 3 server. (I did have on some CentOS 2 boxes which had been upgraded from RedHat 7.0, which also showed problems with kernel default updates.)
Best Regards Michael Paesold
Daniel de Kok wrote:
On Thu, 10 May 2007 21:56:09 +0200 Daniel de Kok daniel@centos.org wrote:
- CentOS 3: this is the first release of yum 2.4 for CentOS 3, and we plan to provide this as an optional upgrade through the CentOSPlus repository. We have added code to yum 2.4 for default kernel handling (as setting the default kernel after kernel updates was handled by yum 2.0). Additionally, the package also requires the yum C metadata parser.
Any folks out there who have tested this on CentOS 3 yet? We'd really like to get some feedback on how well this works, especially with the new kernel update handling.
I have tested this on two CentOS 3 servers so far. There was no issue with pyhton-optik here (as mentioned in this thread):
..Dependencies resolved I will do the following: [update: yum 2.4.3-4.el3.centos.noarch] I will install/upgrade these to satisfy the dependencies: [deps: python-optik 1.4.1-2.noarch] [deps: python-sqlite 1.1.7-1.2.1.i386] [deps: centos-yumconf 3-2.noarch] [deps: sqlite 3.3.6-2.i386] [deps: python-elementtree 1.2.6-5.el3.centos.i386] [deps: yum-metadata-parser 1.1.0-2.el3.centos.i386] [deps: python-urlgrabber 2.9.8-2.noarch]
On one of the servers I use packages from rpmforge. I installed the priorities plugin, added some repository specific excludes etc. All works very well (and much faster now). I updated about 10 packages using the new yum and there were no issues.
Concerning the kernel update handling: There hasn't been a kernel update for CentOS 3 in quite some time, so it's hard to test on a production server. I will see if I can find some time to test this here on a server at the office. What are you concerned about most? A system with more than one kernel flavor installed?
Best Regards Michael Paesold
On Wed, 2007-05-23 at 11:16 +0200, Michael Paesold wrote:
Concerning the kernel update handling: There hasn't been a kernel update for CentOS 3 in quite some time, so it's hard to test on a production server. I will see if I can find some time to test this here on a server at the office. What are you concerned about most? A system with more than one kernel flavor installed?
Yes, well, at least two things could use some more testing:
- System with multiple kernel flavors (having more than one kernel in the update set). - Systems that use LILO.
Thanks for your testing so far!
-- Daniel
Daniel de Kok wrote:
On Wed, 2007-05-23 at 11:16 +0200, Michael Paesold wrote:
Concerning the kernel update handling: There hasn't been a kernel update for CentOS 3 in quite some time, so it's hard to test on a production server. I will see if I can find some time to test this here on a server at the office. What are you concerned about most? A system with more than one kernel flavor installed?
Yes, well, at least two things could use some more testing:
- System with multiple kernel flavors (having more than one kernel in
the update set).
- Systems that use LILO.
I don't use LILO on any system, so I can't help here. But I tested the kernel update for multiple kernel flavors. I downgraded a system to 2.4.21-47.EL and installed both the UP as well as the smp kernel.
After that I tried several variations of yum update, i.e. "yum update", "yum update kernel", "yum update kernel-smp", all variations with each of the kernel flavors set to default in /etc/grub.conf, and with one or both of the new versions of the kernel flavor uninstalled.
The behavior was correct for all cases. The new kernel was always set to default when the flavor had been default before, and it was never set to default when the flavor had not been default before.
When the default was set to the new version, a message was displayed: Setting default GRUB kernel to /boot/vmlinuz-2.4.21-47.0.1.EL or for the smp kernel: Setting default GRUB kernel to /boot/vmlinuz-2.4.21-47.0.1.ELsmp
Btw., this is a system previously upgraded from RedHat 9.0 to CentOS 3, so it was not just a clean install. Seems to work fine here!
Thanks for your testing so far!
Thank you very much for working on this! The new yum is so much better. I am looking forward to having this in the plus repo for CentOS 3.
Best Regards, Michael Paesold
Daniel de Kok napsal(a):
Hi all,
We have added yum 2.4.3 updates for CentOS 3 and 4 to the CentOS testing repository. These packages introduce the following changes:
CentOS 4: yum now requires the yum-metadata-parser package. This is a backport of the yum C metadata parser, and provides an significant performance increase over the Python metadata parser.
CentOS 3: this is the first release of yum 2.4 for CentOS 3, and we plan to provide this as an optional upgrade through the CentOSPlus repository. We have added code to yum 2.4 for default kernel handling (as setting the default kernel after kernel updates was handled by yum 2.0). Additionally, the package also requires the yum C metadata parser.
Daniel, any plans to pronounce both packages production safe and move to Centos repo? Thanks, David
Hi David,
On Fri, 2007-08-17 at 11:32 +0200, David Hrbác( wrote:
any plans to pronounce both packages production safe and move to Centos repo?
Wrt. the C3 version, the plan is to move the packages to CentOSPlus. There's still an issue that has to be worked out in the C4 version (yum-metadata-parser in C4 is newer than in C5, making C4 -> C5 upgrades problematic).
-- Daniel
-
"Ing. Ernesto Pérez Estévez" -
Akemi Yagi -
Dag Wieers -
Daniel de Kok -
Daniel de Kok -
David Hrbác( -
Fred Kienker -
Grant McChesney -
Jim Perrin -
Johnny Hughes -
Jordi Espasa Clofent -
Karanbir Singh -
Linux Rockz -
Michael Paesold -
William L. Maltby