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: Tue, 01 Dec 2020 11:38:15 +0100 [thread overview]
Message-ID: <1606818706.ve3c41z0my.astroid@melmoth.none> (raw)
In-Reply-To: <875z5np284.fsf@eauchat.org>
Hi Sébastien,
Excerpts from Sébastien Lerique's message of November 30, 2020 11:29 am:
>>> Once I have your latest patch I should probably be able to
>>> converge on what you have done. Here is my current patchset for
>>> reference: http://0x0.st/i7b_.diff , I'm working on
>>> 4a914de930a8317cab5bc11bdb608e3a3da3d1ad. I don't know whether
>>> to
>>> send parts of this as separate patches or not.
>>
>> Sounds like a plan! :-)
>>
>> Can I suggest that you wait for #44077 to be merged and then
>> submit your improvements?!
>
> Yes! I'll do that.
Just to let you know that it's been merged!
Quiet a few packages still have to be rebuilt, so it took some time for
me to install it, but… everything seems to work as expected!
So, you can proceed with submitting your patches and remove the `patch-setup-py`
from `poetry`.
Thanks!
--
Tanguy
next prev parent reply other threads:[~2020-12-01 10:51 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 ` [bug#44401] [PATCH] gnu: poetry: Update to 1.1.4 Tanguy LE CARROUR
2020-11-30 9:45 ` 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 [this message]
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
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=1606818706.ve3c41z0my.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 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).