From: Cyril Roelandt <tipecaml@gmail.com>
To: guix-devel@gnu.org
Subject: [PATCH 0/3] Add python-bandit.
Date: Tue, 22 Sep 2015 00:31:12 +0200 [thread overview]
Message-ID: <1442874675-31473-1-git-send-email-tipecaml@gmail.com> (raw)
The first and third patches are probably easy to review. The second one is a bit
tricky. As explained in the comment, there is a circular dependency between
recent versions of python-pbr and python-fixtures, so I packaged older versions
of both python-pbr and python-fixtures to bootstrap the whole thing.
I did not use "inherit" because newer versions of these packages have become
quite different from the old versions, so it might just be clearer to write a
separate definition. Also, python-pbr-0.11 is defined in python.scm, next to
python-fixtures, which should be the only package that will ever need it (or so
I hope). Maybe it would be better to move it next to python-pbr, in
openstack.scm?
Finally, note that python-testrepository does not build well with the latest
version of python-fixtures, so we keep using python-fixtures-0.3.16 for now.
Cyril.
--
Cyril Roelandt (3):
gnu: Add python-pip.
gnu: Update python-fixtures
gnu: Add python-bandit.
gnu/packages/openstack.scm | 40 +++++++++++++++++
gnu/packages/python.scm | 107 ++++++++++++++++++++++++++++++++++++++++++++-
2 files changed, 145 insertions(+), 2 deletions(-)
--
2.1.4
next reply other threads:[~2015-09-21 22:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 22:31 Cyril Roelandt [this message]
2015-09-21 22:31 ` [PATCH 1/3] gnu: Add python-pip Cyril Roelandt
2015-09-22 14:30 ` Mathieu Lirzin
2015-09-21 22:31 ` [PATCH 2/3] gnu: Update python-fixtures Cyril Roelandt
2015-09-22 15:11 ` Mathieu Lirzin
2015-09-22 19:16 ` Thompson, David
2015-09-22 21:45 ` Cyril Roelandt
2015-09-27 20:17 ` Ludovic Courtès
2015-10-08 21:41 ` Cyril Roelandt
2015-10-09 12:18 ` Ludovic Courtès
2015-09-21 22:31 ` [PATCH 3/3] gnu: Add python-bandit Cyril Roelandt
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=1442874675-31473-1-git-send-email-tipecaml@gmail.com \
--to=tipecaml@gmail.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).