On Fri, May 25, 2018 at 07:41:23AM +1000, Brian May wrote:
> Alternatively, if you want, just upload a fixed package to unstable, and
> if all other requirements have been met it should be fine I think.
I don’t want to upload a version which uses so many bundled libraries…
We have both Bootstrap
Dmitry Shachnev writes:
> mkdocs uses mkdocs-bootswatch if this theme is specified in mkdocs.yml file.
>
> None of the Debian packages currently use this, but third-party software
> may use it, that’s why I added Breaks.
>
> It is not critical so I can remove this Breaks for my upload.
Alternati
On Thu, May 24, 2018 at 08:33:47AM +1000, Brian May wrote:
> > The fixed version won’t reach testing *first* because I have added
> > Breaks: mkdocs-bootswatch (<< 0.5) to it.
>
> What is the reason for this? Does mkdocs still try to use
> mkdocs-bootswatch if it is availabe?
mkdocs uses mkdocs-bo
Dmitry Shachnev writes:
> The fixed version won’t reach testing *first* because I have added
> Breaks: mkdocs-bootswatch (<< 0.5) to it.
What is the reason for this? Does mkdocs still try to use
mkdocs-bootswatch if it is availabe?
--
Brian May
On Thu, May 24, 2018 at 07:36:49AM +1000, Brian May wrote:
> I note the python-mkdocs package in sid still build-depends on both
> these packages. So probably should wait until a fixed package reaches
> testing first.
I am (still) working on it. I hope I will upload the new version tomorrow.
The
Dmitry Shachnev writes:
> Yes, this is no longer the case since mkdocs 0.16.0:
> https://github.com/mkdocs/mkdocs/commit/cc1c9a3adbcd8dde
>
> mkdocs-bootstrap is also no longer required, but it is used by two other
> packages in Debian so we have to keep it.
>
> Can you please file a removal bug
On Mon, May 21, 2018 at 07:35:29AM +1000, Brian May wrote:
> > One more question: why do we need mkdocs-bootswatch? It currently is not
> > used by anything in sid, and I would like to avoid doing useless work.
>
> Previously it was required by mkdocs. Are you saying this is no longer
> the case? I
Dmitry Shachnev writes:
> One more question: why do we need mkdocs-bootswatch? It currently is not
> used by anything in sid, and I would like to avoid doing useless work.
Previously it was required by mkdocs. Are you saying this is no longer
the case? If so, please remove it.
Thanks
--
Brian
Dmitry Shachnev writes:
> There are bundled copies of bootstrap-3.3.7.min.{js,css}.
>
> Bootstrap source is large so I don’t want to include it in missing-sources/.
> Instead I would just repack the tarball without all the bundled stuff.
>
> Will you mind if I do that? Also can I switch from git-
On Sun, May 20, 2018 at 09:08:45PM +1000, Brian May wrote:
> Please feel free to go ahead. The only reason I didn't make this part of
> the DPMT is I was told this package (and similarly) mkdocs-bootswatch
> aren't Python packages and as a result don't meet the requirements for
> DPMT.
One more qu
Hi Brian!
On Sun, May 20, 2018 at 09:08:45PM +1000, Brian May wrote:
> Please feel free to go ahead. The only reason I didn't make this part of
> the DPMT is I was told this package (and similarly) mkdocs-bootswatch
> aren't Python packages and as a result don't meet the requirements for
> DPMT.
>
Dmitry Shachnev writes:
> I have been working on updating mkdocs to the latest upstream version, 0.17.3
> (the updated packaging is in Git if you are interested).
>
> However I noticed that the version of mkdocs-bootstrap in archive does not
> support mkdocs 0.17. Please update to the new upstrea
Package: mkdocs-bootstrap
Version: 0.1.1-3
Dear maintainer,
I have been working on updating mkdocs to the latest upstream version, 0.17.3
(the updated packaging is in Git if you are interested).
However I noticed that the version of mkdocs-bootstrap in archive does not
support mkdocs 0.17. Pleas
13 matches
Mail list logo
