-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EPEL7 "Requires:" is sometime wrong #261
Comments
If I run
Can you provide more information about how to reproduce what you're seeing? |
The same command in my environment produces: The rpm Flask package provides:
in In setup.py:
pyp2rpm version is 3.3.5 |
3.3.5 isn't selecting the newest version due to a bug. Either use Could you attach the output and the log produced during that run? (/tmp/pyp2rpm-$user.log) |
I have upgraded to 3.3.6 and now the result still is:
|
uhm... I could suspect that |
I think this is addressed in the latest pyp2rpm. |
These should never be written as "python3-" dependencies. These should always be be written as "python%{python3_pkgversion}-" dependencies, for consistency and backwards compatibility. |
A trouble with EPEL7 is the requirement (
Requires:
) syntax.pyp2rpm uses syntax like
python3-<packagename>
, which is sometimes incorrect. For instance, many packages start with capital letter and EPEL7 downcases them (for instance see at package namedFlask
).I feel fine with
%{?python_enable_dependency_generator}
, it works well with el8. But it doesn't work with el7 (at least some versions of el7, even with latest rpm macros installed).%{?python_enable_dependency_generator}
add requirements in the following formpython3.6dist(flask)
which is EPEL7 compatible. Instead,
python3-Flask
orpython3dist(flask)
are not compatible with EPEL7.The text was updated successfully, but these errors were encountered: