all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tanguy Le Carrour <tanguy@bioneland.org>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 42573@debbugs.gnu.org
Subject: [bug#42573] [PATCH 2/2] gnu: python-clikit: Update to 0.6.2.
Date: Wed, 29 Jul 2020 09:26:56 +0200	[thread overview]
Message-ID: <20200729072656.x3pa4s5iectwkhur@rafflesia> (raw)
In-Reply-To: <20200728092221.9192-1-tanguy@bioneland.org>

Hi Oleg,

>Tanguy Le Carrour <tanguy <at> bioneland.org> writes:
>> * gnu/packages/python-xyz.scm (python-clikit): Update to 0.6.2.
>[…]
>> +    (arguments '(#:tests? #f))  ; no test in the PyPI tarball
>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"?

Any help welcome!

-- 
Tanguy




  parent reply	other threads:[~2020-07-29  7:28 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 [this message]
2020-07-30 18:01   ` bug#42573: " Oleg Pykhalov

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=20200729072656.x3pa4s5iectwkhur@rafflesia \
    --to=tanguy@bioneland.org \
    --cc=42573@debbugs.gnu.org \
    --cc=go.wigust@gmail.com \
    /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.