unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: guix-devel@gnu.org
Subject: [PATCH 2/5] gnu: python-numpydoc: Correct inputs.
Date: Fri,  2 Dec 2016 15:55:02 +0100	[thread overview]
Message-ID: <1480690505-21501-3-git-send-email-h.goebel@crazy-compilers.com> (raw)
In-Reply-To: <1480690505-21501-1-git-send-email-h.goebel@crazy-compilers.com>

This does what 213d1745c6adbfd274b1edc575529e026b0ab743 was
supposed to do.

* gnu/packages/python.scm (python-numpydoc, python-numpydoc)
Change first of the duplicate [native-inputs] definitions to
[propagated-inputs].
---
 gnu/packages/python.scm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
index ea94f44..24df71f 100644
--- a/gnu/packages/python.scm
+++ b/gnu/packages/python.scm
@@ -3390,7 +3390,7 @@ that client code uses to construct the grammar directly in Python code.")
            (substitute* "numpydoc/tests/test_plot_directive.py"
              (("3") "2"))))))
     (build-system python-build-system)
-    (native-inputs
+    (propagated-inputs
      `(("python-sphinx" ,python-sphinx)))
     (native-inputs
      `(("python-nose" ,python-nose)))
-- 
2.7.4

  parent reply	other threads:[~2016-12-02 14:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-02 14:55 [PATCH 0/5] Fixes for packages with new python build sytem Hartmut Goebel
2016-12-02 14:55 ` [PATCH 1/5] gnu: calibre: Do not use python setuptools for building Hartmut Goebel
2016-12-02 14:55 ` Hartmut Goebel [this message]
2016-12-02 14:55 ` [PATCH 3/5] gnu: python2-ipython: Fix inputs Hartmut Goebel
2016-12-02 14:55 ` [PATCH 4/5] gnu: python-numpy: " Hartmut Goebel
2016-12-02 14:55 ` [PATCH 5/5] gnu: dblatex: Update comment Hartmut Goebel
2016-12-02 15:45 ` [PATCH 0/5] Fixes for packages with new python build sytem Marius Bakke
2016-12-02 17:08   ` Hartmut Goebel

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=1480690505-21501-3-git-send-email-h.goebel@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@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).