unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Philip Munksgaard" <philip@munksgaard.me>
To: "Lars-Dominik Braun" <lars@6xq.net>
Cc: 54760@debbugs.gnu.org
Subject: bug#54760: import: hackage: Internal libraries are not filtered out of dependency list
Date: Thu, 02 Jun 2022 11:53:28 +0200	[thread overview]
Message-ID: <f9c895e0-28c6-4069-969e-00ace03055bf@www.fastmail.com> (raw)
In-Reply-To: <YooEVtIztcFN2nrI@noor.fritz.box>

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.




  reply	other threads:[~2022-06-02  9:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07  8:18 bug#54760: import: hackage: Internal libraries are not filtered out of dependency list Philip Munksgaard
2022-05-22  9:37 ` Lars-Dominik Braun
2022-06-02  9:53   ` Philip Munksgaard [this message]
2022-06-02  9:59     ` Philip Munksgaard
2022-06-02 11:31       ` Philip Munksgaard
2022-06-02 11:57         ` Lars-Dominik Braun
2022-06-02 12:47           ` Philip Munksgaard
2022-06-05  9:43             ` Lars-Dominik Braun
2022-06-06 11:30   ` 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=f9c895e0-28c6-4069-969e-00ace03055bf@www.fastmail.com \
    --to=philip@munksgaard.me \
    --cc=54760@debbugs.gnu.org \
    --cc=lars@6xq.net \
    /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).