From debbugs-submit-bounces@debbugs.gnu.org Thu Dec 02 09:51:29 2021 Received: (at submit) by debbugs.gnu.org; 2 Dec 2021 14:51:29 +0000 Received: from localhost ([127.0.0.1]:47081 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1msnQn-00084p-K9 for submit@debbugs.gnu.org; Thu, 02 Dec 2021 09:51:29 -0500 Received: from lists.gnu.org ([209.51.188.17]:42158) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1msnQj-00084f-Vu for submit@debbugs.gnu.org; Thu, 02 Dec 2021 09:51:27 -0500 Received: from eggs.gnu.org ([209.51.188.92]:50658) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1msnQj-0002kZ-NE for bug-guix@gnu.org; Thu, 02 Dec 2021 09:51:25 -0500 Received: from mout.kundenserver.de ([212.227.126.130]:55289) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1msnQh-0003Vw-Dd for bug-guix@gnu.org; Thu, 02 Dec 2021 09:51:25 -0500 Received: from hermia.goebel-consult.de ([79.211.184.181]) by mrelayeu.kundenserver.de (mreue012 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MLiXQ-1nAKHQ45su-00Hbuo for ; Thu, 02 Dec 2021 15:51:21 +0100 Received: from [192.168.110.2] (lenashee.goebel-consult.de [192.168.110.2]) by hermia.goebel-consult.de (Postfix) with ESMTP id EF3955F526 for ; Thu, 2 Dec 2021 15:51:25 +0100 (CET) Message-ID: <05024745-375a-4881-911b-048e62cbed47@crazy-compilers.com> Date: Thu, 2 Dec 2021 15:51:18 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.3.2 Content-Language: en-US From: Hartmut Goebel To: bug-guix Organization: crazy-compilers.com Subject: commiter.scm: backtrace if commit fails Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K1:whR/25l/0L/yh2fpNJWPoP7R97ZW7j8txD9R90I83bq8d8RDxhH TQBSwRYmuUuwkqZMe3wiJNngugrh2OXQK8/kG1AxooqsROHehQqranm3+vui3QVMZEO5ODq kLAysO51q6ictnv9KLYhgFAgnFn2QOj4rHr8zkS37TdeyYnuDuPP/MQD7Bhxzw4deNwJtjF YEz12ZO7RoVdGLC2DTNZw== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:+GyxfAnAjzM=:npeLHrGoF0KOJon5vSAg/9 XUFkZ6Myni5llHyx4bQT8Png0K5Sp6qzrNza/D6DPylQvYWIwmSfUqCmsuHh98Ly8y5/Bpp0n fk7U5e1Dp7e7BRW9DE1yIXG3JeWpXugudOicEAAPMQkXN9vc448RwuB2MPvyecMOHZuNz5Ek9 e2NNEsR/KPiGAmGFFLmLBknjB819AcngPxmnqJpgQP4LZOv4LP3MI3O9aHOW+RodMmCWhEvlP p2sL9r4t8utH8+8KkSJUU9z9DYRVveRFDODcVFw10tQENlgrpIiLHYcA+HYAnpBWO3QrtjGmR 07Y+C+eJUHUp/n+5SEvrhVtn9dgfoC1YxfcF1Iiwwng7TRVFVuYsYYSMa1mpc7B6jjCgbLCzl jDQPeQsTMpgdnYQbObw2wDnmwjzPbGoAJQwGYaAcD37GMWLMlnvEylsAOSWqSFsw8qItxjlsj BqE6/oJhfdoHFGP7Ovgtk0Ql1EwJN9uusZVPm8tTw5znDiM2brtPrBKonX4LDykywKLyrdWML VSahLOtKnKylsF8zh33+GRC3zxWtHgceuyIIXZmWxLMr4uR6uvDEvipTzjc++lVvTA8nTPNiS UYMqcRkSe4r1TisHRSBJ98qkwrEJzoSW8/eehhW3wohRGshT4w/v8zwRJjID7Kc7EPChmbj+7 usKjwhhBmpfzyGxnLH9zpzxVfmjxqrKUEcxAO+M+ZVEKBdGHlwz7zENYkh1hqbnbIQ3Fw1A+E jkwOM+Xdv0snIlEP Received-SPF: none client-ip=212.227.126.130; envelope-from=h.goebel@crazy-compilers.com; helo=mout.kundenserver.de X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: submit X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) 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 #) In ice-9/boot-9.scm:    724:2  5 (call-with-prompt _ _ #) In ice-9/eval.scm:    619:8  4 (_ #(#(#))) 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 # …) 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 |