From: ludo@gnu.org (Ludovic Courtès)
To: Ben Sturmfels <ben@sturm.com.au>
Cc: 26438-done@debbugs.gnu.org
Subject: bug#26438: [PATCH] Add fabric, python-paramiko: Update to 1.17.4.
Date: Tue, 11 Apr 2017 18:00:40 +0200 [thread overview]
Message-ID: <87o9w3q6hj.fsf@gnu.org> (raw)
In-Reply-To: <87a87nwzo9.fsf@sturm.com.au> (Ben Sturmfels's message of "Tue, 11 Apr 2017 10:33:42 +1000")
Hello,
Ben Sturmfels <ben@sturm.com.au> skribis:
> Couple of notes:
>
> 1. I found that I needed to upgrade python-paramiko to minimum 1.17.4 to
> avoid an incompatibility between python-paramiko and newer
> python-pycrypto. I'm not sure what the implications are of this.
> Technically only the Python 2 version needs to be upgraded, since Fabric
> is Python 2 only, but I've upgraded both for consistency.
Sounds good.
> 2. I've disabled tests for now as they fail when the package attempts to
> download the "test-require" dependency "fudge". What's the normal way to
> stop the Python package doing it's own dependency downloading? Happy to
> also package "python2-fudge", but that didn't fix the downloading issue.
I would expect that adding python2-fudge would indeed fix the problem
(the setuptools machinery checks for already-available packages and only
tries to download as a last resort.) Would need more investigation I
guess!
>>From 521b29606ca4e1a34c9db89fbc22201eea581370 Mon Sep 17 00:00:00 2001
> From: Ben Sturmfels <ben@sturm.com.au>
> Date: Tue, 11 Apr 2017 00:06:20 +1000
> Subject: [PATCH] gnu: Add fabric, python-paramiko: Update to 1.17.4.
>
> * gnu/packages/python.scm (python-paramiko): Update to 1.17.4.
> * gnu/packages/admin.scm (fabric): New variable.
I’ve split it into two commits and applied.
Thank you, and welcome!
Ludo’.
prev parent reply other threads:[~2017-04-11 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 0:33 bug#26438: [PATCH] Add fabric, python-paramiko: Update to 1.17.4 Ben Sturmfels
2017-04-11 16:00 ` Ludovic Courtès [this message]
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=87o9w3q6hj.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=26438-done@debbugs.gnu.org \
--cc=ben@sturm.com.au \
/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).