unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: kjartanoli@outlook.com
Cc: 55826@debbugs.gnu.org
Subject: bug#55826: guix pull fails on local channel
Date: Tue, 07 Jun 2022 11:34:35 +0200	[thread overview]
Message-ID: <87tu8w6bjg@nckx> (raw)
In-Reply-To: <mailman.8438.1654578063.1231.bug-guix@gnu.org>

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

Hi!

Kjartan Oli Agustsson 写道:
>> Updating channel 'kjartan' from Git repository at 
>> 'file:///home/kjartan/guix-custom'...
>> Authenticating channel 'kjartan', commits 3bd6c82 to 6677083 (1 
>> new commits)...
>> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
>> #<unknown port>:5:1: unexpected end of input while searching 
>> for: )

Guile errors are quite literal-minded, most of the time.  All the 
world's a string, and parsing it an adventure.

This error means that you have a missing or mismatched closing ) 
somewhere, or didn't close a " so Guile doesn't see it, or…

It's impossible to say more without seeing the code.

> If I delete the git repository and re-initialize it the pull is
> successful, but once I commit any changes to this new repository 
> the
> problem re-appears.

It must be some specific change/file, not any change.

A quick and dirty

  ~/guix-custom$ guix repl -L. <each/scheme/file/in/turn.scm

might be enough: Guile will print all kinds of things to ignore, 
but if you see the same error about searching for ), you'll know 
that the problem is in that file.

But really…

> Does anyone have any clues as to what could be
> wrong, or how I could go about debugging this?

…use an editor (like emacs, but other fine and graphical editors 
are available) that balances or at least highlights brackets. 
Manually counting them is madness and not how anybody writes Lisps 
in real life.

> If it helps the channel definition is:
> (channel
>   (name 'kjartan) 
> 	(url "file:///home/kjartan/guix-custom")
> 	(introduction
> 		 (make-channel-introduction
>       	"3bd6c82a5bb588c35ead0458036aac0ef60f166a"
> 				(openpgp-fingerprint
> 		    	 "4801 0D71 49C0 1DD6 E5FD  6AC9 D757 2FE3 
> 605E E6B0"))))

This looks fine, but I was unable to clone the repository. :-)

Kind regards,

T G-R

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

       reply	other threads:[~2022-06-07 10:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.8438.1654578063.1231.bug-guix@gnu.org>
2022-06-07  9:34 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2022-06-07 22:10   ` bug#55826: guix pull fails on local channel Kjartan Oli Agustsson
2022-06-07  0:20 Kjartan Oli Agustsson
2022-06-07  6:32 ` Liliana Marie Prikler

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=87tu8w6bjg@nckx \
    --to=bug-guix@gnu.org \
    --cc=55826@debbugs.gnu.org \
    --cc=kjartanoli@outlook.com \
    --cc=me@tobias.gr \
    /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).