Piotr Ożarowski writes:
> this one worked perfectly fine for me (tested with dh_python2 1.2014-2)
> so I assumed you pointed us to a wrong example
What do you mean by “worked perfectly”? Remember that the problem I'm
encountering is that the package builds successfully, but with
‘${python:De
[Ben Finney, 2016-10-17]
> I don't know why, but you snipped the sentence where I give an example:
Your mail suggested that there's a problem with dh-python in general and
not with one of your packages only...
> Ben Finney wrote:
>
> > How can I convince ‘dh-python’ to derive Debian package depe
Piotr Ożarowski writes:
> [Ben Finney, 2016-10-15]
> > How can I convince ‘dh-python’ to derive package dependencies from the
> > Setuptools ‘install_requires’ declaration?
>
> by dh-python you mean dh_python3, right?
In this case, ‘dh_python2’. Would you expect that to be different?
> > How ca
[Ben Finney, 2016-10-15]
> How can I convince ‘dh-python’ to derive package dependencies from the
> Setuptools ‘install_requires’ declaration?
by dh-python you mean dh_python3, right?
> The Pip requirements tend to be tightly restrictive, because Pip is not
> a distribution system but rather a de
Howdy all,
How can I convince ‘dh-python’ to derive package dependencies from the
Setuptools ‘install_requires’ declaration?
The Pip requirements tend to be tightly restrictive, because Pip is not
a distribution system but rather a deployment system. So those
requirements tend not to be good cand
5 matches
Mail list logo
