Adam W provided these examples:

Problem 1: package python2-ipaclient-4.7.3-2.fc29.noarch requires freeipa-client-common = 4.7.3-2.fc29, but none of the providers can be installed
- freeipa-client-common-4.7.3-2.fc29.noarch does not belong to a distupgrade repository
- problem with installed package python2-ipaclient-4.7.3-2.fc29.noarch
Problem 2: package python2-ipalib-4.7.3-2.fc29.noarch requires freeipa-common = 4.7.3-2.fc29, but none of the providers can be installed
- freeipa-common-4.7.3-2.fc29.noarch does not belong to a distupgrade repository
- problem with installed package python2-ipalib-4.7.3-2.fc29.noarch
Problem 3: package python2-libipa_hbac-2.2.0-3.fc29.x86_64 requires libipa_hbac = 2.2.0-3.fc29, but none of the providers can be installed
- libipa_hbac-2.2.0-3.fc29.x86_64 does not belong to a distupgrade repository
- problem with installed package python2-libipa_hbac-2.2.0-3.fc29.x86_64

See similar issue in https://bugzilla.redhat.com/show_bug.cgi?id=1684819

sorry, no, this is not what I meant.

this was already handled with obsoletes in fedora-obsolete-packages for F30 and F31. fedora-obsolete-packages is a package where we carry Obsoletes: that don't belong anywhere else. This broke because the obsoletes in that package were too low versioned: they were < 4.7.2-20 for the FreeIPA packages and < 2.1.0-20 for the one from sssd, but the versions of FreeIPA and sssd in F29 have gotten past those versions, so the obsoletes statements no longer took effect.

I have just sent out updates to fix this:

https://bodhi.fedoraproject.org/updates/FEDORA-2019-44e4f5d303
https://bodhi.fedoraproject.org/updates/FEDORA-2019-9e971b3d14

The packages were dropped in F30, there is nothing new in F32 here. In fact the obsoletes are removed from fedora-obsolete-packages in F32 because the policy is to carry them only for two releases (so, F30 and F31). As we don't support upgrades across more than two releases at once.

This issue should be closed.

Ok, closing.