Hi all, Something related to protobuf has shifted in unstable, which is now causing gobgp to FTBFS. I've tried to figure out the correct way to fix it, but haven't been able to, so I'm asking the team for guidance. Currently building gobgp in unstable errors out with: > src/github.com/osrg/gobgp/api/attribute.pb.go:9:2: cannot find package "google.golang.org/protobuf/types/known/anypb" in any of: > /usr/lib/go-1.19/src/google.golang.org/protobuf/types/known/anypb (from $GOROOT) > /build/gobgp-2.34.0/obj-x86_64-linux-gnu/src/google.golang.org/protobuf/types/known/anypb (from $GOPATH) > src/github.com/osrg/gobgp/api/gobgp.pb.go:14:2: cannot find package "google.golang.org/protobuf/types/known/emptypb" in any of: > /usr/lib/go-1.19/src/google.golang.org/protobuf/types/known/emptypb (from $GOROOT) > /build/gobgp-2.34.0/obj-x86_64-linux-gnu/src/google.golang.org/protobuf/types/known/emptypb (from $GOPATH) > src/github.com/osrg/gobgp/api/gobgp.pb.go:15:2: cannot find package "google.golang.org/protobuf/types/known/timestamppb" in any of: > /usr/lib/go-1.19/src/google.golang.org/protobuf/types/known/timestamppb (from $GOROOT) > /build/gobgp-2.34.0/obj-x86_64-linux-gnu/src/google.golang.org/protobuf/types/known/timestamppb (from $GOPATH) If I replace golang-goprotobuf-dev with golang-google-protobuf-dev in the Build-Depends, the build proceeds further, but dies with: > src/github.com/osrg/gobgp/pkg/packet/bgp/prefix_sid.go:558:33: cannot use raw (variable of type *anypb.Any) as type *any.Any in argument to ptypes.UnmarshalAny > src/github.com/osrg/gobgp/pkg/packet/bgp/prefix_sid.go:604:35: cannot use stlvRaw (variable of type *anypb.Any) as type *any.Any in argument to ptypes.UnmarshalAny > src/github.com/osrg/gobgp/pkg/packet/bgp/prefix_sid.go:656:35: cannot use stlvRaw (variable of type *anypb.Any) as type *any.Any in argument to ptypes.UnmarshalAny I tried to add golang-github-golang-protobuf-1-5-dev to the Build- Depends, but another dependency is bringing in golang-github-golang- protobuf-1-3-dev which conflicts. Has this sort of issue bitten anyone else? I'd appreciate any pointers! Thanks, Mathias
Attachment:
signature.asc
Description: This is a digitally signed message part