[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#980432: ITP: golang-github-jhump-protoreflect -- Reflection (Rich Descriptors) for Go Protocol Buffers



Hello,

I'm not working on this package anymore.

The packaging itself was not hard to do, and you can find it at https://salsa.debian.org/go-team/packages/golang-github-jhump-protoreflect

However, the package does not build as is. It seems to require a more recent version of the golang protobuf thing (sorry I can't be more precise).

Here are my personal notes on the matter:

- Building against `golang-goprotobuf-dev 1.3.4-1` from Debian fails, due to #977652.
- Tried to vendor in golang-goprotobuf-dev, however the build breaks again.
- Bottom-line: Debian ships goprotobuf `1.3.4`, upstream goes with `1.4`. We NEED `1.4`.

That was a year ago. Looking at it today, nothing changed in unstable, but there is a recent version of goprotobuf in experimental:

  $ rmadison golang-goprotobuf-dev
  debian:
  golang-goprotobuf-dev | 1.3.4-2+b6 | stable
  golang-goprotobuf-dev | 1.3.4-2+b6 | testing
  golang-goprotobuf-dev | 1.3.4-2+b6 | unstable
  golang-goprotobuf-dev | 1.5.2-1~exp1 | experimental

So I think that the best approach would be to:

- try to build the package against golang-goprotobuf-dev from experimental to see if it works - maybe also update the packaging files of jhump-protoreflect, as upstream is now at version 1.10.1

From what I understand, it's not easy to update golang-goprotobuf in Debian unstable as it would break things. Cf https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=golang-goprotobuf.

Going forward, even if you manage to build jhump-protoreflect, I don't know what it would take to maintain it. It's about low-level Go stuff, code generation, and I don't understand any of that. That's also a reason why I gave up on the package.

I don't know who, if anyone, is working on updating golang-goprotobuf-dev in unstable. Maybe you should reach out on the Debian Go mailing list to ask.

All the best, and thanks for pinging me, I should have updated the ITP with this information long ago.

Cheers!

--
Arnaud Rebillout


Reply to: