I'm skeptical that we can fix this quickly enough, and it might not even be a good idea (to change the most important library under packagekit so shortly before a new release). But I think it does violate our release criterion:
https://fedoraproject.org/wiki/Fedora_42_Final_Release_Criteria#Installing,_removing_and_updating_software

Especially this one:

The displayed state of software or software sources must not differ from their actual state.

This assumes there's only one true repo state for the whole system. It doesn't account for what this bug caused, i.e. different parts of the system seeing the repo state differently. But that only accentuates the the problem, and shows that this is not a valid state based on our criteria.

I think this should be accepted as a blocker, and realistically, maybe marked as "hard-to-fix" and bumped to the next release (when we should definitely fix it), unless the libdnf change happens to be really trivial (which I doubt).

FinalBlocker +1

FinalBlocker +1

going by the criteria it's a

FinalBlocker +1

FinalBlocker +1

yeah, I have to agree with Kamil's evaluation here.
FinalBlocker +1
AGREED AcceptedFinalBlocker

The following votes have been closed:

• Accepted FinalBlocker (+5, 0, -0)
  • +1 by kparal, derekenz, augenauf, geraldosimiao, adamwill

Release F42 is no longer tracked by BlockerBugs, closing this ticket.