all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tanguy LE CARROUR <tanguy@bioneland.org>
To: "Sébastien Lerique" <sl@eauchat.org>
Cc: 44401@debbugs.gnu.org
Subject: [bug#44401] [PATCH] gnu: poetry: Update to 1.1.4.
Date: Sun, 29 Nov 2020 18:45:39 +0100	[thread overview]
Message-ID: <1606671404.14slyqzte6.astroid@melmoth.none> (raw)
In-Reply-To: <20201102222624.3552-1-sl@eauchat.org>

Hi Sébastien,

Good to know that I'm not the only one with an interest in Poetry! :-)


> This submission was somwhat premature, as poetry 1.1.4 requires
> python-keyring 21.2.0, which in turn requires python-mypy for
> tests, which itself has failing tests on my machine. It seems I
> tried to bite too much in one go, so maybe this can be put on hold
> until I resolve the pending issues?

FYI, the upgrade to 1.1.4 is also discussed here:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=44077

It seems that there's also a problem with the latest version of keyring on Guix:
https://github.com/jaraco/keyring/issues/469
But I'm (slowly) working on it!

Happy hacking!

-- 
Tanguy




  parent reply	other threads:[~2020-11-29 17:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 22:26 [bug#44401] [PATCH] gnu: poetry: Update to 1.1.4 Sébastien Lerique
     [not found] ` <handler.44401.B.160435601427578.ack@debbugs.gnu.org>
2020-11-03  0:01   ` [bug#44401] Acknowledgement ([PATCH] gnu: poetry: Update to 1.1.4.) Sébastien Lerique
2020-11-29 17:45 ` Tanguy LE CARROUR [this message]
2020-11-30  9:45   ` [bug#44401] [PATCH] gnu: poetry: Update to 1.1.4 Sébastien Lerique
2020-11-30 10:08     ` Tanguy LE CARROUR
2020-11-30 10:29       ` Sébastien Lerique
2020-12-01 10:38         ` Tanguy LE CARROUR
2020-12-02  8:15           ` Tanguy LE CARROUR
2020-12-03 21:49             ` bug#44401: " Marius Bakke

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=1606671404.14slyqzte6.astroid@melmoth.none \
    --to=tanguy@bioneland.org \
    --cc=44401@debbugs.gnu.org \
    --cc=sl@eauchat.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 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.