unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: guix-devel@gnu.org
Subject: Re: a GUIX_PACKAGE_PATH / modules puzzle
Date: Wed, 02 May 2018 22:16:53 -0700	[thread overview]
Message-ID: <87bmdxwc6y.fsf@gmail.com> (raw)
In-Reply-To: <20180501223951.whoj67yv2h3t6wyl@abyayala> (Nils Gillmann's message of "Tue, 1 May 2018 22:39:51 +0000")

[-- Attachment #1: Type: text/plain, Size: 2107 bytes --]

Nils Gillmann <gillmann@infotropique.org> writes:

> Hi,
>
> I'm not sure if guile-users / -dev liste is more appropriate. If it is, let me know.
>
> I'm currently still using GUIX_PACKAGE_PATH until I got my layout all set up.
> There's an issue that I can't seem to get rid of, I'll try my best to describe it now:
>
> I have package definitions in 2 repositories (3 to be precise, +1 WIP repo). Both follow
> the exact same layout that can still be understood by Guix and GPP (GUIX_PACKAGE_PATH).
>
> Repository 1: /home/user/src/infotropique/ports
> Repository 2: /home/user/src/infotropique/pkgs
>
> The modules are in similar named subfolders, following the layout $REPONAME $CATEGORY $NAME NAME.
>
> I only switched to this recently, previously the "CATEGORY NAME NAME" was located in the root of
> the reository. Both repos worked this way.
>
> After the transition to the new layout, ports works.
> pkgs however is throwing errors at me for days. I've tried moving all but one module
> out of the repo, same error. It was a simple easy, no repo-internal dependencies, module.
> The error is always similar to https://ftp.n0.is/pub/pkgs-error.txt
>
> I can not share the actual repo at this moment on this mailinglist, but maybe the
> repl message is something that someone could give me a hint, even if it's just a
> tiny bit of a "read this manpage" or something like that would help. I've tried
> debugging this for days and any help's welcome.

Could this error be coming from the scheme-files procedure in (guix
discovery)?  It looks like that's the only place where fold-right is
invoked in that module, and it seems to match up with the stack trace,
unless I'm misreading it (which is possible).  You might find it useful
to insert some pk statements into that code to try to figure out what is
being evaluated as "unspecified".  My guess, which could be wrong, is
that perhaps scandir* is returning an unspecified value unintentionally
at some point?  Someone with more experience debugging Guile code can
probably provide better advice.

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-05-03  5:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 22:39 a GUIX_PACKAGE_PATH / modules puzzle Nils Gillmann
2018-05-03  5:16 ` Chris Marusich [this message]
2018-05-03  5:36   ` Nils Gillmann
2018-05-03  7:23     ` Chris Marusich
2018-05-03  8:30       ` Nils Gillmann
2018-05-10 22:27         ` Nils Gillmann
2018-05-10 23:26           ` Nils Gillmann
2018-05-11  7:00             ` Nils Gillmann
2018-05-11  7:19               ` Nils Gillmann
2018-05-12 13:43               ` Ricardo Wurmus
2018-05-12 19:45                 ` Nils Gillmann
2018-05-13  5:15                   ` Ricardo Wurmus
2018-05-11  7:36   ` Nils Gillmann

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=87bmdxwc6y.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=guix-devel@gnu.org \
    /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).