all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>, guix-devel@gnu.org
Subject: Re: [PATCH 0/5] Fixes for packages with new python build sytem
Date: Fri, 02 Dec 2016 16:45:51 +0100	[thread overview]
Message-ID: <87bmwucp1s.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <1480690505-21501-1-git-send-email-h.goebel@crazy-compilers.com>

[-- Attachment #1: Type: text/plain, Size: 576 bytes --]

Hartmut Goebel <h.goebel@crazy-compilers.com> writes:

> This patches fixes some build issues caused by using the new python build
> system.
>
> Hartmut Goebel (5):
>   gnu: calibre: Do not use python setuptools for building.
>   gnu: python-numpydoc: Correct inputs.
>   gnu: python2-ipython: Fix inputs.
>   gnu: python-numpy: Fix inputs.
>   gnu: dblatex: Update comment.
>
>  gnu/packages/docbook.scm | 10 +++++++---
>  gnu/packages/ebook.scm   |  3 +++
>  gnu/packages/python.scm  |  9 +++++----
>  3 files changed, 15 insertions(+), 7 deletions(-)

Thanks! These LGTM.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2016-12-02 15:45 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 ` [PATCH 2/5] gnu: python-numpydoc: Correct inputs Hartmut Goebel
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 ` Marius Bakke [this message]
2016-12-02 17:08   ` [PATCH 0/5] Fixes for packages with new python build sytem 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

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

  git send-email \
    --in-reply-to=87bmwucp1s.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mbakke@fastmail.com \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.