From: Fabio Berton <[email protected]>

This change adds the --no-gpg-sign option to prevent buildhistory
commits from failing due to GPG signing issues. Depending on the setup,
buildhistory may fail to create a commit if the user has the
commit.gpgsign option enabled.

For example, if the user creates a signing key that requires a password,
the commit won't be created and will fail with the following error:

/
|error: Enter passphrase: Load key "/home/<user>/.ssh/id_ed25519":
|incorrect passphrase supplied to decrypt private key?
|fatal: failed to write commit object
\

The bitbake command won't fail, but buildhistory won't have a commit.
Also, the commit may silently fail when building inside a container due
to missing packages or issues with accessing the GPG agent.

This is similar to [1], and signing the buildhistory commit
should be avoided to prevent such issues.

1 - 
https://git.openembedded.org/openembedded-core/commit/?id=7595a0a63a933af9dd9d1e458dc34a4ba80d9eae

Signed-off-by: Fabio Berton <[email protected]>
---
 meta/classes/buildhistory.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/buildhistory.bbclass 
b/meta/classes/buildhistory.bbclass
index 78037a6462..8f605a720e 100644
--- a/meta/classes/buildhistory.bbclass
+++ b/meta/classes/buildhistory.bbclass
@@ -794,7 +794,7 @@ result: $result
 metadata revisions:
 END
        cat ${BUILDHISTORY_DIR}/metadata-revs >> $commitmsgfile
-       git commit $commitopts -F $commitmsgfile --author 
"${BUILDHISTORY_COMMIT_AUTHOR}" > /dev/null
+       git commit --no-gpg-sign $commitopts -F $commitmsgfile --author 
"${BUILDHISTORY_COMMIT_AUTHOR}" > /dev/null
        rm $commitmsgfile
 }
 
-- 
2.43.0

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#230781): 
https://lists.openembedded.org/g/openembedded-core/message/230781
Mute This Topic: https://lists.openembedded.org/mt/117717093/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to