Piotr Ożarowski writes:
> dh_python* is checking usr/share/mkdocs-bootstrap by default (among
> other dirs). If you want it to check usr/share/mkdocs as well, you have
> to point it to, f.e. like this:
>
> override_dh_python3:
> dh_python3 -N mkdocs-bootstrap
> dh_python3 -p mkdocs-bo
[Brian May, 2016-05-10]
> Brian May writes:
>
> >> export PYBUILD_INSTALL_ARGS=--install-lib=/usr/share/mkdocs/themes/
> >
> > Was hoping to avoid the need to add /usr/share/mkdocs/themes to the
> > sys.path.
>
> This results in the following lintian warning:
>
> E: mkdocs-bootstrap: package-
Brian May writes:
>> export PYBUILD_INSTALL_ARGS=--install-lib=/usr/share/mkdocs/themes/
>
> Was hoping to avoid the need to add /usr/share/mkdocs/themes to the
> sys.path.
This results in the following lintian warning:
E: mkdocs-bootstrap: package-installs-python-pycache-dir
usr/share/mkdoc
Piotr Ożarowski writes:
> * please use --install-lib instead of moving files after dh_python3.
> Moving files once dh_python{2,3} creates hooks to bytecompile py files
> is not really a good idea.
>
> export PYBUILD_INSTALL_ARGS=--install-lib=/usr/share/mkdocs/themes/
Was hoping to avoid t
[Brian May, 2016-05-02]
> 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 mk
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
Hi Brian,
On Sat, Apr 23, 2016 at 06:16:19PM +1000, Brian May wrote:
> So I think it is probably a good idea to have three seperate Debian
> source packages and three seperate binary packages.
>
> It looks like both mkdocs-bootswatch and mkdocs-bootstrap contain
> non-Python code.
>
> So instead o
Piotr Ożarowski writes:
> [Brian May, 2016-04-18]
>> Sorry, I don't quite understand. How will this help with the fact that
>> mkdocs-bootswatch is listed as a requirement, but we don't have
>> mkdocs-bootswatch in Debian?
>
> FTR: using not packaged version of mkdocs-bootswatch is not an option,
[Brian May, 2016-04-18]
> Sorry, I don't quite understand. How will this help with the fact that
> mkdocs-bootswatch is listed as a requirement, but we don't have
> mkdocs-bootswatch in Debian?
FTR: using not packaged version of mkdocs-bootswatch is not an option,
but that's obvious, right?
[Brian May, 2016-04-18]
> >> What is the appropriate fix? Should I create a new mkdocs-bootswatch
> >
> > I moved all themes to /usr/share in python-pastescript and it works
>
> Sorry, I don't quite understand. How will this help with the fact that
> mkdocs-bootswatch is listed as a requirement, b
Piotr Ożarowski writes:
>> What is the appropriate fix? Should I create a new mkdocs-bootswatch
>
> I moved all themes to /usr/share in python-pastescript and it works
Sorry, I don't quite understand. How will this help with the fact that
mkdocs-bootswatch is listed as a requirement, but we don'
[Brian May, 2016-04-12]
> When building python-mkdocs from git source I get this error:
>
> LANG=C.UTF-8 PYTHONPATH=. ./debian/scripts/mkdocs build
> Traceback (most recent call last):
> File "./debian/scripts/mkdocs", line 7, in
> from mkdocs.__main__ import cli
> File "/<>/mkdocs/__main
12 matches
Mail list logo
