> please don't use python- prefix, use mkdocs-bootswatch. Note that binary
> package is "mkdocs"
Ok, so I just call both source *and* binary packages mkdocs-bootswatch
and mkdocs-bootstrap then?
>> I plan to maintain this as part of the DPMT - Debian Python Modules
>> Team.
>
> I think PAPT is m
[Brian May, 2016-05-01]
> > please don't use python- prefix, use mkdocs-bootswatch. Note that binary
> > package is "mkdocs"
>
> Ok, so I just call both source *and* binary packages mkdocs-bootswatch
> and mkdocs-bootstrap then?
yes please
> mkdocs was required for a DPMT package - django-rest-f
[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
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..
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
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 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:
> 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
Dmitry Shachnev writes:
> Your plan LGTM, though I would still use setup.py to install the themes
> (with passing appropriate --install-lib), to make sure that the egg-info
> directory (with entry points declarations) is still installed.
>
> And then patch mkdocs to add /usr/share/mkdocs/themes t
9 matches
Mail list logo
