You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a project implements rpm-py-installer as a required dependency, then later tried to release the project as a RPM package, the project have to consider rpm-py-installer is not provided as a RPM package.
Maybe RPM spec file would consider that a required dependency package exists as a RPM package.
But I have no plan to provide rpm-py-installer as a RPM package.
When a project implements
rpm-py-installer
as a required dependency, then later tried to release the project as a RPM package, the project have to considerrpm-py-installer
is not provided as a RPM package.Maybe RPM spec file would consider that a required dependency package exists as a RPM package.
But I have no plan to provide
rpm-py-installer
as a RPM package.The solution that a python project of this case did is here to consider the status in
setup.py
.https://github.com/rebase-helper/rebase-helper/blob/master/setup.py
Here is a issue that
rpkg
faced.https://bugzilla.redhat.com/show_bug.cgi?id=1579367
And the possible solution.
https://pagure.io/rpkg/pull-request/319
I think I have to write this on README for people to know this issue in advance.
Providing best practices to fix it on README might be better.
ex.
rpm_spec_file_of_your_project.spec
or
The text was updated successfully, but these errors were encountered: