From: "Sébastien Lerique" <sl@eauchat.org>
To: Tanguy LE CARROUR <tanguy@bioneland.org>
Cc: 44401@debbugs.gnu.org
Subject: [bug#44401] [PATCH] gnu: poetry: Update to 1.1.4.
Date: Mon, 30 Nov 2020 11:29:15 +0100 [thread overview]
Message-ID: <875z5np284.fsf@eauchat.org> (raw)
In-Reply-To: <1606730475.mjds5el6sr.astroid@rafflesia.none>
Hi Tanguy,
>> So far I had to update:
>> - python-keyring to 21.5.0,
>> - python-setuptools to 50.3.2,
>> - python-virtualenv to 20.2.1,
>> - python-distlib to 0.3.1,
>> - python-tomlkit to 0.7.0,
>> - and use requests-toolbelt-0.9.1 in poetry's package
>> definition
>>
>> And I was now missing poetry-core, which I see you have done.
>> This
>> is turning into a large patchset, and on my side it's still
>> with
>> some tests disabled (though I'm still planning to activate
>> them).
>
> The main problem is `python-distlib`. So based on Marius'
> comment, I
> created a `python-distlib/next`.
>
> This is part of v5 here:
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=44077
>
Indeed, the /next solution was a good idea to keep moving. I
second your question on who/what makes sure that the /next package
is removed once python-distlib is upgraded (maybe simply add a
FIXME to python-distlib so whoever upgrades it is notified).
>>> 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!
>>
>> Yes, I found that simply adding python-setuptools (aside from
>> python-setuptools-scm) to the native-inputs made the
>> build-system
>> recognize the version.
>
> That's great!! You could add a comment with your solution to the
> issue,
> for the sake of documenting it.
>
Done :)
>> 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.
Sébastien
next prev parent reply other threads:[~2020-11-30 10:31 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 [this message]
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=875z5np284.fsf@eauchat.org \
--to=sl@eauchat.org \
--cc=44401@debbugs.gnu.org \
--cc=tanguy@bioneland.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.