Am 05.12.2016 um 15:13 schrieb Piotr Ożarowski:
> [Malte Forkel, 2016-12-05]
>> Why do you recommend putting the requirements into Build-Depends? Most
>> of those packages are currently not available on the build system (I'm
>> not pbuilder for this).
>
> because you most probably need it for test
[Malte Forkel, 2016-12-05]
> Why do you recommend putting the requirements into Build-Depends? Most
> of those packages are currently not available on the build system (I'm
> not pbuilder for this).
because you most probably need it for tests anyway and if tests work
with version >= A, you don't n
Thanks for your help!
May be I should have mentioned that I'm packaging for internal use here.
So required package versions not available in the standard distribution
will be provided from a local repository.
Am 05.12.2016 um 13:28 schrieb Piotr Ożarowski:
> this looks like requirements.txt (i.e.
[Malte Forkel, 2016-12-05]
> The application requires Python 3.5, so I added to stdeb.cfg
>
> Depends: python3 (>= 3.5)
>
> The application also specifies the following requirements:
>
> requests>=2,<3
> pyyaml>=3.11,<4
> pytz>=2016.7
> pip>=7.0.0
> jinja2>=2.8
> voluptuous==0.9.2
Hi,
I'm trying to package an application with stdeb and pybuild but have
problems generating versioned dependencies in debian/control.
The application requires Python 3.5, so I added to stdeb.cfg
Depends: python3 (>= 3.5)
The application also specifies the following requirements:
requests>
5 matches
Mail list logo