Aptly publish API (curl) fails because gpg still asks for passphrase even when passing "Passphrase" or "PassphraseFile" #1252
Labels
please confirm resolved
We believe the issue is resolved ! if so, please close the issue, thanks ;-)
Detailed Description
This happens when using gpg2 at least. In regular aptly command line, two options are required:
However there's no way to pass "batch" with REST, so we get an error:
Context
When using the REST API for Publishing for the first time which requires passing the gpp passphrase to unlock the key.
Note that because the key is gpg2 I cannot use the "internal" GPG provider since it looks for the legacy secring/pubring which don't exist in gpg2.
Possible Implementation
Not sure why "batch" is required, even when passing the PassPhraseFile with cmd line, but be that as it may, please provide a "batch" option for REST
Your Environment
Debian bookworm
aptly version: 1.5.0+ds1-1+b4
The text was updated successfully, but these errors were encountered: