The backtrace I posted was completely wrong, sorry, because I had a different libdnf on the system where I got it. The correct backtrace should be the one at https://bugzilla.redhat.com/show_bug.cgi?id=1727424 .
openQA testing indicates that this is causing crashes in PackageKit. This happens in the test which tests enrolling to a FreeIPA domain using Cockpit (which does some package installs via PK, IIRC) and in the GNOME desktop update test, when refreshing available updates. Tarballs of /var/log and the crash dump directories can be found in affected tests, like this one - coredump.tar.gz is the coredumpctl-captured dump, spoolabrt.tar.gz is the ABRT-captured crash directory, and var_log.tar.gz has the entire contents of /var/log .
It should be pushable right now, but for some reason Bodhi claims it isn't. The required wait time is 14 days, and it was pushed to testing 24 days ago, but if you try and push it, Bodhi says:
"This critical path update has not yet been approved for pushing to the stable repository. It must first reach a karma of 2, consisting of 0 positive karma from proventesters, along with 2 additional karma from the community. Or, it must spend 14 days in testing without any negative feedback Additionally, it must pass automated tests."
since this is causing real problems for real people, I'm gonna change my karma to +1 to see if that will fix it. Next time I really wish people would submit updates properly. :(
This update is not installable on top of current stable F29:
Problem: package crypto-policies-20190527-1.git0b3add8.fc29.noarch conflicts with nss < 3.44.0 provided by nss-3.43.0-1.fc29.x86_64 - cannot install the best update candidate for package nss-3.43.0-1.fc29.x86_64 - cannot install the best update candidate for package crypto-policies-20190211-2.gite3eacfc.fc29.noarch
It should have been included in the NSS update (https://bodhi.fedoraproject.org/updates/FEDORA-2019-e2f5e10754 ) rather than being submitted as a separate update, or not submitted until that update went stable.
Please do not push this until that update has gone stable.
Ah, OK - if you were already on top of this, that's fine, I just wanted to be sure :)
For future reference: when creating an update through the webUI you can include multiple builds when you create it, and/or you can also edit an existing update and add new builds to it, so long as those builds are not already in another update. I'm not sure offhand how to do it with the CLI as I don't usually create updates that way, but it's probably possible.
This and https://bodhi.fedoraproject.org/updates/FEDORA-2019-afc9c91690 (the corresponding 'fuse' package update) should not have been submitted separately, as this creates a dependency problem if that update is pushed stable before this one. They should have been submitted together. I am -1ing both updates to ensure they cannot be submitted for stable automatically in the wrong order. Please ensure you push this one stable manually first, then once it has gone stable, push the fuse update stable.