Package: signing-party
Version: 2.1-1
Severity: normal

Hello,

store before: since mutt now depends on a newer ligpg* version, I got
gnupg2. And for some reason, gpg-agent is no longer working, I guess
it's caused by gpg2 installation? Anyhow, gpg2 works. With gpg-agent. So
I wanted to continue using caff with gpg2. Therefore, I configured
.caffrc to use gpg2.

What we get now:

$ caff 7C3AB9CFD230BD30DD009C591E7091B1F14A64A2 --debug
[DEBUG] gpg (GnuPG) 2.1
[DEBUG] Creating symlink /home/user/.caff/gnupghome/S.gpg-agent to 
/home/user/.gnupg/S.gpg-agent
[DEBUG] Creating symlink /home/user/.caff/gnupghome/S.dirmngr to 
/home/user/.gnupg/S.dirmngr
[DEBUG] Exporting key(s) 69740E5CB35FEC3C from your normal GnuPGHOME to 
/home/user/.caff/gnupghome
[DEBUG] gpg2 --batch --no-tty --trust-model=always --no-auto-check-trustdb 
--no-autostart ...
[DEBUG] stdin: <&=4, stdout: IO::Handle=GLOB(0x294bfa8)
[DEBUG] gpg2 --batch --no-tty --homedir /home/user/.caff/gnupghome --quiet 
--trust-model=always --no-auto-check-trustdb --no-autostart ...
[DEBUG] status: IO::Handle=GLOB(0x294bd20), stdout: >&=4, stdin: 5
[NOTICE] Fetching keys from pool.sks-keyservers.net, this may take a while...
[DEBUG] gpg2 --batch --no-tty --homedir /home/user/.caff/gnupghome 
--trust-model=always --keyserver=pool.sks-keyservers.net auto-key-retrieve 
--no-auto-check-trustdb --no-autostart ...
[DEBUG] stdin: <&=4, stdout: >&=4, status: IO::Handle=GLOB(0x3d9eb78)
[DEBUG] Imported 7C3AB9CFD230BD30DD009C591E7091B1F14A64A2 for 
7C3AB9CFD230BD30DD009C591E7091B1F14A64A2
gpg: key F14A64A2: "[User ID not found]" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
[DEBUG] gpg2 --batch --no-tty --homedir /home/user/.caff/gnupghome 
--trust-model=always --with-fingerprint --with-colons --no-auto-check-trustdb 
--no-autostart ...
[DEBUG] stdin: <&=4, stdout: IO::Handle=GLOB(0x3ddcad0)
gpg: error reading key: Legacy key
[WARN] gpg2 exited with value 2
[WARN] No public keys found with list-key 
7C3AB9CFD230BD30DD009C591E7091B1F14A64A2 (note that caff uses its own keyring 
in /home/user/.caff/gnupghome)

The solution is removing .caff/gnupghome and let it replace it. This is
either a bug or your docs might point out that it needs to be deleted
after changing gpg version.

Regards,
Eduard.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages signing-party depends on:
ii  gnupg                      1.4.19-5
ii  libc6                      2.19-19
ii  libclass-methodmaker-perl  2.24-1
ii  libgnupg-interface-perl    0.52-2
ii  libmailtools-perl          2.13-1
ii  libmime-tools-perl         5.505-1
ii  libnet-idn-encode-perl     2.202-1
ii  libterm-readkey-perl       2.33-1
ii  libtext-template-perl      1.46-1
ii  perl                       5.20.2-6
ii  python                     2.7.9-1
ii  qprint                     1.1.dfsg.2-2

Versions of packages signing-party recommends:
ii  dialog                                     1.2-20150528-1
ii  exim4-daemon-light [mail-transport-agent]  4.86-3
ii  libgd-perl [libgd-gd2-perl]                2.53-1+b1
ii  libpaper-utils                             1.1.24+nmu4
ii  whiptail                                   0.52.18-1

Versions of packages signing-party suggests:
ii  fonts-droid                1:4.4.4r2-7
ii  imagemagick                8:6.8.9.9-5.1+b1
ii  mutt                       1.5.23-3.1
pn  qrencode                   <none>
ii  texlive-font-utils         2015.20150823-1
ii  texlive-latex-extra        2015.20150823-1
ii  texlive-latex-recommended  2015.20150823-1
pn  texlive-xetex              <none>
pn  wipe                       <none>

-- no debconf information

-- 
<cray> knopper wie ich mitbekommen habe hast du irgendwie etwas mit knoppix zu
        tun, ..

Reply via email to