@lucaskanashiro: This patch is for golang-github-containers-common source package. This source package produces golang-github-containers-common-dev binary package, which is just source code on filesystem. But podman binary package, which is produced from libpod source package, has golang-github-containers-common-dev in its Build-Depends. It doesn't depend on golang-github-containers-common-dev during runtime. So when golang-github-containers-common is updated, libpod should be rebuilt. Should I keep libpod as confirmed, and make a patch against libpod to make a rebuild?
@lucaskanashiro: This patch is for golang- github- containers- common source package. This source package produces golang- github- containers- common- dev binary package, which is just source code on filesystem. But podman binary package, which is produced from libpod source package, has golang- github- containers- common- dev in its Build-Depends. It doesn't depend on golang- github- containers- common- dev during runtime. So when golang- github- containers- common is updated, libpod should be rebuilt. Should I keep libpod as confirmed, and make a patch against libpod to make a rebuild?
@neil-aldur: I'll try to reproduce.