GNU bug report logs -
#49418
Importing haskell packages from hackage doesn't apply metadata revisions
Previous Next
Full log
Message #19 received at 49418-done <at> debbugs.gnu.org (full text, mbox):
On Wed, 7 Jul 2021, at 07:58, Philip Munksgaard wrote:
> On Wed, 7 Jul 2021, at 05:26, John Kehayias via Bug reports for GNU Guix wrote:
> > Actually, this does exist in the Haskell build system in Guix, but
> > seems to be undocumented and not used by the importer. You can add the
> > following to the arguments (in the bootstrap package in this case) to
> > use a metadata revision:
> >
> > #:cabal-revision ("2" "0a6j3313vz7n7dn8abddyib4jggblaq89f87ib4imdwjxjajbm33")
> >
> > The hash is from running guix hash file (where file = 2.cabal in this
> > case, downloaded from Hackage). This should be part of the importer, to
> > specify a revision or by default grab the latest, I would say.
> >
> > (and I'm guessing you know this is packaged in guix as
> > integer-logarithms, without the "ghc-" prefix for some reason; not the
> > only package like that I've noticed)
> >
>
> Ah yes, good catch! I agree that the fix should be to amend the
> importer, such that it finds out about these revisions and
> automatically uses the latest one.
Actually, upon closer inspection, that's exactly what it does! Instead of actually using the importer in my original example (as I claimed), I had actually just modified the code from gnu/packages/haskell-xyz.scm. Doing a fresh import correctly picks up that there is a new revision of the cabal file and produces the right derivation. I'll close this issue.
This bug report was last modified 3 years and 316 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.