Re: python-mkdocs new dependancy
[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, but we don't have > mkdocs-bootswatch in Debian? > > Just noticed, that same problem exists for mkdocs-bootstrap too. if you move themes to /usr/share/mkdocs/themes and patch /usr/bin/mkdocs to add this dir to sys.path (and there's no other entry point), even those themes that use pkg_requires will continue to work -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
Re: python-mkdocs new dependancy
[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: remember to git pull
On Apr 17, 2016, at 06:36 PM, Brian May wrote: >(or even better, use the quick-update script instead) quick-update script? Oh, and +1 for the recommendation! I'd just add to also be sure that you commit and push your changes. ;) I've had one or two cases where the repo doesn't match the archive. dgit -Barry
Re: remember to git pull
Barry Warsaw writes: > On Apr 17, 2016, at 06:36 PM, Brian May wrote: > >>(or even better, use the quick-update script instead) > > quick-update script? In the python-modules repository - it will also warn you if you have unpushed changes or dirty repositories. http://anonscm.debian.org/cgit/python-modules/tools/python-modules.git/tree/quick-update -- Brian May
