Comment 10 for bug 1272375

Ah I'm sorry, unlike in the other bugs I forgot to link to the python3.4 test logs in that one. I now updated the description to include it. So rebuilding s3ql to also include a 3.4 extension will mostly fix this bug. But the original failures that you also see with 3.3 will most likely still happen. If the upstream commit you linked to fixes those, then indeed all is well.

Note that Matthias' no-change rebuild only changed the default module to python 3.4 (https://launchpadlibrarian.net/163787523/buildlog_ubuntu-trusty-amd64.s3ql_2.7-1build1_UPLOADING.txt.gz), but the package actually needs to be fixed to build extensions for *all* supported python3 versions.