Treat Obsoletes as Conflicts after installation
Obsoletes: have traditionally been implemented as an
installation directive rather than a dependency assertion.
This leads to flip-flop-flip behavior where a previously erased
package is then reinstalled by depsolvers using a broken dependency.
* Blueprints in grey have been implemented.