Possibly missing dependencies in golang-github-docker-docker-dev

Bug #1883978 reported by Andreas Hasenack
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
docker.io (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

There is a big difference between the dependencies of golang-github-docker-docker-dev in debian and ubuntu:

https://pastebin.ubuntu.com/p/9d8XmsfGqT/

tl;dr ubuntu only has golang-github-docker-docker-credential-helpers-dev listed in Depends, whereas debian has tons more

This is possibly what caused the ftbfs in golang-github-fsouza-go-dockerclient (bug #1883960), as it builds fine in debian, but failed in ubuntu because of a missing golang-golang-x-crypto-dev b-d, which may come indirectly via golang-github-docker-docker-dev. I'm fixing that ftbfs by adding this b-d, but we should check why our golang-github-docker-docker-dev has so few depends.

Revision history for this message
Reinhard Tartler (siretart) wrote :

I think this is also affecting many other package builds, such as https://launchpad.net/ubuntu/+source/golang-github-containers-storage/1.20.2-3/+build/19612159

Didier, Roche, how do you feel about adding those dependencies to the ubuntu package?

Changed in docker.io (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Didier Roche (didrocks) wrote :

I don’t see any reason why we have a different set of dependencies, apart if docker has all of them vendorized in ubuntu for reason.

This is more a decision from the server team anyway, as it’s them who maintains this package.

Revision history for this message
Reinhard Tartler (siretart) wrote :

Didier, what's the best way to contact them? Can you subscribe people that would be able to advise / give guidance how to best resolve the FTBFS bugs mentioned above?

Revision history for this message
Robie Basak (racb) wrote :
tags: added: server-next
Revision history for this message
Lucas Kanashiro (lucaskanashiro) wrote :

After a discussion I have with Rheinard and Rick, we decided to keep docker.io package the way it is right now because this was a decision made sometime ago when we started to diverge from Debian. Long story short, in Ubuntu we use all the dependencies vendored (and not as regular dependencies on other debian packages) because we decided to keep backporting new versions of docker.io to supported LTS releases, and in the worst case scenario we would need to backport +120 packages (in the case where all the dependencies also need update). As you may know Golang dependencies are volatile and upstream developers update them, usually in their vendor directory, constantly. This is good because regardless of the LTS version you are using you have an updated version of docker.io.

The side effect of this decision is that library packages which depend on docker.io library might need to declare dependency on other packages that would be provided by the docker.io library package if we were in sync with Debian. I've seen some packages in this situation and for now the workaround is to add those dependencies like Andreas mentioned in the bug description. If the number of packages needing this workaround increases considerably we should revisit this topic.

tags: removed: server-next
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers