Re: python-mkdocs new dependancy

2016-05-10 Thread Brian May
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 >

Re: python-mkdocs new dependancy

2016-05-10 Thread Piotr Ożarowski
[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:

Re: python-mkdocs new dependancy

2016-05-09 Thread Brian May
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:

Re: python-mkdocs new dependancy

2016-05-05 Thread Brian May
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/

Re: python-mkdocs new dependancy

2016-05-05 Thread Piotr Ożarowski
[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. > >

Re: python-mkdocs new dependancy

2016-05-02 Thread Brian May
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

Re: python-mkdocs new dependancy

2016-04-24 Thread Dmitry Shachnev
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

Re: python-mkdocs new dependancy

2016-04-23 Thread Brian May
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

Re: python-mkdocs new dependancy

2016-04-18 Thread Piotr Ożarowski
[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?

Re: python-mkdocs new dependancy

2016-04-18 Thread Piotr Ożarowski
[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,

Re: python-mkdocs new dependancy

2016-04-17 Thread Brian May
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