severity 725889 grave
severity 726479 important
found 725889 1.4.15-1
quit
On Wed, Oct 09, 2013 at 09:09:02PM +0200, Bill Allombert wrote:
/usr/bin/gpg --batch --no-options --no-default-keyring --trust-model=always
--homedir /tmp/tmp.HC3e3knvrs --keyring
Hi Bill,
On Wed, October 16, 2013 11:19, Bill Allombert wrote:
severity 725889 grave
severity 726479 important
found 725889 1.4.15-1
quit
On Wed, Oct 09, 2013 at 09:09:02PM +0200, Bill Allombert wrote:
/usr/bin/gpg --batch --no-options --no-default-keyring
--trust-model=always --homedir
On Wed, Oct 16, 2013 at 12:09:42PM +0200, Thijs Kinkhorst wrote:
Hi Bill,
There are potentially 12000 systems affected.
Now has I see it, you have two way to fix the problem:
Either apply the patch Werner send (GIT
2528178e7e2fac6454dd988121167305db7c71d9),
or revert the previous
On Wed, October 16, 2013 15:56, Bill Allombert wrote:
On Wed, Oct 16, 2013 at 12:09:42PM +0200, Thijs Kinkhorst wrote:
Hi Bill,
There are potentially 12000 systems affected.
Now has I see it, you have two way to fix the problem:
Either apply the patch Werner send (GIT
On Fri, 11 Oct 2013 20:13, bill.allomb...@math.u-bordeaux1.fr said:
Yes. Sorry to have induced you to add a bug. I was really struggling to
understand how the flags were interacting with each others.
No problem. It actually shows the need for a encryption only tool much
like we use gpgv of
On Wed, 9 Oct 2013 22:59, w...@gnupg.org said:
I'll take care of this tomorrow. The cause for this is very likely
Okay. I completed the other change: It is now possible to use most
commands along with --always-trust without creating or requiring a
trustdb.
On Wed, Oct 09, 2013 at 10:59:05PM +0200, Werner Koch wrote:
On Wed, 9 Oct 2013 21:09, bill.allomb...@math.u-bordeaux1.fr said:
Actually this is the gnupg upgrade which cause this issue.
I'll take care of this tomorrow. The cause for this is very likely
a1a59e6 * gpg: No need to
On Wed, Oct 09, 2013 at 11:30:17AM -0600, Bob Proulx wrote:
Package: popularity-contest
Version: 1.60
Severity: normal
After the daily upgrade yesterday popularity-contest's cron task now
reports:
# /etc/cron.daily/popularity-contest
gpg: fatal: can't open
On Wed, 9 Oct 2013 21:09, bill.allomb...@math.u-bordeaux1.fr said:
Actually this is the gnupg upgrade which cause this issue.
I'll take care of this tomorrow. The cause for this is very likely
a1a59e6 * gpg: No need to create a trustdb when encrypting with --always-trust.
IIRC, I did this
9 matches
Mail list logo
