We've traced this down to a problem with the generation of the system-image delta at the time the image was promoted from the devel-proposed to the devel channel. The /usr/bin/python3.4 binary is missing from the delta, even though /usr/bin/python3.4m is present; as a result, anyone who was running version 1 of the image on the devel channel, and then upgraded, has the wrong (old) /usr/bin/python3.4 binary on their system.
This requires further investigation to understand both how the corruption of the delta happened, and how we can recover users on this channel who have applied the corrupted delta.
We've traced this down to a problem with the generation of the system-image delta at the time the image was promoted from the devel-proposed to the devel channel. The /usr/bin/python3.4 binary is missing from the delta, even though /usr/bin/python3.4m is present; as a result, anyone who was running version 1 of the image on the devel channel, and then upgraded, has the wrong (old) /usr/bin/python3.4 binary on their system.
This requires further investigation to understand both how the corruption of the delta happened, and how we can recover users on this channel who have applied the corrupted delta.