Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1878909
Information from BlockerBugs App:
<img alt="1878909" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/1878909" />
Commented but haven't voted yet: kalev, kparal, adamwill, geraldosimiao, coremodule
The votes have been last counted at 2020-10-19 17:28 UTC and the last processed comment was #comment-696898
To learn how to vote, see:
I am not sure there's a lot of value in pulling this in: distro upgrades would get just as well fixed with a 0 day update. At the same time, I am not opposed to this either :)
So, pkgconf-pkg-config is installed by default (at least on Fedora Workstation), but just in x86_64 version. The i686 is not installed. So this does not pose problems to a default installation of release-blocking images and thus is not a blocker.
As a freeze exception, this doesn't need to be pulled in because of upgrades (that will get solved on the release day if the fix is pending stable). But perhaps this is enough low risk and an actual problem you can hit on F33 right now that we could pull this in for this reason. However, I'm not clear how important it is to be able to install pkgconf-pkg-config.i686 - when do you need this?
@kparal we often take upgrade-affecting bugs as FEs on the grounds that it's good to fix upgrades ASAP, as people do upgrade during pre-release testing and after signoff but before "official" release.
The change here looks a tad beyond simple-and-definitely-safe though, as it involves a wrapper script and an rpm invocation. It already turned out to have one bug, which was the difference between -3 and -4. So I'd want quite convincing feedback that the update doesn't actually break anything else in order to be comfortable with an FE for this, I think.
Using the last updated (pkgconf-1.7.3-4.fc33) I managed to install both on my F33kde. Working fine. F33 KDE
Discussed during the 2020-10-19 blocker review meeting: 
The decision to classify this bug as an "AcceptedFreezeException (Final)" was made as it is a noticeable issue that cannot be fixed with an update.
The following votes have been closed:
Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)
Release F33 is no longer tracked by BlockerBugs, closing this ticket.
to comment on this ticket.