Sadly I think the damage is already done as the mozjs60 updates went out to updates-testing and rawhide last night, and I don't think there's much point any more in adding conflicts retroactively now -- it won't fix the systems that already have gotten the mozjs60 update. I'll go talk to releng to see if they can do an updates push with the fix quickly.
If I understand this right, the issue here is that pungi doesn't "see" the package that is supposed to pull in glib-networking because it comes from a different repo (the stable repo), so it thinks glib-networking is a leaf package and doesn't make it multilib.
The way it's suppsosed to work is that all -devel packages are multilibbed by pungi, so libsoup-devel is multilib, which pulls in libsoup, which in turn pulls in glib-netowkring, making it too multilib. However, libsoup-devel and libsoup aren't in the testing repo so it all falls apart. They are of course in the base repo and it all should work correctly once pushed to stable.
I don't think this should warrant a -1 karma: we actually need the karma so that it can get pushed to stable and get properly multilibbed (multilib is working in stable repos, but apparently somewhat broken in testing).
@augenauf Sorry, this is not the right place for bugreports like this, and the negative karma is unwarranted. The bodhi system is for regression testing and this update clearly didn't regress the PyCharm repo in any way. Please contact the PyCharm repo owners or file a ticket against fedora-workstation-repositories on bugzilla. Thanks!
@ignatenkobrain @walters Can you guys fix up the platform-python bits please? I know nothing of it, just submitted the update that walters built. See https://src.fedoraproject.org/rpms/gpgme/pull-request/3 for background info. I'm also not at the computer right now so I'd appreciate help here, thanks.