From: Leo Famulari <leo@famulari.name>
To: Adam Van Ymeren <adam@vany.ca>
Cc: 29415@debbugs.gnu.org
Subject: [bug#29415] [PATCH] gnu: python-axolotl: Update to 0.1.39 and fix build.
Date: Mon, 27 Nov 2017 13:09:59 -0500 [thread overview]
Message-ID: <20171127180959.GC20970@jasmine.lan> (raw)
In-Reply-To: <87vahvvkb2.fsf@vany.ca>
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
On Mon, Nov 27, 2017 at 10:00:01AM -0500, Adam Van Ymeren wrote:
> Leo Famulari <leo@famulari.name> writes:
> There is also a pull request pending from someone else that updates
> pyton-axolotl to use a newer python cryptography library rather than the
> deprecated python-pycrypto library. That would also fix this issue and
> is a much better long term fix but also a more intrusive change.
I noticed that as well. Pycrypto is no longer maintained and has an
extremely serious bug that was never fixed in a released version:
https://github.com/dlitz/pycrypto/issues/176
And the author seems to implicitly agree that people should stop using
it:
https://github.com/dlitz/pycrypto/issues/173
So I added a TODO comment to the package, saying that we should remove
it:
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/python-crypto.scm?id=12a130b0118c3f56e6337e011dc4a89f2671359a#n186
So, I recommend being careful how you use any package that depends on
pycrypto.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-11-27 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 20:04 [bug#29415] [PATCH] gnu: python-axolotl: Update to 0.1.39 and fix build Adam Van Ymeren
2017-11-25 0:09 ` Leo Famulari
2017-11-27 15:00 ` Adam Van Ymeren
2017-11-27 18:09 ` Leo Famulari [this message]
2017-11-27 18:10 ` Leo Famulari
2018-01-30 21:16 ` Ludovic Courtès
2018-01-31 14:38 ` Adam Van Ymeren
2018-01-31 16:37 ` bug#29415: " Ludovic Courtès
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=20171127180959.GC20970@jasmine.lan \
--to=leo@famulari.name \
--cc=29415@debbugs.gnu.org \
--cc=adam@vany.ca \
/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).