Bug 1436118 - Missing egg-info for python-enchant on F24
Summary: Missing egg-info for python-enchant on F24
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-enchant
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Charalampos Stratakis
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-27 08:32 UTC by Viliam Križan
Modified: 2017-04-04 20:50 UTC (History)
2 users (show)

Fixed In Version: python-enchant-1.6.8-1.fc24
Clone Of:
Environment:
Last Closed: 2017-04-04 20:50:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Viliam Križan 2017-03-27 08:32:55 UTC
Description of problem:

python-enchant package on Fedora 24 is missing egg-info. An application that would require "pyenchant", written in `install_requires`, and has entry points would raise an error on start:

pkg_resources.DistributionNotFound: The 'pyenchant' distribution was not found and is required by APPLICATION


How reproducible:
Build python package with entry points, with `install_requires=['pyenchant']`, and RPM with `Requires: python3-enchant`.

Comment 1 Charalampos Stratakis 2017-03-27 09:34:47 UTC
It seems that in the SPEC, the egg-info is removed during the %install which is not the case for later branches. Will fix it.

Comment 2 Fedora Update System 2017-03-28 01:49:47 UTC
python-enchant-1.6.8-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-a893e322ab

Comment 3 Fedora Update System 2017-04-04 20:50:33 UTC
python-enchant-1.6.8-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.