Bug#961814: Debian Bugs information: logs for Bug#961814

2020-08-03 Thread Reinhard Tartler
Thanks!

Will incorporate in the next upload.


Bug#961814: Debian Bugs information: logs for Bug#961814

2020-08-03 Thread Reinhard Tartler
On Mon, Aug 3, 2020 at 8:30 AM Shengjing Zhu  wrote:

> If I read the comments in upstream issue correctly, it will be solved in 2
> months (they said 6 months later at April). What's the urgent thing we need
> to address in this two months?
>

I realized that podman 2.0 requires this newer version of protobuf. I've
changed podman to vendor the sources for now. Urgency is in the eye of the
beholder, I guess.

It just seems weird to me to not be able to use this package until this bug
is addressed.

-rt


Bug#961814: Debian Bugs information: logs for Bug#961814

2020-08-03 Thread Shengjing Zhu
If I read the comments in upstream issue correctly, it will be solved in 2
months (they said 6 months later at April). What's the urgent thing we need
to address in this two months?

// send from my mobile device

Reinhard Tartler  于 2020年8月3日周一 19:38写道:

>
>
>
>>From: Shengjing Zhu 
>>To: Debian Bug Tracking System 
>>Subject: Not ready for using
>>Date: Fri, 29 May 2020 23:36:43 +0800
>>
>> Package: golang-google-protobuf
>> Severity: serious
>>
>> Though it has been packaged, it's not ready for using.
>>
>> The current version will generate .pb.go files which requires
>> v1.4+ version of `github.com/golang/protobuf/proto`
>> .
>> See the reason at https://github.com/golang/protobuf/issues/1077
>>
>> Besides, I split the /bin/protoc-gen-go to a separated package.
>> Now two packages offer /bin/protoc-gen-go:
>>
>> + golang-goprotobuf-dev (1.3.x, by src:golang-goprotobuf):
>>   both /bin/protoc-gen-go and github.com/golang/protobuf/* files
>> + protoc-gen-go (1.23.0, by src:golang-google-protobuf):
>>   only /bin/protoc-gen-go
>>   Go files google.golang.org/protobuf/* are in golang-google-protobuf-dev
>>
>> The 1.23.0 version of protoc-gen-go will generate files which import
>> both google.golang.org/protobuf and github.com/golang/protobuf, and
>> require 1.4.0+ github.com/golang/protobuf.
>>
>> Any suggestions how can we move forward are appreciated.
>>
>> Maybe the easiest way is to wait upstream fixing issue #1077.
>>
>>
> Have you considered to revert upstream patch at
> https://go-review.googlesource.com/c/protobuf/+/218939/4/cmd/protoc-gen-go/internal_gengo/main.go
>  for
> debian locally? As far as I understand, this is the change (i.e., revert)
> upstream plans to make in a couple of months. I think Debian could move
> ahead with this to unblock other packages using this.
>
> What do you think?
>
> -rt
>
>
>


Bug#961814: Debian Bugs information: logs for Bug#961814

2020-08-03 Thread Reinhard Tartler
>From: Shengjing Zhu 
>To: Debian Bug Tracking System 
>Subject: Not ready for using
>Date: Fri, 29 May 2020 23:36:43 +0800
>
> Package: golang-google-protobuf
> Severity: serious
>
> Though it has been packaged, it's not ready for using.
>
> The current version will generate .pb.go files which requires
> v1.4+ version of `github.com/golang/protobuf/proto`
> .
> See the reason at https://github.com/golang/protobuf/issues/1077
>
> Besides, I split the /bin/protoc-gen-go to a separated package.
> Now two packages offer /bin/protoc-gen-go:
>
> + golang-goprotobuf-dev (1.3.x, by src:golang-goprotobuf):
>   both /bin/protoc-gen-go and github.com/golang/protobuf/* files
> + protoc-gen-go (1.23.0, by src:golang-google-protobuf):
>   only /bin/protoc-gen-go
>   Go files google.golang.org/protobuf/* are in golang-google-protobuf-dev
>
> The 1.23.0 version of protoc-gen-go will generate files which import
> both google.golang.org/protobuf and github.com/golang/protobuf, and
> require 1.4.0+ github.com/golang/protobuf.
>
> Any suggestions how can we move forward are appreciated.
>
> Maybe the easiest way is to wait upstream fixing issue #1077.
>
>
Have you considered to revert upstream patch at
https://go-review.googlesource.com/c/protobuf/+/218939/4/cmd/protoc-gen-go/internal_gengo/main.go
for
debian locally? As far as I understand, this is the change (i.e., revert)
upstream plans to make in a couple of months. I think Debian could move
ahead with this to unblock other packages using this.

What do you think?

-rt