GNU bug report logs - #38907
Recursive crates importer does not respect dependencies versions

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 38907 in the body.
You can then email your comments to 38907 AT debbugs.gnu.org in the normal way.

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

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

From: Valentin Ignatev <valentignatev <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: Recursive crates importer does not respect dependencies versions
Date: Sat, 4 Jan 2020 01:23:57 +0300

[Message part 1 (text/plain, inline)]

Hey Guix! I'm trying to import notify 4.0.14 with guix import crate
notify <at> 4.0.14 --recursive and it completes without an error, but it
doesn't seem to pick correct versions for dependencies.

For example, notify v4.0.14 deends on fsevent ^0.4, but the crates
importer generates a definition for fsevent v2.0.1. Attached file is
the result of guix import crate notify <at> 4.0.14 --recursive command

Best regards,
Valentin

[notify.scm (text/x-scheme, attachment)]

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

From: Valentin Ignatev <valentignatev <at> gmail.com>
To: 38907 <at> debbugs.gnu.org
Subject: Recursive crates importer does not respect dependencies versions
Date: Sat, 4 Jan 2020 01:33:48 +0300

Ah, on the second thought this might be solved upcoming semantic
verison importer from https://issues.guix.gnu.org/issue/38408, so
maybe this is a duplicate.

Valentin

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

From: Brendan Tildesley <btild <at> mailbox.org>
To: "38907 <at> debbugs.gnu.org" <38907 <at> debbugs.gnu.org>
Subject: close?
Date: Sun, 21 Mar 2021 12:09:36 +0100 (CET)

[Message part 1 (text/plain, inline)]

Since 38408 has been pushed, can you close this one if the issue has been fixed?

[Message part 2 (text/html, inline)]

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

From: Leo Famulari <leo <at> famulari.name>
To: Brendan Tildesley via Bug reports for GNU Guix <bug-guix <at> gnu.org>
Cc: "38907 <at> debbugs.gnu.org" <38907 <at> debbugs.gnu.org>
Subject: Re: bug#38907: close?
Date: Sun, 21 Mar 2021 19:50:42 -0400

On Sun, Mar 21, 2021 at 12:09:36PM +0100, Brendan Tildesley via Bug reports for GNU Guix wrote:
> Since 38408 has been pushed, can you close this one if the issue has been fixed?

Anyone is able to close (or reopen) a bug :)

It's done with email. For this bug, it can be closed by sending a
message to <38907-done <at> debbugs.gnu.org>.

The debbugs control interface is described here:

https://debbugs.gnu.org/server-control.html

Previous Next

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