Hello community, here is the log from the commit of package podman for openSUSE:Factory checked in at 2019-01-08 12:26:59 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/podman (Old) and /work/SRC/openSUSE:Factory/.podman.new.28833 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "podman" Tue Jan 8 12:26:59 2019 rev:33 rq:662066 version:0.11.1.1 Changes: -------- --- /work/SRC/openSUSE:Factory/podman/podman.changes 2018-12-07 14:39:54.698735798 +0100 +++ /work/SRC/openSUSE:Factory/.podman.new.28833/podman.changes 2019-01-08 12:29:05.192232343 +0100 @@ -1,0 +2,5 @@ +Tue Dec 18 09:40:40 UTC 2018 - Marco Vedovati <[email protected]> + +- Update package summary and description + +------------------------------------------------------------------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ podman.spec ++++++ --- /var/tmp/diff_new_pack.wipKOT/_old 2019-01-08 12:29:05.832231645 +0100 +++ /var/tmp/diff_new_pack.wipKOT/_new 2019-01-08 12:29:05.836231640 +0100 @@ -26,7 +26,7 @@ Name: podman Version: 0.11.1.1 Release: 0 -Summary: Debugging tool for pods and images +Summary: Daemon-less container engine for managing containers, pods and images License: Apache-2.0 Group: System/Management Url: https://github.com/containers/libpod @@ -65,14 +65,12 @@ %endif %description -podman is a simple client only tool to help with debugging issues when daemons -such as CRI runtime and the kubelet are not responding or failing. A shared API -layer could be created to share code between the daemon and podman. podman does -not require any daemon running. podman utilizes the same underlying components -that crio uses i.e. containers/image, container/storage, -oci-runtime-tool/generate, runc or any other OCI compatible runtime. podman -shares state with crio and so has the capability to debug pods/images created -by crio. +Podman is a container engine for managing pods, containers, and container +images. +It is a standalone tool and it directly manipulates containers without the need +of a container engine daemon. +Podman is able to interact with container images create in buildah, cri-o, and +skopeo, as they all share the same datastore backend. %prep %setup -q
