From: Danny Milosavljevic <dannym@scratchpost.org>
To: Hartmut Goebel <h.goebel@goebel-consult.de>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 3/5] gnu: Add python-sphinx-alabaster-theme-0.7.
Date: Fri, 7 Oct 2016 16:51:51 +0200 [thread overview]
Message-ID: <20161007165151.29d6218e@scratchpost.org> (raw)
In-Reply-To: <57F78082.3000407@goebel-consult.de>
Hi,
On Fri, 7 Oct 2016 13:01:22 +0200
Hartmut Goebel <h.goebel@goebel-consult.de> wrote:
> Am 07.10.2016 um 12:32 schrieb Danny Milosavljevic:
> > +(define-public python-sphinx-alabaster-theme-0.7
> Why do we need this exact version?
I don't know why - but we do, as you yourself wrote.
Hartmut Goebel wrote:
> These are required at run-time and thus need to be propagated-inputs:
>
> 'alabaster>=0.7,<0.8',
> > + (package
> > + (name "python-sphinx-alabaster-theme-0.7")
>
> The version number is *never* put into the name.
True, sorry.
next prev parent reply other threads:[~2016-10-07 14:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 10:32 [PATCH 0/5] Update Sphinx to 1.4.6 Danny Milosavljevic
2016-10-07 10:32 ` [PATCH 1/5] gnu: Add python-snowballstemmer Danny Milosavljevic
2016-10-07 10:32 ` [PATCH 2/5] gnu: Add python-sphinx-cloud-sptheme Danny Milosavljevic
2016-10-07 10:58 ` Hartmut Goebel
2016-10-07 13:28 ` Danny Milosavljevic
2016-10-07 13:48 ` Hartmut Goebel
2016-10-07 14:58 ` Danny Milosavljevic
2016-10-07 10:32 ` [PATCH 3/5] gnu: Add python-sphinx-alabaster-theme-0.7 Danny Milosavljevic
2016-10-07 11:01 ` Hartmut Goebel
2016-10-07 14:51 ` Danny Milosavljevic [this message]
2016-10-07 10:32 ` [PATCH 4/5] gnu: Add python-imagesize Danny Milosavljevic
2016-10-07 11:07 ` Hartmut Goebel
2016-10-07 10:32 ` [PATCH 5/5] gnu: Update Sphinx to 1.4.6 Danny Milosavljevic
2016-10-07 11:14 ` Hartmut Goebel
2016-10-07 11:16 ` [PATCH 0/5] " 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=20161007165151.29d6218e@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=h.goebel@goebel-consult.de \
/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.