On May 6, 2009, at 5:58 PM, Michael Jennings wrote:

>>
>> Basically that leaves a back-door where a later install/upgrade
>> of the Obsolete:'d package(s) is permitted. The issue is periodically
>> re-discovered and invariably leads to
>> 	RPM sux!
>> conclusions.
>>

So how do I solve this problem? For better or worse, packages
do get renamed, and its common packaging practice to add an Obsoletes:
when doing so. It just doesn't work like expected.

(other quite cogent arguments snipped but not ignored)

73 de Jeff