On Thu Jun 19, 2003 at 08:12:05PM -0400, Charles A Edwards wrote: > > You're right though Vincent - it's been doing it over a number of > > releases. You'll find a few posts from me in the archives on it. > > Another point that can be irritating is that the naming scheme for the > mdk kernel is from time to time changed rather than remaining a > constant. > > A case in point is that I rebuilt and installed from the src.rpm > kernel-2.4.21-0.rc1.1mdk-1-1mdk(the current cooker kernel) on my 9.1 > system but because the naming scheme has been changed urpmi thinks that > kernel-2.4.21.0.18mdk is'newer' and wishes to install it as well as > 'upgrading' the kernel-
Well, kernel-2.4.21-0.rc1.1mdk should never have been used. The 2.4.21.0.18mdk is a pre-release 2.4.21, thus using 0.18mdk instead of 18mdk. This rc1 should have been 2.4.21.0.19mdk or something else equally appropriate. 2.4.21 final would be 2.4.21.1mdk. I don't know why that changed but it's only a big deal if you track cooker (if you're tracking cooker, why are you doing updates?). 2.4.21 or 2.4.22 will most likely be in 9.2 so the upgrade path is clear. Remember all the warnings about cooker? They're all true. =) -- MandrakeSoft Security; http://www.mandrakesecure.net/ Online Security Resource Book; http://linsec.ca/ "lynx -source http://linsec.ca/vdanen.asc | gpg --import" {FE6F2AFD : 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD}
pgp00000.pgp
Description: PGP signature
