[Popcon-developers] Bug#725889: regression: gpg: fatal: can't open trustdb.gpg: No such file or directory

[Bob Proulx]

reassign 725889 gnupg
affects 725889 + popularity-contest
thanks

Bill Allombert wrote:
> Bob Proulx wrote:
> > Downgrading to version 1.59 does not produce the output.
> 
> Actually this is the gnupg upgrade which cause this issue.

Confirmed.  It was only the unfortunate timing of the change to popcon
that it enabled encryption on the same day.  If it had enabled
encryption last week and then gnupg only upgraded today then this
would have indicated otherwise.  Reassigning to gnupg and marking as
affecting popularity-contest.  It is likely this change will affect
more packages.

> With gpg 1.4.15-1, this leads to an error. It works fine with gpg 1.4.14-1
> ...
> How to reproduce: 
> - install popularity-contest 
> 
> - change the variable DAY in /etc/cron.daily/popularity-contest to match the
>   current day number (sunday 0, monday 1, etc)
> 
> - run /etc/cron.daily/popularity-contest

Perhaps a very slightly simpler reproducer of the problem.  No $DAY
config file modifications needed.  Uses a key that every Debian
machine is likely to have.  Won't try to submit data to popcon.  Not
dependent upon popcon at all.  Just a self contained local test.

  rm -f /tmp/testdata.gpg
  echo foo > /tmp/testdata
  mkdir /tmp/gpgtesthome
  chmod go-rwx /tmp/gpgtesthome
  gpg --quiet --batch --armor --no-options --no-default-keyring --trust-model=always --homedir /tmp/gpgtesthome --keyring /usr/share/keyrings/debian-keyring.gpg --recipient E1C21845 --output /tmp/testdata.asc --encrypt /tmp/testdata

Version 1.4.14-1 is quiet.  Version 1.4.15-1 emits:

  gpg: fatal: can't open `/tmp/gpgtesthome/trustdb.gpg': No such file or directory
  secmem usage: 1408/1408 bytes in 2/2 blocks of pool 1408/32768

And of course any gpg keyring and recipient key could be substituted
to make this a simpler reproducer and independent of Debian.

Thanks,
Bob