Comment 2 for bug 1946376

Proposal for addressing this:

The following packages contain vendored source:
* golang-github-containernetworking-plugins-dev
* golang-github-docker-docker-dev

This can cause problems if other packages end up including both the
package containing the vendored source, and the equivalent
non-vendored source.

To address this, I propose the following:
1) Make adjustments to packages that need build-dependency changes and
can be done in a way that is compatible with both the current and
proposed versions of {containernetworking-plugins,docker-docker}-dev:
* golang-github-containers-buildah
* golang-github-containers-common
* golang-github-containers-image
* golang-github-fsouza-go-dockerclient
* golang-github-openshift-imagebuilder
* golang-github-tonistiigi-fsutil
* prometheus
* skopeo
* golang-github-opencontainers-specs (just sync from Debian)

By starting with these over half the affected packages can be solved
now and not have to be uploaded in lockstep with the changes, since
the changes they need are compatible with packages in jammy or
jammy-proposed right now and are also compatible with the proposed
changes for later steps.

2) Do these in lockstep
* golang-github-containernetworking-plugins - devendor the dev package
* docker.io - devendor the dev package
* crowdsec - patch for build-depends
* runc - sync unchanged from Debian
* libpod - sync + patch for build-depends

Two other packages have build-depends on the packages that provide
vendored source, but are not affected by the changes
* golang-github-samalba-dockerclient
* golang-gthub-containers-dnsname

See ppa-patches.tgz for a dirty version of the debdiffs above.
If we wish to proceed I will cleanup the package versions and request
sponsorship.