On Thu, 2016-11-24 at 20:39 +0100, László Böszörményi (GCS) wrote: > Your changes seem to be correct. I plan to upload the attached diff > in some hours if you don't mind.
It is now present in unstable. However the buildd status seems bad. ppc64el due to segfault during python2 test. kfreebsd-* had never compiled protobuf since 3.x.x release. armel,armhf,hppa,i386,mips,mipsel,powerpc,x32 failed during python3 test due to the same reason: Traceback (most recent call last): File "/«PKGBUILDDIR»/python3/google/protobuf/internal/reflection_test.py", line 639, in testIntegerTypes TestGetAndDeserialize('optional_uint32', 1 << 31, long) NameError: name 'long' is not defined There is no "long" type in python3, so this is an upstream py2 -> py3 porting bug. See: https://github.com/google/protobuf/issues/1504 I looked into protobuf's code at master branch and it seems to be solved: https://github.com/google/protobuf/blob/master/python/google/protobuf/internal/reflection_test.py#L658-L659 https://github.com/google/protobuf/blob/master/python/google/protobuf/internal/reflection_test.py#L642-L645 Should we consider to cherry-pick the corresponding upstream commit to Debian's protobuf 3.0.0 package or, to import protobuf 3.1.0 (maybe impossible due to transition freeze) ? [1] https://buildd.debian.org/status/logs.php?pkg=protobuf&ver=3.0.0-8 [2] https://github.com/google/protobuf/releases