@labbott, it seems that #1701226 was added here by accident, however I cannot edit the update without specifying the severity.

No regressions noted.

Basic screenshotting works.

Updating from selinux-policy-targeted-3.14.2-49.fc29 to selinux-policy-targeted-3.14.2-51.fc29 - the scriptlet turned my CPU into a grill, my X session and Xfce desktop crashed and dnf failed mid transaction.

Thanks. That helps.

Could you please check (after upgrade):

$ rpm -q --requires singularity-runtime | grep python3
$ rpm -qf /usr/bin/python3
$ rpm -q --whatprovides /usr/bin/python3

And if you have singularity installed and do the update, python36 is not installed?

For the record: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/YHB4K7Z3FJCNLTMU7RPYSVZ2XLTAUHR3/

Let me just say that if other RPM packages actually depend on /usr/bin/python3, you'll get /usr/bin/python3. However if non RPM software you use depends on it, you are now in trouble. So what you expect is a reasonable thing to ask.

Thanks. I'll move this to the mailing list (a better place to discuss this).

And what would you want it to do?

What does yum --enablerepo=epel-testing update actually do then?

(I'll send it.)

I consider raising a new warning as a change of API, but I realize that it is probably disputable. Anyway, the update is in stable, probably to late to change anything, let's not bike shed then. I was surprised by this, and others might be as well. I'd consider an e-mail to dependent package maintainers as a reasonable thing to do.

Are we sure this is API compatible enough to go into stable Fedoras? See for example https://bugzilla.redhat.com/show_bug.cgi?id=1692172

I've added a build of python36 that has explicit conflicts with previous versions of python34.

Makes python3 build again (except test_asyncio).

Adding karma to my own fix, but I've verified the fix is working:

<mock-chroot> sh-5.0# rpm -q rpmlint
rpmlint-1.10-22.fc30.noarch
<mock-chroot> sh-5.0# rpmlint rpm*
...
6 packages and 0 specfiles checked; 4 errors, 57 warnings.

For the record, this broke Python https://bugs.python.org/issue36263

python2-txsocksx-0:1.15.0.2-10.fc30.noarch need python2-parsley on F30.