Paul Wise writes:
> I guess my question wasn't clear enough. I was asking why
> pep8/python-pep8 are used at build time at all. They are tools for
> checking style, there is no reason to use them at build time at all.
Good question. However not my package, I am simply doing a NMU on a RC
bug for
On Mon, May 2, 2016 at 7:06 AM, Brian May wrote:
> The idea was to allow it to build unchanged on Jessie, which doesn't
> have python-pep8.
I guess my question wasn't clear enough. I was asking why
pep8/python-pep8 are used at build time at all. They are tools for
checking style, there is no reas
Paul Wise writes:
> On Sun, May 1, 2016 at 6:21 PM, Brian May wrote:
>
>> "python-pep8 | pep8" in the build depends
>
> Why is pep8 in a Build-Depends? It doesn't seem like something that
> should be used at build time, only at upstream development time.
The idea was to allow it to build unchang
On Sun, May 1, 2016 at 6:21 PM, Brian May wrote:
> "python-pep8 | pep8" in the build depends
Why is pep8 in a Build-Depends? It doesn't seem like something that
should be used at build time, only at upstream development time.
--
bye,
pabs
https://wiki.debian.org/PaulWise
On 2016-05-01 20:21:26, Brian May wrote:
> Hello,
>
> If I try to build a package on Jessie using sbuild that has
> "python-pep8 | pep8" in the build depends, it gives me the
> following error:
>
> --- cut ---
> Installing build dependencies
> Reading package lists...
> Building dependency tree..
[Brian May, 2016-05-01]
> If I try to build a package on Jessie using sbuild that has
> "python-pep8 | pep8" in the build depends, it gives me the
[...]
> Why isn't it falling back to installing pep8 when python-pep8 is not
> available? Isn't this the expected behaviour? Or have I got something
> w
6 matches
Mail list logo