unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Blake Shaw <blake@nonconstructivism.com>
Cc: 51415@debbugs.gnu.org
Subject: [bug#51415] [PATCH] In the Artanis package the propagated input of guile-json is conflicting with guix, and no series of guix upgrades or guix installs seems to fix this. Therefore, I moved guile-json from a propagated input to an input, which solves the issue, but may not be ideal for people who don't wish to keep multiple copies of guile-json
Date: Tue, 26 Oct 2021 13:46:35 -0400	[thread overview]
Message-ID: <YXg++2hgOfTHsSxG@jasmine.lan> (raw)
In-Reply-To: <20211026124602.28283-1-blake@nonconstructivism.com>

On Tue, Oct 26, 2021 at 07:46:02PM +0700, Blake Shaw via Guix-patches via wrote:
> In the Artanis package the propagated input of guile-json is
> conflicting with guix, and no series of guix upgrades or guix installs
> seems to fix this. Therefore, I moved guile-json from a propagated
> input to an input, which solves the issue, but may not be ideal for
> people who don't wish to keep multiple copies of guile-json

Thanks for the report... can you share the warnings or error messages
that you are seeing?

It's likely that guile-json is propagated for a good reason, and that
not propagating it would cause problems for artanis users. Maybe there
is another way to solve the problem that you're experiencing.




  reply	other threads:[~2021-10-26 17:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 12:46 [bug#51415] [PATCH] In the Artanis package the propagated input of guile-json is conflicting with guix, and no series of guix upgrades or guix installs seems to fix this. Therefore, I moved guile-json from a propagated input to an input, which solves the issue, but may not be ideal for people who don't wish to keep multiple copies of guile-json Blake Shaw via Guix-patches via
2021-10-26 17:46 ` Leo Famulari [this message]
2021-11-08 21:08   ` Ludovic Courtès
2023-01-03 22:34     ` Maxim Cournoyer

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=YXg++2hgOfTHsSxG@jasmine.lan \
    --to=leo@famulari.name \
    --cc=51415@debbugs.gnu.org \
    --cc=blake@nonconstructivism.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 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).