What is going on with the kernel releases. First a package named "kernel-2.2.13-12mdk" appears on the mirrors that solved the raid problem I had (with a changelog that said the raid path was added), so far cool. But the next day a package named "kernel-2.2.13-11mdk" appears which guess what? have the same changelog but no raid support :-( ... ... Anyway, there is something wrong with the cooker building environment since I have noticed several anomalies: 1. packages appear with a new date stamp, new changelogs (and by this I suppose the package is different) but with the same patchlevel as the previous package. I have examined some of these cases, and indeed there was achange in the package, but no change in version designation. 2. packages appear with a certain patchlevel designation, and then a newer package follows with a lower patchlevel ???? (ex. - the kernel case I just mentioned) Is this caused by human error? Because if not, the there are bugs in the building environment. These may seem like small glitches, but this causes havoc on automatically upgraded systems (Yes, I do automatically upgrade my system to the cooker mirror, is this crazy or brave?); and at the least it renders the use package version designation useless. I know I may look like a whiner with my long posts, but I just want to put my grain of salt to build better distros for everyone. Thanks, ===== Eugenio Diaz, BSEE/BSCE Linux Engineer [EMAIL PROTECTED] __________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com
