I've got some packages updated (mostly in experimental): - golang-github-vbauerster-mpb_5.0.3-1_source.changes ACCEPTED into experimental - golang-github-openshift-api_4.0+git20190508.81d064c-4_source.changes ACCEPTED into unstable - golang-github-shirou-gopsutil_2.19.11-2_source.changes ACCEPTED into unstable - golang-github-opencontainers-selinux_1.5.1-2_source.changes ACCEPTED into unstable - golang-github-containers-storage_1.20.2-1_source.changes ACCEPTED into experimental - golang-github-containers-image_5.5.1-2_source.changes ACCEPTED into experimental - golang-github-containers-buildah_1.15.0-1_source.changes ACCEPTED into experimental - golang-github-containers-psgo_1.5.1-1_source.changes ACCEPTED into unstable - golang-github-gorilla-mux_1.7.4-1_source.changes ACCEPTED into unstable - skopeo_1.1.0-1_source.changes ACCEPTED into experimental
I think most of those packages currently in experimental need coordinated uploads because of incompatible changes introduced in golang-github-vbauerster-mpb_5.0.3-1. But for now, I think we should be good to update libpod at least in experimental. Best, -rt On Mon, Jul 6, 2020 at 7:36 AM Reinhard Tartler <siret...@debian.org> wrote: > Source: libpod > Severity: wishlist > > Podman 2.0 is going to be supported in RHEL 8.3 long term and is thus a > great candidate for inclusion into Debian bullseye. Let's try to get it > packaged for debian. > > I've looked at https://github.com/containers/libpod/blob/v2.0/go.mod to > understand what packages in Debian needs work for this new upstream. > > These packages needs packaging. In some cases, it might make sense to > keep the package vendored in the libpod source package. I would suggest > to prioritize working on these packages: > > github.com/hpcloud/tail v1.0.0 (NOT PACKAGED?) > github.com/gorilla/schema v1.1.0 (NOT PACKAGED?) > github.com/containers/common v0.14.3 (stuck in NEW) > > github.com/cri-o/ocicni v0.2.0 (NOT PACKAGED?) > github.com/opencontainers/runtime-spec > v1.0.3-0.20200520003142-237cc4f519e2 (NOT PACKAGED?) > github.com/uber/jaeger-client-go v2.24.0+incompatible (NOT > PACKAGED) > github.com/uber/jaeger-lib v2.2.0+incompatible // indirect (NOT > PACKAGED) > > > These are dependencies that we have in debian but in an older > version. This may or may not be required for podman 2.0, but updating > them might be a good idea anyways: > > github.com/containers/image/v5 v5.5.1 (have: 5.0.0) > github.com/containers/storage v1.20.2 (have: 1.15) > github.com/containers/buildah v1.15.0 (have 1.11.6) > > github.com/containernetworking/cni > v0.7.2-0.20200304161608-4fae32b84921 (have 0.7.1) > github.com/containers/conmon v2.0.18+incompatible (have 2.0.9) > github.com/containers/psgo v1.5.1 (have 1.4.0) > github.com/coreos/go-systemd/v22 v22.1.0 (have 22.0) > github.com/google/shlex v0.0.0-20181106134648-c34317bd91bf > (have 0.0~git20150127) > github.com/gorilla/mux v1.7.4 (have 1.7.3) > github.com/onsi/ginkgo v1.13.0 (have 1.12.0) > github.com/onsi/gomega v1.10.1 (have 1.9.0) > github.com/opencontainers/image-spec > v1.0.2-0.20190823105129-775207bd45b6 (have 1.0.1) > > github.com/opencontainers/selinux v1.5.2 (have 1.3.1) > github.com/openshift/imagebuilder v1.1.6 // indirect (have > 1.1.4) > github.com/opentracing/opentracing-go v1.1.0 (have 1.0.2) > github.com/seccomp/containers-golang v0.5.0 (have 0.3.2) > github.com/sirupsen/logrus v1.6.0 (have 1.3.0) > github.com/spf13/cobra v0.0.7 (have 0.0.5) > github.com/stretchr/testify v1.6.1 (have 1.4.0) > go.etcd.io/bbolt v1.3.5 (have 1.3.3) > gopkg.in/yaml.v2 v2.3.0 (have 2.2.2) > > These packages are already uptodate, no further action needed: > > github.com/cyphar/filepath-securejoin v0.2.2 (have 0.2.2) > github.com/davecgh/go-spew v1.1.1 (have 1.1.1) > github.com/docker/distribution v2.7.1+incompatible (have 2.7.1) > github.com/docker/go-connections v0.4.0 (have 0.4.0) > github.com/docker/go-units v0.4.0 (have 0.4.0) > github.com/fsnotify/fsnotify v1.4.9 (have 1.4.9) > github.com/ghodss/yaml v1.0.0 (have 1.0.0) > github.com/godbus/dbus/v5 v5.0.3 (have: 5.0.3) > github.com/google/uuid v1.1.1 (have 1.1.1) > github.com/hashicorp/go-multierror v1.0.0 (have: 1.0.0) > github.com/json-iterator/go v1.1.10 (have 1.1.10) > github.com/mrunalp/fileutils v0.0.0-20171103030105-7d4729fb3618 > (have 0.0~git20200504) > github.com/opencontainers/go-digest v1.0.0 (have 1.0.0) > github.com/opencontainers/runtime-tools v0.9.0 (have 0.9.0) > github.com/pkg/errors v0.9.1 (have 0.9.1) > github.com/pmezard/go-difflib v1.0.0 (have 1.0.0) > github.com/rootless-containers/rootlesskit v0.9.5 (have 0.9.5) > github.com/spf13/pflag v1.0.5 (have 1.0.5) > github.com/syndtr/gocapability > v0.0.0-20180916011248-d98352740cb2 (have 0.0+git20180916) > github.com/varlink/go v0.0.0-20190502142041-0f1d566d194b (have > 0.3.0) > github.com/vishvananda/netlink v1.1.0 (have 1.1.0) > > > These packages may need special handling, I'm not sure in what other > category these fall into. Dmitry, golang team, can you please share your > opinion how we should proceed with these: > > github.com/opencontainers/runc v1.0.0-rc90 (have: > 0.0~git20190911) > github.com/docker/docker v1.4.2-0.20191219165747-a9416c67da9f > (have 19.03) > > golang.org/x/crypto v0.0.0-20200423211502-4bdfaf469ed5 > golang.org/x/net v0.0.0-20200520004742-59133d7f0dd7 > golang.org/x/sync v0.0.0-20200317015054-43a5402ce75a > golang.org/x/sys v0.0.0-20200519105757-fe76b779f299 > > k8s.io/api v0.18.4 > k8s.io/apimachinery v0.18.4 > k8s.io/client-go v0.0.0-20190620085101-78d2af792bab > > > -- System Information: > Debian Release: bullseye/sid > APT prefers testing > APT policy: (500, 'testing'), (50, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores) > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > -- regards, Reinhard
