[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#54760: import: hackage: Internal libraries are not filtered out of d
From: |
Philip Munksgaard |
Subject: |
bug#54760: import: hackage: Internal libraries are not filtered out of dependency list |
Date: |
Thu, 02 Jun 2022 11:53:28 +0200 |
User-agent: |
Cyrus-JMAP/3.7.0-alpha0-591-gfe6c3a2700-fm-20220427.001-gfe6c3a27 |
Hi Lars,
On Sun, 22 May 2022, at 11:37, Lars-Dominik Braun wrote:
>> The attoparsec package on hackage defines multiple internal libraries inside
>> one package, named "attoparsec" and "attoparsec-internal", with the first
>> depending on the latter. Importing attoparsec using `guix import hackage
>> attoparsec` therefore yields the following erroneous package definition: […]
>
> attached patches should fix this. I tried them with both, attoparsec and
> raaz, and internal libraries appear neither in inputs nor native inputs
> any more.
>
Indeed, that seems to work for those packages, but it still doesn't seem to
work for OneTuple, as mentioned here: https://issues.guix.gnu.org/52152#3
Also, attoparsec still won't build with result of the import, but for different
reasons.
- bug#54760: import: hackage: Internal libraries are not filtered out of dependency list,
Philip Munksgaard <=