GNU bug report logs - #69397
guix import crate misses dependencies

Previous Next

To reply to this bug, email your comments to 69397 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Nathan Dehnel <ncdehnel <at> gmail.com>
To: bug-guix <bug-guix <at> gnu.org>
Subject: guix import crate misses dependencies
Date: Sun, 25 Feb 2024 18:12:18 -0600

Run for example: guix import crate -r --recursive-dev-dependencies -
-allow-yanked egui_dock <at> 0.11
this will import a bunch of packages that require rust-bytemuck-1 as a
dependency, but it will not be included, and must be imported
separately.

guix 313458c

Message #8 received at 69397 <at> debbugs.gnu.org (full text, mbox):

From: Carlo Zancanaro <carlo <at> zancanaro.id.au>
To: Nathan Dehnel <ncdehnel <at> gmail.com>
Cc: 69397 <at> debbugs.gnu.org
Subject: Re: bug#69397: guix import crate misses dependencies
Date: Mon, 26 Feb 2024 11:46:01 +1100

Hi Nathan,

I just tried running your example:

On Sun, Feb 25 2024, Nathan Dehnel wrote:
> guix import crate -r --recursive-dev-dependencies --allow-yanked egui_dock <at> 0.11

I saw that rust-bytemuck-1 was included as an input in lots of packages,
as you said. However, I also noticed that bytemuck is present in
Guix. "guix edit rust-bytemuck" opened gnu/packages/crates-io.scm which
defines the rust-bytemuck-1 variable to a package for rust-bytemuck.

Rather than importing bytemuck separately, it should be enough to add
(use-modules (gnu packages crates-io)) at the top of your scheme file to
bring the Guix definition in.

Carlo

Message #11 received at 69397 <at> debbugs.gnu.org (full text, mbox):

From: Nathan Dehnel <ncdehnel <at> gmail.com>
To: Carlo Zancanaro <carlo <at> zancanaro.id.au>
Cc: 69397 <at> debbugs.gnu.org
Subject: Re: bug#69397: guix import crate misses dependencies
Date: Sun, 25 Feb 2024 20:21:19 -0600

Oh, my bad. Yeah, I just had my modules wrong. Thanks.

On Sun, Feb 25, 2024 at 6:46 PM Carlo Zancanaro <carlo <at> zancanaro.id.au> wrote:
>
> Hi Nathan,
>
> I just tried running your example:
>
> On Sun, Feb 25 2024, Nathan Dehnel wrote:
> > guix import crate -r --recursive-dev-dependencies --allow-yanked egui_dock <at> 0.11
>
> I saw that rust-bytemuck-1 was included as an input in lots of packages,
> as you said. However, I also noticed that bytemuck is present in
> Guix. "guix edit rust-bytemuck" opened gnu/packages/crates-io.scm which
> defines the rust-bytemuck-1 variable to a package for rust-bytemuck.
>
> Rather than importing bytemuck separately, it should be enough to add
> (use-modules (gnu packages crates-io)) at the top of your scheme file to
> bring the Guix definition in.
>
> Carlo

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.