When doing an upgrade of my system I ran into an inability to upgrade packages due to a new openmotif being available (openmotif-2.2.3-r6 -> openmotif-2.2.3-r7), however the new openmotif depends on motif-config-0.9. The problem is that 0.9 blocks versions of openmotif prior to 2.2.3-r7, and this block prevents a smooth upgrade. I realize that I can get around this by unmerging one or both and remerging them, but that is the problem: this is a far from optimal solution, and should not be necessary. openmotif and motif-config should upgrade smoothly and cleanly; manually unmerging the old packages should not be required.
*** This bug has been marked as a duplicate of 79606 ***
