Bug 1687555

Summary: include python subpackages
Product: Red Hat Enterprise Linux 8 Reporter: Lokesh Mandvekar <lsm5>
Component: podmanAssignee: Jindrich Novy <jnovy>
Status: CLOSED DUPLICATE QA Contact: atomic-bugs <atomic-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: ddarrah, dornelas, dwalsh, jligon, jwboyer, lsm5, mheon, pthomas, smccarty
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
python3-podman provides python bindings to allow python programs to easily interact with podman containers.
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 13:59:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1701002    

Description Lokesh Mandvekar 2019-03-11 17:53:33 UTC
Description of problem:

python-podman and python-pypodman need to be included in the podman package.

Comment 2 Daniel Walsh 2019-03-11 17:55:49 UTC
We only need podman3-python NOT pypodman.

Comment 3 Lokesh Mandvekar 2019-03-11 18:01:24 UTC
The python-podman package used to exist as a subpackage of podman but then upstream separated it into a new repo (https://github.com/containers/python-podman). Frantisek removed the python subpackage from podman https://pkgs.devel.redhat.com/cgit/rpms/podman/commit/?h=stream-container-tools-1.0&id=169bbe4c19e2ba74f1cd96862a9d16e0beccaa3b . I requested for a dist-git creation for python-podman at https://projects.engineering.redhat.com/browse/RCM-52450 but it's not done yet.

Comment 4 Daniel Walsh 2019-03-12 11:43:55 UTC
I don't see this as a blocker.  We can release the python library in 8.0.1 or later.

Comment 7 Daniel Walsh 2019-08-14 10:54:00 UTC
Jindrich, did this ever happen?

Comment 9 Jindrich Novy 2019-08-19 13:59:08 UTC

*** This bug has been marked as a duplicate of bug 1698072 ***