A patch has been submitted for the second part of this issue [0] and a new
issue has been created for the first part [1]. I'm therefore closing this issue.
0: https://issues.guix.gnu.org/54729
1: https://issues.guix.gnu.org/54760
On Wed, 6 Apr 2022, at 21:27, zimoun wrote:
> Hi,
>
> On Mon, 31
Hi,
On Mon, 31 Jan 2022 at 11:33, "Philip Munksgaard" wrote:
> ```
> (define-module (gnu packages futhark)
> #:use-module (guix packages)
> #:use-module (guix download)
> #:use-module (guix build-system haskell)
> #:use-module (guix licenses)
> #:use-module (guix git-download)
>
Hi,
On Wed, 23 Feb 2022 at 12:27, Philip Munksgaard wrote:
> The relevant section states:
>
> > This option outputs a directory if the package requires multiple
> > registrations: this can occur if internal/convenience libraries are used.
> > These configuration file names are sorted so that
On Wed, 23 Feb 2022, at 12:06, Philip Munksgaard wrote:
> And yes, this is indeed the issue I'm mostly concerned about. It seems
> like
> `/gnu/store/25ql0xsjqf0alrvy6hmpw6gzirzbqfmv-ghc-attoparsec-0.14.4/ghc-attoparsec-0.14.4.conf`
>
> is expected to be a file, while it is in fact a
On Wed, 23 Feb 2022, at 11:02, zimoun wrote:
> It is 2 different issues; therefore I propose to keep them separated.
Yes, I agree, sorry for the confusion.
> Let focus on this oneā¦
>
>> When trying to build this file however, I get the following error:
>>
>> ```
>> running "runhaskell Setup.hs"
Hi,
Thanks for he report.
It is 2 different issues; therefore I propose to keep them separated.
On Mon, 31 Jan 2022 at 11:33, "Philip Munksgaard" wrote:
> ```
> $ guix import hackage -r attoparsec
[...]
>
> guix/import/utils.scm:492:33: In procedure lookup-node:
> Wrong number of values
I'm trying to build a newer version of attoparsec than the one included in
guix, namely version 0.14.4.
First of all, `guix import hackage -r attoparsec` fails, as far as I can tell
because of the requirement to attoparsec-internal, with the following error:
```
$ guix import hackage -r