On 08. 06. 21 15:58, Tomas Hrnciar wrote:
Chances are, you already got an automated F35FailsToInstall bugzilla from Miro,
that your package fails to install. It would be really helpful if you could
find the missing dependency and mark the bugzilla for your package dependingon
the bugzilla for t
On Tue, Jun 15, 2021 at 5:35 AM Miro Hrončok wrote:
>
> On 14. 06. 21 7:31, Zbigniew Jędrzejewski-Szmek wrote:
> >> BuildRequires: %{py3_dist pytest}
> > Does it make sense to recommend py3_dist here? python3dist(pytest) is
> > not more complex but can be fed to 'dnf install' directly, so in the
>
On 14. 06. 21 7:31, Zbigniew Jędrzejewski-Szmek wrote:
BuildRequires: %{py3_dist pytest}
Does it make sense to recommend py3_dist here? python3dist(pytest) is
not more complex but can be fed to 'dnf install' directly, so in the
end it's more flexible. I always find the macro more obfuscation tha
On 14. 06. 21 7:31, Zbigniew Jędrzejewski-Szmek wrote:
For example, if a user runs pip install requests[security]
Please quote 'requests[security]' in the command. [] are special to the shell.
Done.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
__
On 14. 06. 21 2:23, Toshio Kuratomi wrote:
What do you/the packaging macros do when a pypi name is taken by two
different packages? (For instance, how setuptools and distribute used
the same name)
The PyPI names for those are "setuptools" and "distribute". These don't
conflict.
They do confl
On 14. 06. 21 7:57, Zbigniew Jędrzejewski-Szmek wrote:
What about making this conditional:
Requires: (pyproject-rpm-macros if rpm-build)
You can't really*use* the macros without rpmbuild, and one less
hard dependency is always good. With the conditional dep, pretty
much any real system will
