From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: 52244@debbugs.gnu.org
Subject: bug#52244: commiter.scm: backtrace if commit fails
Date: Thu, 2 Dec 2021 15:51:18 +0100 [thread overview]
Message-ID: <05024745-375a-4881-911b-048e62cbed47@crazy-compilers.com> (raw)
When commiting the change fails, committer.scm outputs a backtrace.
While one can packagers be experienced enough to understand the error
even if it is garbled by the backtrace,
I propose suppressing it for two reasons:
1. The backtrace makes it harder to spot the actual error (since one
needs to "parse" more text)
2. I often have issues with my guix development environment being
instable. So when I see a backtrace from commiter.scm, I think about
issues with my environment first - and not about an issue with git :-)
Expected
================
No backtrace, but a concise error message, like here:
$ ./pre-inst-env guile ./etc/committer.scm
gnu: python-stdnum: Update to 1.17.
* gnu/packages/finance.scm (python-stdnum): Update to 1.17.
error: gpg beim Signieren der Daten fehlgeschlagen
fatal: Fehler beim Schreiben des Commit-Objektes.
etc/committer.scm:399:24: Cannot commit
Reproduce
=================
There might be other ways to trigger a failing "git commit". For me it
occured when using an outdated PGPG key for signing:
1. Configure git to use the outdated GPG key for signing, e.g.
git config --get user.signingkey 634A8DFFD3F631DF
2. use committer.scm to commit some changes:
$ ./pre-inst-env guile ./etc/committer.scm
gnu: python-stdnum: Update to 1.17.
* gnu/packages/finance.scm (python-stdnum): Update to 1.17.
error: gpg beim Signieren der Daten fehlgeschlagen
fatal: Fehler beim Schreiben des Commit-Objektes.
Backtrace:
In ice-9/boot-9.scm:
1752:10 7 (with-exception-handler _ _ #:unwind? _ # _)
In unknown file:
6 (apply-smob/0 #<thunk 7f47664f5f60>)
In ice-9/boot-9.scm:
724:2 5 (call-with-prompt _ _ #<procedure default-prompt-handle…>)
In ice-9/eval.scm:
619:8 4 (_ #(#(#<directory (guile-user) 7f47664efc80>)))
In ice-9/boot-9.scm:
2835:4 3 (save-module-excursion _)
4380:12 2 (_)
In srfi/srfi-1.scm:
634:9 1 (for-each #<procedure 7f47648b19a0 at etc/committer.sc…> …)
In etc/committer.scm:
399:24 0 (_ _)
etc/committer.scm:399:24: Cannot commit
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
reply other threads:[~2021-12-02 14:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=05024745-375a-4881-911b-048e62cbed47@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=52244@debbugs.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.
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.