Comments

262 Comments

What is the plan here? Shall I unpush the update, or do we wait for the upstream fix?

Installing. Will do some basic testing, but I don't have a printer access ATM.

Either way, I won't do this and 4 months old bodhi update is not a proper place to have this conversation. Try the epel-devel mailing list.

karma

This update is not backwards compatible, see https://bugzilla.redhat.com/show_bug.cgi?id=1786893#c8 and below.

As an EPEL update, this does not fix BZ#1748018.

BZ#1748018 PYC magic number has changed, all pyc files must be re-created

Out of curiosity, why is this called "python3-0-10.f26container"?

As an EPEL update, this does not fix BZ#1748018.

BZ#1748018 PYC magic number has changed, all pyc files must be re-created

As an EPEL update, this does not fix BZ#1748018.

BZ#1748018 PYC magic number has changed, all pyc files must be re-created

As an EPEL update, this does not fix BZ#1748018.

BZ#1748018 PYC magic number has changed, all pyc files must be re-created

As an EPEL update, this does not fix BZ#1748018.

BZ#1748018 PYC magic number has changed, all pyc files must be re-created

As an EPEL update, this does not fix BZ#1748018.

BZ#1748018 PYC magic number has changed, all pyc files must be re-created

Starts fine. Lets me submit this karma.

THis is an epel update and as such, it cannot fix bz1748018.

BZ#1748018 PYC magic number has changed, all pyc files must be re-created

Feel free to open a bugzilla report or a thread on the python-devel mailing list, discussing this over an unrelated update in Bodhi is not efficient.

Is that a difference from the previous version? May I suggest using mock? https://fedoraproject.org/wiki/Using_Mock_to_test_package_builds

I've created a buildroot override for this, so Koschei can catch potential problems before it is pushed.