Comments

328 Comments

I get this error:

Transaction check error:
  file /usr/bin/distro from install of python36-distro-1.2.0-2.el7.noarch conflicts with file from package python2-distro-1.2.0-1.el7.noarch
karma

No regressions

@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.

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?

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).

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.

karma

Makes python3 build again (except test_asyncio).

BZ#1688284 Regression of OpenSSL 1.1.1b-1 in EVP_PBE_scrypt() with salt=NULL