GNU bug report logs - #35750
`guix import hackage` is unaware of metadata revisions

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 35750 in the body.
You can then email your comments to 35750 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: Robert Vollmert <rob <at> vllmrt.net>
To: bug-guix <at> gnu.org
Subject: `guix import hackage` is unaware of metadata revisions
Date: Wed, 15 May 2019 17:06:48 +0200

As far as I can tell, `guix import hackage` imports the first revision of a hackage
release.

I suggest aiming to import the latest cabal revision from hackage, as
already supported by haskell-build-system via the #:cabal-version
argument.

In the meantime, documenting this in the `guix import hackage` documentation
would be much appreciated, it took me quite a long time to figure out what
was going wrong here.

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

From: Timothy Sample <samplet <at> ngyro.com>
To: Robert Vollmert <rob <at> vllmrt.net>
Cc: 35750-done <at> debbugs.gnu.org
Subject: Re: bug#35750: `guix import hackage` is unaware of metadata revisions
Date: Thu, 13 Jun 2019 22:32:25 -0400

Hi Robert,

Robert Vollmert <rob <at> vllmrt.net> writes:

> As far as I can tell, `guix import hackage` imports the first revision
> of a hackage
> release.
>
> I suggest aiming to import the latest cabal revision from hackage, as
> already supported by haskell-build-system via the #:cabal-version
> argument.

Thanks to your patch <https://bugs.gnu.org/36048>, this is now fixed.
Closing.


-- Tim

Previous Next

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