So google-cloud (and a bunch of other packages) started failing after my
upgrade of grpc, because of a symbol change, and because we were not
regenerating protobufs on compilation.

This also caused #845453, and a bunch of other issues.

I have already prepared a replacement for google's proto definiions
(genproto), which regenerates all protobufs on build, and will solve
many of these issues. But we need to be careful to always regenerate
protobufs, because if the protobuf or grpc libraries change, they might
break again like this.

Also, a comment about google-cloud: I finally upgraded to a new version
(it seems they had releases after all, but not in github), so now it is
using the new import path, and the old one is kept for compatibility.
Also, I created a new upstream branch (upstream-ng) that follows git

I did not upload yet, as it depends on genproto passing NEW.

Also, the tests are accessing the network, so if anybody has some time,
please take a look at disabling the problematic ones. Upstream does not
even seem to have a bug tracker, so I could not report this.

On 30/11/16 10:57, Santiago Vila wrote:

> I tried to build this package in stretch with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)
> but it failed:

> src/ 
> undefined: grpc.SupportPackageIsVersion3
> src/
>  undefined: grpc.SupportPackageIsVersion3
> src/
>  undefined: grpc.SupportPackageIsVersion3

Martín Ferrari (Tincho)

Pkg-go-maintainers mailing list

Reply via email to