Description of problem: When installing podman-compose via the RPM from EPEL, the required runtime dependency python-dotenv is not installed automatically, causing podman-compose to fail at runtime unless the user manually installs it. This is a regression. Version-Release number of selected component (if applicable): podman-compose-1.5.0-1.el9 How reproducible: 100% Steps to Reproduce: 1. sudo dnf install podman-compose 2. create minimal podman-compose.yaml ``` version: "3.9" services: test: image: nginx:alpine ``` 3. run podman-compose up Actual results: Traceback (most recent call last): File "/bin/podman-compose", line 5, in <module> from podman_compose import main File "/usr/lib/python3.9/site-packages/podman_compose.py", line 39, in <module> from dotenv import dotenv_values ModuleNotFoundError: No module named 'dotenv' Error: executing /bin/podman-compose --help: exit status 1 Expected results: rpm requires core deps and runs as expected Additional info: This issue affects usability for users expecting podman-compose to function after RPM installation, and may cause confusion and additional bug reports.
FEDORA-EPEL-2025-d458fcf581 (podman-compose-1.5.0-2.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-d458fcf581
FEDORA-EPEL-2025-d458fcf581 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-d458fcf581 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-d458fcf581 (podman-compose-1.5.0-2.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.