Hi team,
I maintain a package, python-mirakuru[1], and the spec file uses
pyproject-rpm-macros.
With the latest release, 2.5.0, the project migrated[2] from using
requirements.txt files to use pipenv/Pipfile to declare dependencies.
I found that after bumping the version in the spec it fails dur
Hi Mikel.
The way upstream manages the dependencies of the project seems to be
weird to me. They use setuptools as a build backend and have runtime
dependencies in pyproject.toml but at the same time, they have Pipfile
and Pipfile.lock with runtime and test dependencies.
The best would be to
