all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Winter via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: 61885@debbugs.gnu.org
Subject: bug#61885: `guix import go` fails outside of pre-inst-env
Date: Wed, 1 Mar 2023 12:52:51 -0500	[thread overview]
Message-ID: <D601594D-B966-4066-8021-4F0E87E845C4@winter.cafe> (raw)
In-Reply-To: <875ybkolb8.fsf@jpoiret.xyz>

> Using (gnu packages check) then (gnu packages golang) doesn't make the
> error appear.  The solution imo, esp. since (gnu packages check) already
> uses (gnu packages golang), is to have the variant package defined
> alongside the parent. Here is a patch that should fix this.

To clarify: I do think this is the best solution, though the oddities I mentioned may warrant further investigation into potentially different issues.

In addition to those, I wonder why `guix build` shows that the cyclic package can't be found, rather than throwing an error as `guix import` does. Maybe it's worth fixing that, if possible, to not cause (worse) confusion?

Thanks,
Winter



  parent reply	other threads:[~2023-03-01 17:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01  3:42 bug#61885: `guix import go` fails outside of pre-inst-env winter--- via Bug reports for GNU Guix
2023-03-01  9:47 ` Josselin Poiret via Bug reports for GNU Guix
2023-03-01  9:48   ` bug#61885: [PATCH] gnu: go-github-com-robfig-cron-1.2: Move to (gnu packages golang) Josselin Poiret via Bug reports for GNU Guix
2023-03-01 10:40     ` Simon Tournier
2023-03-02 22:31       ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2023-03-01 17:34   ` bug#61885: `guix import go` fails outside of pre-inst-env Winter via Bug reports for GNU Guix
2023-03-01 17:52   ` Winter via Bug reports for GNU Guix [this message]
2023-03-01 21:04     ` Josselin Poiret via Bug reports for GNU Guix

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=D601594D-B966-4066-8021-4F0E87E845C4@winter.cafe \
    --to=bug-guix@gnu.org \
    --cc=61885@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=winter@winter.cafe \
    /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.