On Thu, Jan 7, 2021 at 10:59 PM Alberto Bertogli <albert...@blitiri.com.ar> wrote: > But those issues are not made worse by allowing golang-google-protobuf > to go in, right? >
Let golang-google-protobuf go in is one thing, it's not difficult. However without golang-goprotobuf 1.4.x it's not useful currently. But it will be changed if upstream has switched to golang-google-protobuf only. > What's blocking golang-google-protobuf from moving to testing now that > the dependency on golang-goprotobuf is no longer there? > > Is the issue that golang-google-protobuf source also builds a > protoc-gen-go? > protoc-gen-go has been splitted and built by golang-google-protobuf. But most upstream currently still use golang-goprotobuf to generate pb.go, and haven't switched to use protoc-gen-go provided by golang-google-protobuf, and protoc-gen-go-grpc provided by golang-google-grpc-dev(which is not built by Debian currently). > Why can't the latter be split, so upstreams that include pre-generated > .pb.go (as is the official recommendation) can be included in Debian > as-is using the corresponding dependency? > I doubt it will work. Most upstream pb.go which is generated by new protoc-gen-go(provided by golang-goprotobuf/1.4), depends on both golang-goprotobuf and golang-google-protobuf, and need golang-goprotobuf/1.4 -- Shengjing Zhu
