This bug was fixed in the package debsig-verify - 0.13
---
debsig-verify (0.13) unstable; urgency=medium
* Disable all current GnuPG warnings, as these do not concern us, because
we only use gpg for verification purposes, so we should not be handling
sensitive material
** Changed in: debsig-verify (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1355900
Title:
debsig-verify offers no way to specify an alternate keyring
To
** Bug watch added: Debian Bug tracker #758525
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758525
** Also affects: debsig-verify (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758525
Importance: Unknown
Status: Unknown
** Changed in: debsig-verify (Ubuntu)
** Changed in: debsig-verify (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1355900
Title:
debsig-verify offers no way to specify an alternate keyring
To
A new option --home was added to debsig-verify git that should support
what is requested here. You can put
/path/to/alternative/home/etc/debsig/etc/debsig/policies and
.../usr/share/debsig/keyrings there.
** Changed in: debsig-verify (Ubuntu)
Status: Triaged = In Progress
** Changed in:
