Hi,
On Thu, 18 Jun 2020, Raphael Hertzog wrote:
> Actually your fix does not work because pkg_resources is not documented in
> setup.py or requirements.txt and thus it will not magically appear in
> ${python3:Depends} just by adding it in Build-Depends.
>
> I opened https://github.com/SecureAuthCorp/impacket/issues/885 upstream to
> get this fixed but in the meantime we have to hardcode the dependency in
> Depends. I'll do that for now.
Actually, I'm not sure that anything needs to happen at the upstream
level... pkg_resources is part of setuptools, we have packaged it
separately but I believe that there's no way for us to track its usage
based on upstream dependencies so we must always manually add such a
depency (this really smells like a big deficiency in our packaging tools).
Am I correct?
Should upstream list setuptools in their requirements.txt or setup.py
because they use "pkg_resources"?
Cheers,
--
⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog <hert...@debian.org>
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋ The Debian Handbook: https://debian-handbook.info/get/
⠈⠳⣄⠀⠀⠀⠀ Debian Long Term Support: https://deb.li/LTS
_______________________________________________
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
