guix pull fails on local channel

Open

Details

3 participants

Kjartan Oli Agustsson
Liliana Marie Prikler
Tobias Geerinckx-Rice

Owner: unassigned

Submitted by: Kjartan Oli Agustsson

Severity: normal

Debbugs page

Kjartan Oli Agustsson wrote 3 years ago

Recipients:(address . bug-guix@gnu.org)

Message-ID:GV1P193MB231058950024F1B6F79943AEDFA59@GV1P193MB2310.EURP193.PROD.OUTLOOK.COM

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:

Toggle quote (4 lines)

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

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

Liliana Marie Prikler wrote 3 years ago

Recipients:

Message-ID:0286bdb4fb92d3b234ecf73f0a26d9e20c539914.camel@ist.tugraz.at

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

Agustsson:

Toggle quote (17 lines)> 
> 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:
> 
> > 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: )
> 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?

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

Tobias Geerinckx-Rice wrote 3 years ago

Re: bug#55826: guix pull fails on local channel

Recipients:(address . kjartanoli@outlook.com)(address . 55826@debbugs.gnu.org)

Message-ID:87tu8w6bjg@nckx

Hi!

Kjartan Oli Agustsson 写道：

Toggle quote (8 lines)

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

Toggle quote (5 lines)

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

Toggle quote (3 lines)

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

Toggle quote (11 lines)> 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

-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCYp8hEw0cbWVAdG9iaWFz

LmdyAAoJEA2w/4hPVW15YT8BAI1CujwU7UkZfDpW2M41J5OuI6bXvF/MyNa0qcPC

5E6pAP9Clsep/VscdjbVJKk9C6DVWKUd+L2W28Omm5fG9stdBw==

=LGUw

-----END PGP SIGNATURE-----

Kjartan Oli Agustsson wrote 3 years ago

Recipients:(name . Tobias Geerinckx-Rice)(address . me@tobias.gr)(address . 55826@debbugs.gnu.org)

Message-ID:GV1P193MB2310207AC70B1E5F86CD34BADFA59@GV1P193MB2310.EURP193.PROD.OUTLOOK.COM

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

Toggle quote (6 lines)

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

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.

Toggle quote (8 lines)

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

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

Toggle quote (10 lines)> 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.

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

Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 55826@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it

mumi current 55826

Then, you may apply the latest patchset in this issue (with sign off)

mumi am -- -s

Or, compose a reply to this issue

mumi compose

Or, send patches to this issue

mumi send-email *.patch

You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags

mumi command -t +confirmed -t +easy

Or, remove the moreinfo tag and set the help tag

mumi command -t -moreinfo -t +help

is:open	open issues
is:done	closed issues
submitter:<who>	search issue submitter
author:<who>	search by message author
date:yesterday..now	search by issue date
mdate:3m..2d	search by message date