all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Clément Lassieur" <clement@lassieur.org>
To: "Marek Paśnikowski" <marek@marekpasnikowski.pl>
Cc: help-guix@gnu.org
Subject: Re: Cannot build personal channel derivation during guix pull
Date: Wed, 24 Jan 2024 02:42:57 +0100	[thread overview]
Message-ID: <87r0i78q1q.fsf@lassieur.org> (raw)
In-Reply-To: <1899125.tdWV9SEqCh@akashi> ("Marek Paśnikowski"'s message of "Tue, 23 Jan 2024 16:17:48 +0100")

Hello Marek,

On Tue, Jan 23 2024, Marek Paśnikowski wrote:

> Dear All
>
> This is my first attempt to connect to my personal Guix channel. After ironing 
> out server-side inadequacies in my configuration code, I encountered a very 
> resilient, cryptic error.
>
> After one day of experimentation, where nothing I did made the error change, I 
> turn to your experience and knowledge. Could I ask to take a look at my 
> repository ( hosted on https://git.marekpasnikowski.pl/channel.git , branch 
> wip-channel - master has incorrect parens in authorization code ) and see if I 
> missed anything in the file structure?
>
> Also, I would appreciate a confirmation whether the channel can be pulled on 
> your system. I do keep in mind a possibility of a local impurity or cache 
> poison.

I cloned your "channel.git" and checked out branch "wip-channel" but I
found nothing there that looks like a channel.  There are dotfiles, a
home and an os file, but that's not what a channel is.  A channel is a
bunch of guix modules (usually packages) that are meant to be shared.
It typically looks like guix or nonguix.

Dotfiles should not be in a channel because you don't want them to be in
your store.

If things are not meant to be shared, then there is no need to do a
channel.

Hope it helps,
Clément

P.S. Your parenthesis style doesn't help to read your code ;)

> Here is my current channels.scm:
>
> ( list
>   ( channel
>     ( name 'guix )
>     ( branch "master" )
>     ( url "https://git.savannah.gnu.org/git/guix.git" )
>     ( introduction
>       ( make-channel-introduction
>         "9edb3f66fd807b096b48283debdcddccfea34bad"
>         ( openpgp-fingerprint
>           "BBB0 2DDF 2CEA F6A8 0D1D E643 A2A0 6DF2 A33A 54FA" ) ) ) )
>   ( channel
>     ( name 'personal-channel )
>     ( branch "wip-channel" )
>     ( introduction
>       ( make-channel-introduction
>         "f8ccfe8f3e5c8bafe06665cbd4b0c9301e1a64b6"
>         ( openpgp-fingerprint
>           "590E 500F E39D 26B3 E60B 743B 6D81 B120 7711 899F" ) ) )
>     ( url "https://git.marekpasnikowski.pl/git/channel.git" ) ) )
>
> And this is the COMPLETE build log I receive every single time:
>
> $ zcat /var/log/guix/drvs/hg/15jjf4dr5z7lsfvcj07z2mrw69kzvp-personal-
> channel.drv.gz
>
> (repl-version 0 1 1)
> (exception unbound-variable (value #f) (value "Unbound variable: ~S") (value 
> (channel)) (value #f))


  parent reply	other threads:[~2024-01-24  1:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 15:17 Cannot build personal channel derivation during guix pull Marek Paśnikowski
2024-01-23 22:09 ` Felix Lechner via
2024-01-24  1:42 ` Clément Lassieur [this message]
2024-01-24  6:28   ` Marek Paśnikowski
2024-01-26 21:32 ` Marek Paśnikowski
2024-01-27 17:27   ` Parnikkapore via
2024-01-28 12:23     ` Marek Paśnikowski

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r0i78q1q.fsf@lassieur.org \
    --to=clement@lassieur.org \
    --cc=help-guix@gnu.org \
    --cc=marek@marekpasnikowski.pl \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.