guix pull fails on local channel

I recently installed the full Guix system, and after reading the

sections of the manual about channels I set one up for my personal

modifications to existing packages. Everything worked fine until I

committed changes to one of those package definitions and re-ran 'guix

pull' which fails with:

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. Does anyone have any clues as to what could be

wrong, or how I could go about debugging this?

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"))))

--

Kjartan Óli Ágústsson

GPG Key fingerprint: 4801 0D71 49C0 1DD6 E5FD 6AC9 D757 2FE3 605E E6B0

Am Dienstag, dem 07.06.2022 um 00:20 +0000 schrieb Kjartan Oli

Agustsson:

Chances are that the changes you're trying to commit are ill-formed.

Use an editor that highlights brackets such as Emacs to find out where

you are missing one. If it's in the middle of the file, marking the

whole file and pressing TAB once should make the fault visible – if

it's towards the end, enter closing parentheses until they are no

longer matched up with anything prior.

Cheers

Hi!

Kjartan Oli Agustsson ???

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.

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…

…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.

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

Kind regards,

T G-R

Tobias Geerinckx-Rice <me@tobias.gr> writes:

I just re-initialized the git repo, and changed the channel introduction

to use the initial commit on the new repo. A 'guix pull' ran just fine.

Then I committed a change that added a single newline at the end of a

file, the error came back.

I tried this, the only output I got was:

;;; note: source file ./kjartan/packages/emacs.scm

;;; newer than compiled /gnu/store/bgnnzx7qsiy22yggh3a0q4i0932n6hl7-kjartan/lib/guile/3.0/site-ccache/kjartan/packages/emacs.go

I am well aware of this, everything I have written in every file of the

channel has been written in Emacs, which does not report any unmatched

'(' anywhere in either of the two files I currently have.

--

Kjartan Óli Ágústsson

GPG Key fingerprint: 4801 0D71 49C0 1DD6 E5FD 6AC9 D757 2FE3 605E E6B0