From: "Philip Munksgaard" <philip@munksgaard.me>
To: zimoun <zimon.toutoune@gmail.com>,
"John Kehayias" <john.kehayias@protonmail.com>
Cc: 52152@debbugs.gnu.org
Subject: bug#52152: Haskell Hackage importer can create dependency cycles
Date: Thu, 07 Apr 2022 10:10:39 +0200 [thread overview]
Message-ID: <f6a5957c-eaf0-4852-9f45-9cfb631485cd@www.fastmail.com> (raw)
In-Reply-To: <86h77549ri.fsf@gmail.com>
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
next prev parent reply other threads:[~2022-04-07 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 2:50 bug#52152: Haskell Hackage importer can create dependency cycles John Kehayias via Bug reports for GNU Guix
2022-03-08 10:04 ` zimoun
2022-04-07 7:45 ` zimoun
2022-04-07 8:10 ` Philip Munksgaard [this message]
2022-06-07 7:31 ` Lars-Dominik Braun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f6a5957c-eaf0-4852-9f45-9cfb631485cd@www.fastmail.com \
--to=philip@munksgaard.me \
--cc=52152@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=zimon.toutoune@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).