From: Oleg Pykhalov <go.wigust@gmail.com>
To: Tanguy Le Carrour <tanguy@bioneland.org>
Cc: 42573-done@debbugs.gnu.org
Subject: bug#42573: [PATCH 2/2] gnu: python-clikit: Update to 0.6.2.
Date: Thu, 30 Jul 2020 21:01:37 +0300 [thread overview]
Message-ID: <875za4lw5a.fsf@gmail.com> (raw)
In-Reply-To: <20200729072656.x3pa4s5iectwkhur@rafflesia> (Tanguy Le Carrour's message of "Wed, 29 Jul 2020 09:26:56 +0200")
[-- Attachment #1: Type: text/plain, Size: 813 bytes --]
Hi,
Tanguy Le Carrour <tanguy@bioneland.org> writes:
>>Could you take a look on a fetching source with ‘git-fetch’ and enabling
>>tests suite?
>
> Actually, I can't! :-(
>
> `crashtest` is a project managed with Poetry. In order to build and test it,
> I need `poetry`. But `poetry` depends on `clikit` that depends on… `crashtest`!
>
> I guess (I hope) that more and more projects will be managed with Poetry,
> so we'll run into this problem again.
>
> There's actually an other problem with Poetry: `poetry` is managed with Poetry!
> I have no idea how to handle this! Is this a scenario where we have to have
> a `poetry-0` that is a "trusted" binary that we use to "properly" build
> the "poetry chain"?
OK, thanks for investigation. I pushed the changes to master.
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2020-07-30 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 9:22 [bug#42573] [PATCH 0/2] gnu: python-clikit: Update to 0.6.2 Tanguy Le Carrour
2020-07-28 9:28 ` [bug#42573] [PATCH 1/2] gnu: Add python-crashtest Tanguy Le Carrour
2020-07-28 9:28 ` [bug#42573] [PATCH 2/2] gnu: python-clikit: Update to 0.6.2 Tanguy Le Carrour
2020-07-29 5:27 ` Oleg Pykhalov
2020-07-29 7:26 ` Tanguy Le Carrour
2020-07-30 18:01 ` Oleg Pykhalov [this message]
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=875za4lw5a.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=42573-done@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 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).