GNU bug report logs - #38709
Recursive crate importer ignores specified version

Previous Next

Package: guix;

Reported by: Valentin Ignatev <valentignatev <at> gmail.com>

Date: Sun, 22 Dec 2019 18:57:02 UTC

Severity: normal

Done: Ludovic Courtès <ludo <at> gnu.org>

Bug is archived. No further changes may be made.

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

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

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#38709; Package guix. (Sun, 22 Dec 2019 18:57:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Valentin Ignatev <valentignatev <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Sun, 22 Dec 2019 18:57:02 GMT) Full text and rfc822 format available.

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 crate importer ignores specified version
Date: Sun, 22 Dec 2019 21:56:03 +0300
[Message part 1 (text/plain, inline)]
When I'm trying to recursively import specific crate version, it
imports the latest version instead:

guix import crate --recursive notify <at> 4.0.14 gives this output:
following redirection to
`https://static.crates.io/crates/notify/notify-5.0.0-pre.1.crate'...
following redirection to
`https://static.crates.io/crates/anymap/anymap-0.12.1.crate'...
following redirection to
`https://static.crates.io/crates/bitflags/bitflags-1.2.1.crate'...

And so on, so it follows notify-5.0.0 instead of 4.0.14

Regards,
Valentin Ignatev
[crate_importer.png (image/png, attachment)]

Information forwarded to bug-guix <at> gnu.org:
bug#38709; Package guix. (Thu, 26 Dec 2019 03:20:01 GMT) Full text and rfc822 format available.

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

From: Martin Becze <mjbecze <at> riseup.net>
To: Valentin Ignatev <valentignatev <at> gmail.com>
Cc: bug-Guix <bug-guix-bounces+mjbecze=riseup.net <at> gnu.org>,
 38709 <at> debbugs.gnu.org
Subject: Re: bug#38709: Recursive crate importer ignores specified version
Date: Wed, 25 Dec 2019 19:19:52 -0800
On 2019-12-22 18:56, Valentin Ignatev wrote:
> When I'm trying to recursively import specific crate version, it
> imports the latest version instead:
> 
> guix import crate --recursive notify <at> 4.0.14 gives this output:
> following redirection to
> `https://static.crates.io/crates/notify/notify-5.0.0-pre.1.crate'...
> following redirection to
> `https://static.crates.io/crates/anymap/anymap-0.12.1.crate'...
> following redirection to
> `https://static.crates.io/crates/bitflags/bitflags-1.2.1.crate'...
> 
> And so on, so it follows notify-5.0.0 instead of 4.0.14
> 
> Regards,
> Valentin Ignatev

Currently the recusive importer doesn't respect version numbers.
Progress is being made on this in issue 38408
https://issues.guix.gnu.org/issue/38408

-Martin Becze




Information forwarded to bug-guix <at> gnu.org:
bug#38709; Package guix. (Thu, 26 Dec 2019 05:26:02 GMT) Full text and rfc822 format available.

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

From: Valentin Ignatev <valentignatev <at> gmail.com>
To: Martin Becze <mjbecze <at> riseup.net>
Cc: bug-Guix <bug-guix-bounces+mjbecze=riseup.net <at> gnu.org>,
 38709 <at> debbugs.gnu.org
Subject: Re: bug#38709: Recursive crate importer ignores specified version
Date: Thu, 26 Dec 2019 08:25:29 +0300
Hey Martin, thanks! I'll follow that one then!

I guess this bug can be closed since there's already quite a
discussion in #38408

Valentin

On 12/26/19, Martin Becze <mjbecze <at> riseup.net> wrote:
> On 2019-12-22 18:56, Valentin Ignatev wrote:
>> When I'm trying to recursively import specific crate version, it
>> imports the latest version instead:
>>
>> guix import crate --recursive notify <at> 4.0.14 gives this output:
>> following redirection to
>> `https://static.crates.io/crates/notify/notify-5.0.0-pre.1.crate'...
>> following redirection to
>> `https://static.crates.io/crates/anymap/anymap-0.12.1.crate'...
>> following redirection to
>> `https://static.crates.io/crates/bitflags/bitflags-1.2.1.crate'...
>>
>> And so on, so it follows notify-5.0.0 instead of 4.0.14
>>
>> Regards,
>> Valentin Ignatev
>
> Currently the recusive importer doesn't respect version numbers.
> Progress is being made on this in issue 38408
> https://issues.guix.gnu.org/issue/38408
>
> -Martin Becze
>




Reply sent to Ludovic Courtès <ludo <at> gnu.org>:
You have taken responsibility. (Mon, 30 Dec 2019 22:21:01 GMT) Full text and rfc822 format available.

Notification sent to Valentin Ignatev <valentignatev <at> gmail.com>:
bug acknowledged by developer. (Mon, 30 Dec 2019 22:21:01 GMT) Full text and rfc822 format available.

Message #16 received at 38709-done <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Valentin Ignatev <valentignatev <at> gmail.com>
Cc: 38709-done <at> debbugs.gnu.org
Subject: Re: bug#38709: Recursive crate importer ignores specified version
Date: Mon, 30 Dec 2019 23:20:22 +0100
Hi Valentin,

Valentin Ignatev <valentignatev <at> gmail.com> skribis:

> When I'm trying to recursively import specific crate version, it
> imports the latest version instead:
>
> guix import crate --recursive notify <at> 4.0.14 gives this output:
> following redirection to
> `https://static.crates.io/crates/notify/notify-5.0.0-pre.1.crate'...
> following redirection to
> `https://static.crates.io/crates/anymap/anymap-0.12.1.crate'...
> following redirection to
> `https://static.crates.io/crates/bitflags/bitflags-1.2.1.crate'...
>
> And so on, so it follows notify-5.0.0 instead of 4.0.14

Commit c7ca707b59304a978cab8c5c25401259c6c18214 should fix this.

Martin Becze <mjbecze <at> riseup.net> skribis:

> Currently the recusive importer doesn't respect version numbers.
> Progress is being made on this in issue 38408
> https://issues.guix.gnu.org/issue/38408

Yes, that will come in handy, though I think
c7ca707b59304a978cab8c5c25401259c6c18214 does provides the immediate fix
for the issue at hand.

Thanks,
Ludo’.




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Tue, 28 Jan 2020 12:24:04 GMT) Full text and rfc822 format available.

This bug report was last modified 4 years and 84 days ago.

Previous Next


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