Description of problem: After applying update to python3-docker that replaces python3-docker-py (currently on updates-testing) docker-squash fails with a traceback. Version-Release number of selected component (if applicable): python3-docker-squash-1.0.5-4.fc26.noarch python3-docker-2.4.2-3.fc26.noarch Steps to Reproduce: 1. Install python3-docker from updates-testing 2. Run docker-squash Actual results: Traceback (most recent call last): File "/bin/docker-squash", line 6, in <module> from pkg_resources import load_entry_point File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3038, in <module> @_call_aside File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3022, in _call_aside f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3051, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 657, in _build_master ws.require(__requires__) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 971, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 857, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'docker-py>=1.7.2' distribution was not found and is required by docker-squash Expected results: No errors. Additional info: There is no new release on te upstream project but the "Add support for new docker-py, version 2" commit is already there https://github.com/goldmann/docker-squash/commit/5d706d04de176f570ff55427af3bb8dbf4af56a3
I'll take a look at releasing new version of docker-squash after my PTO (after 16th). Other option is for someone to backport this commit https://github.com/goldmann/docker-squash/commit/5d706d04de176f570ff55427af3bb8dbf4af56a3 and release updated package and this would be reverted once 1.0.6 would be released.
I can do that tomorrow, enjoy your time. I will need commit access for user robmv. PkgDB is already on read only mode. > How do I request commit access to a dist-git repo? > > Email the PACKAGENAME-owner alias asking to be given access, > or file a bugzilla bug on the package asking for access.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.