Hi, On Sun, May 30, 2021 at 1:38 AM Pirate Praveen <[email protected]> wrote: > > Hi, > > I need github.com/grpc-ecosystem/grpc-gateway/v2 for a dependency of > gitlab (spamcheck) > > It has 3 reverse build dependencies. Should I do it as a normal > transition using same package names or create a new binary package? >
Using build-rdeps from devscripts. $ build-rdeps golang-github-grpc-ecosystem-grpc-gateway-dev Reverse Build-depends in main: ------------------------------ consul crowdsec docker-libkv docker.io etcd flannel gitlab-ci-multi-runner golang-github-census-instrumentation-opencensus-proto golang-github-containers-buildah golang-github-containers-common golang-github-containers-image golang-github-docker-leadership golang-github-fsouza-go-dockerclient golang-github-openshift-imagebuilder golang-github-optiopay-kafka golang-github-samalba-dockerclient golang-github-tonistiigi-fsutil golang-github-xordataexchange-crypt libpod nomad nomad-driver-lxc nomad-driver-podman prometheus singularity-container skopeo vip-manager golang-github-grpc-ecosystem-grpc-gateway-dev is used by some important packages. Have you rebuilt the reverse? If all goes well with /v2 (with patch or w/o patch), then you may don't need a new source/binary package. PS, if you want to make a new binary package with a new import path, it makes more sense to make a source package too. -- Shengjing Zhu
