avoid possible side-effects. Redhat didn't upgrade RH8's rpm over it's lifetime... so they must have deemed it stable (or stable enough). Do
Or, they knew that since they would EOL it shortly, why bother fixing it?
I suspect this has been somewhat true... also there is a limited amount of paid development labor hours and several operating systems being developed at once. Probably they wanted to avoid the support nightmare of people locking up during the rpm upgrade and freaking out. Worst case scenario is rpm is totally broken due to a lockup during upgrade... but I personally have not seen this happen.
we... or should we... rock the boat just to get a newer version of yum?
No, but we should rock the boat to help the project and project developers. My devel system (dual boot RH8 and RH9) is very broken now due to a corrupted rpm database caused by the buggy RPM in RH9. So, in order to develope for myself or FL I need to wipe out the system and re-install. This is a sever detriment to my development and to the project. Providing a stable rpm package that avoids database corruptions will help the project and its developers, and hence is worth rocking the boat.
Just my 2c ... this has been discussed to death already ;-)
Yes, but people keep missing the point. It isn't about yum, it is about a buggy rpm package.
Exactly.
Warren
