unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Mathieu Lirzin <mthl@gnu.org>
Cc: 34204@debbugs.gnu.org
Subject: [bug#34204] [PATCH 3/3] gnu: Add Mkdocs.
Date: Sat, 26 Jan 2019 14:37:37 +0100	[thread overview]
Message-ID: <874l9vv8ta.fsf@elephly.net> (raw)
In-Reply-To: <20190126002849.7707-3-mthl@gnu.org>


Hi Mathieu,

> * gnu/packages/documentation.scm (mkdocs): New variable.
[…]
> +
> +(define-public mkdocs
> +  (package
> +    (name "mkdocs")
> +    (version "1.0.4")
> +    (source
> +     (origin
> +       (method url-fetch)
> +       (uri (pypi-uri "mkdocs" version))
> +       (sha256
> +        (base32
> +         "0fg9w6rdskwnn7knri7xzrd26k9svwqlxvdr0kk5spfpm8ll7lqp"))))
> +    (build-system python-build-system)
> +    (arguments
> +     ;; XXX: Tests are failing.
> +     ;; AttributeError: module 'mkdocs.plugins' has no attribute 'get_plugins'
> +     '(#:tests? #f))

Hmm, any idea why this happens?  Are the plugins not included?  Is there
an upstream bug report about this?

Other than that it looks good to me.

-- 
Ricardo

  reply	other threads:[~2019-01-26 13:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-26  0:25 [bug#34204] [PATCH 0/3] Mkdocs and its dependencies Mathieu Lirzin
2019-01-26  0:28 ` [bug#34204] [PATCH 1/3] gnu: python-tornado: Update to 5.1.1 Mathieu Lirzin
2019-01-26  0:28   ` [bug#34204] [PATCH 2/3] gnu: Add Python LiveReload Mathieu Lirzin
2019-01-26 13:35     ` Ricardo Wurmus
2019-01-26  0:28   ` [bug#34204] [PATCH 3/3] gnu: Add Mkdocs Mathieu Lirzin
2019-01-26 13:37     ` Ricardo Wurmus [this message]
2019-01-26 15:24       ` Mathieu Lirzin
2019-01-26 13:34   ` [bug#34204] [PATCH 1/3] gnu: python-tornado: Update to 5.1.1 Ricardo Wurmus
2019-01-26 14:29     ` Mathieu Lirzin
2021-07-13 13:39 ` bug#34204: [PATCH 0/3] Mkdocs and its dependencies Maxim Cournoyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874l9vv8ta.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=34204@debbugs.gnu.org \
    --cc=mthl@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).