Closed kakapapa closed 11 months ago
Hello,
gpg-agent
is started during the bootstrap only if THIRD_PARTY_APT_KEYS
or DISTRO_BOOTSTRAP_KEYS
are set and exist.
This will set gnupg
override that should already install gnupg
package by:
DISTRO_BOOTSTRAP_BASE_PACKAGES:append:gnupg = ",gnupg"
And gnupg
depends on gpg-agent
, so no double include needed.
Did you sign your custom repo? Does any of THIRD_PARTY_APT_KEYS
or DISTRO_BOOTSTRAP_KEYS
variables set?
Hi @amikan
Did you sign your custom repo? Does any of THIRD_PARTY_APT_KEYS or DISTRO_BOOTSTRAP_KEYS variables set?
Yes. I made a apt repository with some of deb packages from bookworm repository and I signed the repository. Also I set DISTRO_BOOTSTRAP_KEYS variable.
Setting DISTRO_BOOTSTRAP_KEYS
should be enough to have gnupg
(and gpg-agent
) installed.
What Isar revision are you using (next/master/other)?
Can you provide some minimal steps to reproduce (with sample conf files), so we can reproduce the issue?
BTW we have test_repro_signed test case in our CI (testsuite/citest.py) which used signed repo and proofed to work. You can try to look into differences between settings there.
@amikan Thank you for your reply and found it was my fault. sorry to bother you.
The error was caused by using DISTRO_BOOTSTRAP_KEYFILES
not DISTRO_BOOTSTRAP_KEYS
.
Thanks @kakapapa for your feedback.
I tried to use my own apt repository created from bookworm repository, but it was failed to run gpg-agent.
To solve the problem, I had to install gnupg & gpg-agent packages like following;