Hi Salvo!
Can you please file this request as a Debian bug?
I am planning to update the package with Ahmed, and we can look into
patching the external asset loading, and I can teach Ahmed how to close
bugs via changelog etc
Thanks!
if I'm generating html and
> publishing it using mkdocs.
That's something for the upstream to change.
--
WBR, wRAR
signature.asc
Description: PGP signature
Hi Salvo!
On Sun, Jul 14, 2024 at 12:19:43AM +0200, Salvo Tomaselli wrote:
> Sorry for the OT, but should we consider patching mkdocs themes to stop
> linking to external websites (mostly cloudflare) for static assets?
dh_mkdocs supports replacing highlight.js from cloudflare with the pa
On Sun, Jul 14, 2024 at 12:19:43AM +0200, Salvo Tomaselli wrote:
> Sorry for the OT, but should we consider patching mkdocs themes to stop
> linking to external websites (mostly cloudflare) for static assets?
>
> This has been used to create security vulnerabilities recently
>On 13 July 2024 10:19:43 pm UTC, Salvo Tomaselli wrote:
>>Sorry for the OT, but should we consider patching mkdocs themes to stop
>>linking to external websites (mostly cloudflare) for static assets?
>>
>>This has been used to create security vulnerabilities recently (see for the
>>polyfill situation).
>>
patching mkdocs themes to stop
>linking to external websites (mostly cloudflare) for static assets?
>
>This has been used to create security vulnerabilities recently (see for the
>polyfill situation).
>
Otto Kekäläinen writes:
> Are you OK that I upload a new python-mkdocs version together with
> Ahmed (CCd)?
Fine with me, I haven't had a lot of time for Debian lately.
--
Brian May @ Debian
Hello Otto,
Am 13.07.24 um 18:40 schrieb Otto Kekäläinen:
Hi Brian, Nick and Carsten!
Are you OK that I upload a new python-mkdocs version together with Ahmed (CCd)?
Asking to avoid duplicate work with you who are marked as
maintainer/uploader/recent committed.
We will do the work at
https
Hi Brian, Nick and Carsten!
Are you OK that I upload a new python-mkdocs version together with Ahmed (CCd)?
Asking to avoid duplicate work with you who are marked as
maintainer/uploader/recent committed.
We will do the work at
https://salsa.debian.org/python-team/packages/python-mkdocs
Hello,
I am thinking now (with the migration to Salsa) is a good time to move
all the packages directly related to mkdocs to PAPT:
mkdocs-bootstrap - bootstrap themes for MkDocs
mkdocs-bootswatch - bootswatch themes for MkDocs
mkdocs - Static site generator geared towards building project
Thanks Ghislain and Simon for your responses.
It turns out mkdocs need python-markdown not for tests, but rather for
building its own docs.
So probably the correct way to go is to make sure both packages take the
nodoc build profile into account.
On Thu, Jan 11, 2018 at 11:29:34AM +, Simon
On Thu, 11 Jan 2018 at 13:35:13 +0300, Dmitry Shachnev wrote:
> The new release of python-markdown has switched docs building from its own
> custom build system to mkdocs. However python-mkdocs itself build-depends on
> python3-markdown for tests, which results in a circular build-depend
2018-01-11 10:35 GMT+00:00 Dmitry Shachnev :
> Hi Brian and list,
>
> The new release of python-markdown has switched docs building from its own
> custom build system to mkdocs. However python-mkdocs itself build-depends on
> python3-markdown for tests, which results in a circular b
Hi Brian and list,
The new release of python-markdown has switched docs building from its own
custom build system to mkdocs. However python-mkdocs itself build-depends on
python3-markdown for tests, which results in a circular build-dependency.
Will it be fine if I just mark the build-dependency
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
>
[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 war
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
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
.
> >
> > And then patch mkdocs to add /usr/share/mkdocs/themes to sys.path like
> > Piotr suggested.
>
> I have a test version of the packages available:
>
> https://linuxpenguins.xyz/debian/pool/main/m/mkdocs-bootstrap/
* please use --install-lib instead of moving
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/shar
[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 re
> 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
&
[Brian May, 2016-04-30]
> This is a requirement for python-mkdocs.
>
> Not sure if this prefix of python- is appropriate or not because this
> package doesn't contain any python, however it is part mkdocs, and the
> source of mkdocs which has been named python-mkdocs in Debia
Package: wnpp
Severity: wishlist
Owner: Brian May
* Package name: python-mkdocs-bootstrap
Version : 0.1.1
Upstream Author : Dougal Matthews
* URL : https://pypi.python.org/pypi/mkdocs-bootstrap/
* License : BSD
Programming Lang: HTML/CSS
Description
Package: wnpp
Severity: wishlist
Owner: Brian May
* Package name: python-mkdocs-bootswatch
Version : 0.4.0
Upstream Author : Dougal Matthews
* URL : https://pypi.python.org/pypi/mkdocs-bootswatch/
* License : BSD
Programming Lang: HTML/CSS
Description
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.
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
[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-bo
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 re
[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__ imp
On Mon, Jan 25, 2016 at 23:13:49 -0500, Barry Warsaw wrote:
> On Jan 26, 2016, at 01:12 AM, Ben Hutchings wrote:
>
> >That's not the problem at all. Read the error message again. Read the
> >source line it points to. Now look at where rv comes from:
> >
> import subprocess
> rv = sub
On Mon, Jan 25, 2016 at 8:12 PM, Ben Hutchings wrote:
> On Tue, 2016-01-26 at 11:49 +1100, Brian May wrote:
import subprocess
rv = subprocess.Popen(['locale', '-a'], stdout=subprocess.PIPE,
> ... stderr=subprocess.PIPE).communicate()[0]
type(rv)
>
>
> This is
On Jan 26, 2016, at 01:12 AM, Ben Hutchings wrote:
>That's not the problem at all. Read the error message again. Read the
>source line it points to. Now look at where rv comes from:
>
import subprocess
rv = subprocess.Popen(['locale', '-a'], stdout=subprocess.PIPE,
>...
On Tue, Jan 26, 2016 at 1:23:19 +, Ben Hutchings wrote:
> On Tue, 2016-01-26 at 12:16 +1100, Brian May wrote:
> > Ben Hutchings writes:
> >
> > > That's not the problem at all. Read the error message again. Read the
> > > source line it points to. Now look at where rv comes from:
> >
> >
Ben Hutchings writes:
> Oh, well that's probably because you only set LANG and it's being
> overridden by LC_ALL. Use a bigger hammer: set LC_ALL yourself.
Yes, somebody mentioned this on the BTS also. I very much suspect this
will be the solution.
Thanks
--
Brian May
On Tue, 2016-01-26 at 12:16 +1100, Brian May wrote:
> Ben Hutchings writes:
>
> > That's not the problem at all. Read the error message again. Read the
> > source line it points to. Now look at where rv comes from:
>
> Yes, that is how it would appear.
>
> However, all this code does is try
Ben Hutchings writes:
> That's not the problem at all. Read the error message again. Read the
> source line it points to. Now look at where rv comes from:
Yes, that is how it would appear.
However, all this code does is try to work out the appropriate fatal
error message that should get disp
On Tue, 2016-01-26 at 11:49 +1100, Brian May wrote:
> Ben Hutchings writes:
>
> > C.UTF-8 is built into glibc so I believe you can assume it's present in
> > all Debian installations (from wheezy onward).
>
> Ok, this is getting more and more complicated. The only reason I can see
> for the FTBF
Ben Hutchings writes:
> C.UTF-8 is built into glibc so I believe you can assume it's present in
> all Debian installations (from wheezy onward).
Ok, this is getting more and more complicated. The only reason I can see
for the FTBFS in #812672 is because the C.UTF-8 locale doesn't exist. It
shoul
On Tue, 2016-01-26 at 11:29 +1100, Brian May wrote:
[...]
> The problem is that when building djangorestframework, I need to have a
> utf8 locale available. C.UTF-8 is fine. However, I don't think there is
> any guarantee (??) that a utf8 locale will be available when building
> packages. This I be
On 14 February 2015 at 09:52, Brian May wrote:
> What should I call the package? mkdocs? Or python3-mkdocs?
>
Thinking about this, I will call the source python-mkdocs, but the binary
package just mkdocs.
As I think the names python-mkdocs and python3-mkdocs imply some sort of
publ
epends, what fun :-)
> Looks like upstream really does not provide any stable Python API,
> so I think there is no need to build public module packages.
>
What should I call the package? mkdocs? Or python3-mkdocs?
> But you will make me a bit happier if you make the executable use
Hi Brian,
On Fri, 13 Feb 2015 10:06:25 +1100, Brian May wrote:
> MkDocs is a fast, simple and downright gorgeous static site generator
> that's geared towards building project documentation. Documentation
> source files are written in Markdown, and configured with a single YAML
&
Package: wnpp
Severity: wishlist
Owner: Brian May
* Package name: python-mkdocs
Version : 0.11.1
Upstream Author : Tom Christie
* URL : http://www.mkdocs.org/
* License : BSD
Programming Lang: Python
Description : Static site generator geared towards
45 matches
Mail list logo
