unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: phodina <phodina@protonmail.com>, help-guix <help-guix@gnu.org>
Cc: "mbakke@fastmail.com" <mbakke@fastmail.com>
Subject: Re: Circular dependency python-oslo.i18n
Date: Wed, 04 Aug 2021 07:01:52 -0400	[thread overview]
Message-ID: <9BFAE48A-4F71-403B-9023-39F020A59943@lepiller.eu> (raw)
In-Reply-To: <_xaftDTU1p5ygbvk2J_qp3ZdFjEOIWR0HrJwJW8oe2fyfgZvaTFwYtH45oG5_X0z8KgP6Ri5OpLfeHxS0S-NgrL3YOmr5WaSAvZP-KOnhzw=@protonmail.com>

In these cases I think we usually disable the tests and leave a comment explaining the situation.

Le 4 août 2021 03:56:25 GMT-04:00, phodina <phodina@protonmail.com> a écrit :
>Greeting,
>I have a question regarding circular dependency and a package that won't build.
>
>I wanted to send a patch with updated version of pkg python-websocket-client. However, as I ran =./pre-inst-env guix refresh --list-dependent python-websocket-client= I noticed that one of the pkgs depending on this one failed to build.
>
>The reason was that pkg python-oslo.i18n failed to build - pass check phase.
>
>In the native-inputs it misses python-bandit, python-reno and python-oslo.i18n. However, then I get the issue with too many heap allocations.
>
>Digging deeper, I see that python-oslo.config depends on python-oslo.i18n.
>
>Any recommendation on how to solve this conundrum would be appreciated!
>
>guix:
>      repository URL: https://git.savannah.gnu.org/git/guix.git
>      branch: master
>      commit: b95fb85f593d377864fc1bfb3c118e54d03783be
>
>Kind regards
>

      reply	other threads:[~2021-08-04 11:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04  7:56 Circular dependency python-oslo.i18n phodina
2021-08-04 11:01 ` Julien Lepiller [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=9BFAE48A-4F71-403B-9023-39F020A59943@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=help-guix@gnu.org \
    --cc=mbakke@fastmail.com \
    --cc=phodina@protonmail.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.
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).