From: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
To: hongxu.jia@eng.windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/4] gnupg: upgrade 2.5.0 -> 2.5.1
Date: Thu, 28 Nov 2024 16:23:26 +0100 [thread overview]
Message-ID: <Z0iK7kmJ1PpkGXJf@bootlin-mathieu> (raw)
In-Reply-To: <20241127233600.4124020-2-hongxu.jia@windriver.com>
On Wed, Nov 27, 2024 at 03:35:58PM -0800, hongxu via lists.openembedded.org wrote:
> Due to upstream [build: Remove configure option --enable-gpg-is-gpg2][1],
> drop option --enable-gpg-is-gpg2 and remove gpg2 installation
>
> Due to upsream [doc: Remove included yat2m and build HTML versions of
> the man pages.][2], it used standard detection on yat2m other than build
> it from source. Because no native recipe provide yat2m in Yocto,
> explicitly disable doc via option --disable-doc
>
> [1] https://github.com/gpg/gnupg/commit/2125f228d36c0882a87bce433a18253154653d50
> [2] https://github.com/gpg/gnupg/commit/60c541f5880e8c603ca9372d3ca8b7ad68b97018
>
Hi,
I believe this patch is the source of some errors we get on the
autobuilder:
AssertionError: Command 'gpgconf --list-dirs --homedir /tmp/oeqa-feed-sign-pnrdr5tx; gpg -v --batch --homedir /tmp/oeqa-feed-sign-pnrdr5tx --import
/srv/pokybuild/yocto-worker/oe-selftest-fedora/build/build-st-2070984/meta-selftest/files/signing/key.secret' returned non-zero exit status 2:
sysconfdir:/srv/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/gnupg-native/2.5.1/recipe-sysroot-native/etc/gnupg
bindir:/srv/pokybuild/yocto-worker/oe-selftest-fedora/build/build-st-2070984/tmp/work/x86_64-linux/gnupg-native/2.5.1/recipe-sysroot-native/usr/bin/../../usr/bin
libexecdir:/srv/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/gnupg-native/2.5.1/recipe-sysroot-native/usr/libexec
libdir:/srv/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/gnupg-native/2.5.1/recipe-sysroot-native/usr/lib/gnupg
datadir:/srv/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/gnupg-native/2.5.1/recipe-sysroot-native/usr/share/gnupg
localedir:/srv/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/gnupg-native/2.5.1/recipe-sysroot-native/usr/share/locale
socketdir:/run/user/6000/gnupg/d.3hczswacngxo5d1e9ddydbj1
dirmngr-socket:/run/user/6000/gnupg/d.3hczswacngxo5d1e9ddydbj1/S.dirmngr
keyboxd-socket:/run/user/6000/gnupg/d.3hczswacngxo5d1e9ddydbj1/S.keyboxd
agent-ssh-socket:/run/user/6000/gnupg/d.3hczswacngxo5d1e9ddydbj1/S.gpg-agent.ssh
agent-extra-socket:/run/user/6000/gnupg/d.3hczswacngxo5d1e9ddydbj1/S.gpg-agent.extra
agent-browser-socket:/run/user/6000/gnupg/d.3hczswacngxo5d1e9ddydbj1/S.gpg-agent.browser
agent-socket:/run/user/6000/gnupg/d.3hczswacngxo5d1e9ddydbj1/S.gpg-agent.yocto-native
homedir:/tmp/oeqa-feed-sign-pnrdr5tx
gpg: enabled compatibility flags:
gpg: keybox '/tmp/oeqa-feed-sign-pnrdr5tx/pubring.kbx' created
gpg: armor header: Version: GnuPG v1
gpg: sec rsa2048/7B31316B5D64AD52 2015-10-14 testuser (nocomment) <testuser@testemail.com>
gpg: /tmp/oeqa-feed-sign-pnrdr5tx/trustdb.gpg: trustdb created
gpg: using pgp trust model
gpg: key 7B31316B5D64AD52: public key "testuser (nocomment) <testuser@testemail.com>" imported
gpg: no running gpg-agent - starting '/srv/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/gnupg-native/2.5.1/recipe-sysroot-native/usr/bin/gpg-agent'
gpg: waiting for the agent to come up ... (5s)
gpg: waiting for the agent to come up ... (4s)
gpg: waiting for the agent to come up ... (3s)
gpg: waiting for the agent to come up ... (2s)
gpg: waiting for the agent to come up ... (1s)
gpg: can't connect to the gpg-agent: IPC connect call failed
gpg: no running gpg-agent - starting '/srv/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/x86_64-linux/gnupg-native/2.5.1/recipe-sysroot-native/usr/bin/gpg-agent'
gpg: waiting for the agent to come up ... (5s)
gpg: waiting for the agent to come up ... (4s)
gpg: waiting for the agent to come up ... (3s)
gpg: waiting for the agent to come up ... (2s)
gpg: waiting for the agent to come up ... (1s)
gpg: can't connect to the gpg-agent: IPC connect call failed
gpg: error getting the KEK: No agent running
gpg: error reading '/srv/pokybuild/yocto-worker/oe-selftest-fedora/build/build-st-2070984/meta-selftest/files/signing/key.secret': No agent running
gpg: import from '/srv/pokybuild/yocto-worker/oe-selftest-fedora/build/build-st-2070984/meta-selftest/files/signing/key.secret' failed: No agent running
gpg: Total number processed: 0
gpg: imported: 1
gpg: secret keys read: 1
https://valkyrie.yoctoproject.org/#/builders/48/builds/464/steps/14/logs/stdio
Can you have a look at this error, please ?
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-11-28 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 23:35 [PATCH 1/4] man-db: upgrade 2.12.1 -> 2.13.0 Hongxu Jia
2024-11-27 23:35 ` [PATCH 2/4] gnupg: upgrade 2.5.0 -> 2.5.1 Hongxu Jia
2024-11-28 9:39 ` [OE-core] " Alexander Kanavin
2024-11-29 11:57 ` hongxu
2024-11-28 15:23 ` Mathieu Dubois-Briand [this message]
2024-11-29 11:57 ` hongxu
2024-11-27 23:35 ` [PATCH 3/4] gpgme: upgrade 1.23.2 -> 1.24.0 Hongxu Jia
2024-11-27 23:36 ` [PATCH 4/4] scocat: upgrade 1.8.0.0 -> 1.8.0.1 Hongxu Jia
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=Z0iK7kmJ1PpkGXJf@bootlin-mathieu \
--to=mathieu.dubois-briand@bootlin.com \
--cc=hongxu.jia@eng.windriver.com \
--cc=openembedded-core@lists.openembedded.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