bug#52152: Haskell Hackage importer can create dependency cycles

[Philip Munksgaard]

Hi

On Thu, 7 Apr 2022, at 09:45, zimoun wrote:
> On Tue, 08 Mar 2022 at 11:04, zimoun <zimon.toutoune@gmail.com> wrote:
>> And the "cycle" seems expected from OneTuple.cabal:
>>
>> $ cat OneTuple-0.3.1/OneTuple.cabal
>> cabal-version:      >=1.10
>>
>> [...]
>>
>> test-suite th
>>   type:             exitcode-stdio-1.0
>>   default-language: Haskell98
>>   hs-source-dirs:   test
>>   main-is:          th.hs
>>   build-depends:
>>       base
>>     , OneTuple
>>     , template-haskell
>>
>>
>> Well, for what they are worth, based on this remark, two points:
>>
>>  1. I do not know what could be done on Guix side.  An idea?
>>  2. Usually, it is recommended to follow LTS and so Stackage.
>
> I do not think it is a bug from Guix but a bug from OneTuple upstream,
> not in their version 0.2.2.1, and introduce by their version 0.3.1.

I don't think that's correct. My understanding is that it is common (perhaps 
even necessary) to include the library itself in the test-suite dependencies. 
For instance, the same thing appears in attoparsec. However, when importing 
attoparsec, they are filtered out, and indeed we even have functionality to 
filter out the package name [0], but for some reason that doesn't work for 
OneTuple.


0: https://git.savannah.gnu.org/cgit/guix.git/tree/guix/import/hackage.scm#n225