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

Re: Bug#934206: buster-pu: package golang-github-docker-docker-credential-helpers/0.6.1-2+deb10u1



On 8/9/19 5:15 PM, Adam D. Barratt wrote:
> The module apparently has three reverse build-dependencies:
>
> amazon-ecr-credential-helper:
> golang-github-docker-docker-credential-helpers-dev
> docker-pycreds: golang-docker-credential-helpers
> docker.io: golang-github-docker-docker-credential-helpers-dev (>= 0.6.1~)
>
> Would this update imply any of those needing to be rebuilt? If so, is
> that the end of the tree, or do we end up down a rabbit hole of Go
> libraries?

That's a good question. FWIW I tried this command, I got a different
result from you:

$ dose-ceve -T deb \
  --deb-native-arch=amd64 \
  -r golang-github-docker-docker-credential-helpers-dev \
 
debsrc:///var/lib/apt/lists/deb.debian.org_debian_dists_buster_main_source_Sources
\
 
deb:///var/lib/apt/lists/deb.debian.org_debian_dists_buster_main_binary-amd64_Packages
\
  | grep-dctrl -n -s Package '' \
  | sort -u
golang-docker-dev
golang-github-docker-docker-credential-helpers-dev
golang-github-docker-docker-dev
golang-github-fsouza-go-dockerclient-dev
golang-github-samalba-dockerclient-dev

I suppose that for every package ending with -dev in this list, we
should also get the reverse build-depends? Then we're going down the
rabbit hole.

But I'm not sure that following the reverse build-depends is the right
way to do it. Maybe following the Built-Using field is better.

Let me CC the Go team (question is: how to figure out which package to
rebuild after uploading
golang-github-docker-docker-credential-helpers-dev to stable).

Thanks,

  Arnaud




Reply to: