unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Adam Van Ymeren <adam@vany.ca>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 29415@debbugs.gnu.org
Subject: [bug#29415] [PATCH] gnu: python-axolotl: Update to 0.1.39 and fix build.
Date: Wed, 31 Jan 2018 09:38:14 -0500	[thread overview]
Message-ID: <87y3keccvd.fsf@vany.ca> (raw)
In-Reply-To: <877erzvyh4.fsf@gnu.org>

Ludovic Courtès <ludo@gnu.org> writes:

> Hi Adam,
>
> Adam Van Ymeren <adam@vany.ca> skribis:
>
>> Leo Famulari <leo@famulari.name> writes:
>>> I think this change should be submitted upstream, which is here:
>>>
>>> https://github.com/tgalal/python-axolotl
>>>
>>> Can you do that? We wouldn't have to wait for a new release of
>>> python-axolotl, but we should wait to hear what the upstream maintainer
>>> thinks.
>>
>> Pull request sent.
>>
>> 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.
>
> Any update on this?  :-)

Haven't heard anything from the maintainer :/.

We could just go ahead and apply my patch anways :).  Or remove the
package from guix entirely.  As it stands the package has been broken
for over a year in guix.

https://hydra.gnu.org/job/gnu/master/python-axolotl-0.1.35.x86_64-linux

>
> Thanks in advance,
> Ludo’.

  reply	other threads:[~2018-01-31 14:39 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
2017-11-27 18:10     ` Leo Famulari
2018-01-30 21:16     ` Ludovic Courtès
2018-01-31 14:38       ` Adam Van Ymeren [this message]
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=87y3keccvd.fsf@vany.ca \
    --to=adam@vany.ca \
    --cc=29415@debbugs.gnu.org \
    --cc=ludo@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).