Your message dated Mon, 19 May 2014 20:43:22 -0700 (PDT)
with message-id <[email protected]>
and subject line Re: Bug#412896
has caused the Debian Bug report #412896,
regarding emacs-snapshot: [gnus] GPG signing does not work
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
412896: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412896
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: emacs-snapshot
Version: 1:20070223-1
Severity: important
I am using emacs-snapshot with the built-in Gnus:
$ dpkg -l gnus
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-========================-========================-================================================================
pn gnus <none> (no description available)
When I want to gpg-sign a mail (C-c RET s p), I am asked for the
passphrase as usual, but then I get an error no matter how careful I
type the passphrase. It worked earlier; for sure when I was using
sarge's emacs and gnus, but I'm quite sure it worked also with
emacs-snapshot on sarge.
Now I'm using etch and a newer emacs-snapshot from unstable, and I get
this error:
[GNUPG:] USERID_HINT FB1B3D632252FA1A Frank KÃŒster <[email protected]>
[GNUPG:] NEED_PASSPHRASE FB1B3D632252FA1A FB1B3D632252FA1A 17 0
[GNUPG:] BAD_PASSPHRASE FB1B3D632252FA1A
gpg: skipped "frank": bad passphrase
gpg: signing failed: bad passphrase
This is the backtrace:
Debugger entered--Lisp error: (error "Sign error")
signal(error ("Sign error"))
error("Sign error")
mml2015-pgg-sign((part (sign . "pgpmime") (tag-location . 333) (contents .
"hallo\n-- \nDr. Frank K\xf7cster\nSingle Molecule Spectroscopy, Protein
Folding @ Inst. f. Biochemie, Univ. Z\xf7crich\nDebian Developer
(teTeX/TeXLive)\n")))
mml2015-sign((part (sign . "pgpmime") (tag-location . 333) (contents .
"hallo\n-- \nDr. Frank K\xf7cster\nSingle Molecule Spectroscopy, Protein
Folding @ Inst. f. Biochemie, Univ. Z\xf7crich\nDebian Developer
(teTeX/TeXLive)\n")))
mml-pgpmime-sign-buffer((part (sign . "pgpmime") (tag-location . 333)
(contents . "hallo\n-- \nDr. Frank K\xf7cster\nSingle Molecule Spectroscopy,
Protein Folding @ Inst. f. Biochemie, Univ. Z\xf7crich\nDebian Developer
(teTeX/TeXLive)\n")))
mml-generate-mime-1((part (sign . "pgpmime") (tag-location . 333) (contents .
"hallo\n-- \nDr. Frank K\xf7cster\nSingle Molecule Spectroscopy, Protein
Folding @ Inst. f. Biochemie, Univ. Z\xf7crich\nDebian Developer
(teTeX/TeXLive)\n")))
mml-generate-mime()
message-encode-message-body()
message-send-mail(nil)
message-send-via-mail(nil)
message-send(nil)
message-send-and-exit(nil)
call-interactively(message-send-and-exit)
There are some issues with gpg on the commandline: There's no
problem with something like
$ gpg --clearsign gpgsign.backtrace
You need a passphrase to unlock the secret key for
user: "Frank Küster <[email protected]>"
1024-bit DSA key, ID 2252FA1A, created 2003-04-30
However, debsign has problems recognising me:
$ debsign tex-common_1.0_i386.changes
signfile tex-common_1.0.dsc Frank KÃŒster <[email protected]>
gpg: skipped "Frank KÃÅster <[email protected]>": secret key not available
gpg: [stdin]: clearsign failed: secret key not available
debsign: gpg error occurred! Aborting....
(It works with [email protected]).
Moreover, I also have "unusual" characters in my passphrase, which has
caused errors in the past with some gnus versions.
Any idea what I could do to debug this?
Regards, Frank
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing'), (99, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)
Versions of packages emacs-snapshot depends on:
ii emacs-snapshot-bin-common 1:20070223-1 The GNU Emacs editor's shared, arc
ii libasound2 1.0.13-1 ALSA library
ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries
ii libice6 1:1.0.1-2 X11 Inter-Client Exchange library
ii libjpeg62 6b-13 The Independent JPEG Group's JPEG
ii libncurses5 5.5-5 Shared libraries for terminal hand
ii libpng12-0 1.2.15~beta5-1 PNG library - runtime
ii libsm6 1:1.0.1-3 X11 Session Management library
ii libtiff4 3.8.2-7 Tag Image File Format (TIFF) libra
ii libungif4g 4.1.4-4 shared library for GIF images
ii libx11-6 2:1.0.3-5 X11 client-side library
ii libxmu6 1:1.0.2-2 X11 miscellaneous utility library
ii libxpm4 1:3.5.5-2 X11 pixmap library
ii libxt6 1:1.0.2-2 X11 toolkit intrinsics library
ii xaw3dg 1.5+E-14 Xaw3d widget set
emacs-snapshot recommends no packages.
Versions of packages emacs-snapshot-common depends on:
ii dpkg 1.13.25 package maintenance system for Deb
ii emacsen-common 1.4.17 Common facilities for all emacsen
Versions of packages emacs-snapshot-bin-common depends on:
ii emacs-snapshot-common 1:20070223-1 The GNU Emacs editor's common infr
ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries
ii liblockfile1 1.06.1 NFS-safe locking library, includes
Versions of packages emacs-snapshot-el depends on:
ii emacs-snapshot-common 1:20070223-1 The GNU Emacs editor's common infr
Versions of packages emacsen-common depends on:
ii bsdmainutils 6.1.6 collection of more utilities from
Versions of packages emacs-snapshot is related to:
ii dictionaries-common 0.70.10 Common utilities for spelling dict
-- no debconf information
--
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
--- End Message ---
--- Begin Message ---
Previous messages indicate upstream believes this was fixed some time ago.
If you still see the issue in the current Emacs, 24.3, please reopen
and reassign to emacs24 package.
--- End Message ---
