unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: jgart <jgart@dismail.de>
To: Guix Help <help-guix@gnu.org>
Subject: committer.scm
Date: Mon, 31 Oct 2022 20:42:55 -0500	[thread overview]
Message-ID: <20221031204255.GB29692@dismail.de> (raw)

Hi,

Does anyone know how to use the committer.scm script or how it is intended to be used?

This is what my unstaged area looks like:

$ guix-shell  git status
On branch master
Your branch is ahead of 'origin/master' by 4 commits.
  (use "git push" to publish your local commits)

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   gnu/packages/crates-io.scm
        modified:   gnu/packages/rust-apps.scm

no changes added to commit (use "git add" and/or "git commit -a")

This is what it looks like when I call the script in a guix shell:

$ ./etc/committer.scm
committer.scm     committer.scm.in
 guix-shell  etc/committer.scm the-way
Backtrace:
In ice-9/eval.scm:
   721:20 19 (primitive-eval (use-modules ((sxml xpath) #:prefix …) …))
In ice-9/psyntax.scm:
  1218:36 18 (expand-top-sequence (#<syntax:committer.scm:32:0 (us…>) …)
  1210:19 17 (parse _ (("placeholder" placeholder)) ((top) #(# # …)) …)
   259:10 16 (parse _ (("placeholder" placeholder)) (()) _ c&e (eval) …)
In ice-9/boot-9.scm:
  3935:20 15 (process-use-modules _)
   222:29 14 (map1 (((sxml xpath) #:prefix xpath:) ((srfi srfi-1)) …))
   222:29 13 (map1 (((srfi srfi-1)) ((srfi srfi-2)) ((srfi #)) (#) …))
   222:29 12 (map1 (((srfi srfi-2)) ((srfi srfi-9)) ((srfi #)) (#) …))
   222:29 11 (map1 (((srfi srfi-9)) ((srfi srfi-11)) ((srfi #)) (#) …))
   222:29 10 (map1 (((srfi srfi-11)) ((srfi srfi-26)) ((ice-9 #)) # …))
   222:29  9 (map1 (((srfi srfi-26)) ((ice-9 format)) ((ice-9 #)) # …))
   222:29  8 (map1 (((ice-9 format)) ((ice-9 popen)) ((ice-9 #)) # …))
   222:29  7 (map1 (((ice-9 popen)) ((ice-9 match)) ((ice-9 #)) (#) …))
   222:29  6 (map1 (((ice-9 match)) ((ice-9 rdelim)) ((ice-9 #)) # #))
   222:29  5 (map1 (((ice-9 rdelim)) ((ice-9 regex)) ((ice-9 #)) (#)))
   222:29  4 (map1 (((ice-9 regex)) ((ice-9 textual-ports)) ((# #))))
   222:29  3 (map1 (((ice-9 textual-ports)) ((guix gexp))))
   222:17  2 (map1 (((guix gexp))))
  3936:31  1 (_ ((guix gexp)))
   3330:6  0 (resolve-interface (guix gexp) #:select _ #:hide _ # _ # …)

ice-9/boot-9.scm:3330:6: In procedure resolve-interface:
no code for module (guix gexp)



             reply	other threads:[~2022-11-01  1:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01  1:42 jgart [this message]
2022-11-01  6:57 ` committer.scm Julien Lepiller
2022-11-01 22:19   ` committer.scm jgart
2022-11-02  9:19     ` committer.scm Csepp

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=20221031204255.GB29692@dismail.de \
    --to=jgart@dismail.de \
    --cc=help-guix@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.
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).