Your message dated Sat, 9 Jun 2012 12:28:51 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-gnupg-maint] Bug#676698: gnupg: --refresh-keys fails
with HTTP fetch error 28: Previous alarm fired off!
has caused the Debian Bug report #676698,
regarding gnupg: --refresh-keys fails with HTTP fetch error 28: Previous alarm
fired off!
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.)
--
676698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676698
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnupg
Version: 1.4.12-4
Severity: important
Hello Debian GnuPG-Maintainers!
It seems to me that I am experiencing a bug.
Today, the --refresh-keys option suddenly stopped working.
Now I get:
$ gpg --keyserver-options no-honor-keyserver-url \
--import-options repair-pks-subkey-bug \
--refresh-keys $KEYID
gpg: refreshing 1 key from hkp://keys.gnupg.net
gpg: requesting key $KEYID from hkp server keys.gnupg.net
gpgkeys: HTTP fetch error 28: Previous alarm fired off!
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
This bug seems to have appeared as soon as I upgraded my box.
What follows is the list of package upgrades I performed today:
[INSTALL, DEPENDENCIES] libxcb-glx0:amd64
[UPGRADE] debhelper:amd64 9.20120419 -> 9.20120528
[UPGRADE] iceweasel:amd64 10.0.4esr-3 -> 10.0.5esr-1
[UPGRADE] iproute:amd64 20120319-1 -> 20120521-2
[UPGRADE] libbsd0:amd64 0.3.0-2 -> 0.4.0-1
[UPGRADE] libgl1-mesa-dri:amd64 7.11.2-1 -> 8.0.2-2
[UPGRADE] libgl1-mesa-glx:amd64 7.11.2-1 -> 8.0.2-2
[UPGRADE] libglapi-mesa:amd64 7.11.2-1 -> 8.0.2-2
[UPGRADE] libglu1-mesa:amd64 7.11.2-1 -> 8.0.2-2
[UPGRADE] libmowgli2:amd64 0.7.1-1 -> 1.0.0-1
[UPGRADE] libmozjs10d:amd64 10.0.4esr-3 -> 10.0.5esr-1
[UPGRADE] libopenal-data:amd64 1:1.14-3 -> 1:1.14-4
[UPGRADE] libopenal1:amd64 1:1.14-3 -> 1:1.14-4
[UPGRADE] libssh2-1:amd64 1.4.1-1 -> 1.4.2-1
[UPGRADE] mysql-common:amd64 5.5.23+dfsg-2 -> 5.5.24+dfsg-2
[UPGRADE] sgml-base:amd64 1.26+nmu1 -> 1.26+nmu3
[UPGRADE] tcl8.4:amd64 8.4.19-4 -> 8.4.19-5
[UPGRADE] tcl8.5:amd64 8.5.11-1 -> 8.5.11-2
[UPGRADE] xulrunner-10.0:amd64 10.0.4esr-3 -> 10.0.5esr-1
I tried downgrading some of these packages (one at a time: libssh2,
libbsd0, iproute), but I always have been able to reproduce the bug.
I am reporting the bug against package gnupg, since I haven't found
any clear culprit: please help me identifying what's wrong.
Thanks for your time!
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages gnupg depends on:
ii dpkg 1.16.3
ii gpgv 1.4.12-4
ii install-info 4.13a.dfsg.1-10
ii libbz2-1.0 1.0.6-1
ii libc6 2.13-32
ii libreadline6 6.2-8
ii libusb-0.1-4 2:0.1.12-20
ii zlib1g 1:1.2.7.dfsg-11
Versions of packages gnupg recommends:
ii gnupg-curl 1.4.12-4
ii libldap-2.4-2 2.4.28-1.1
Versions of packages gnupg suggests:
pn gnupg-doc <none>
pn imagemagick 8:6.7.4.0-5
pn libpcsclite1 <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sat, June 9, 2012 09:32, Francesco Poli wrote:
> On Fri, 08 Jun 2012 23:44:03 +0200 Francesco Poli (wintermute) wrote:
>
> [...]
>> Hello Debian GnuPG-Maintainers!
>>
>> It seems to me that I am experiencing a bug.
>> Today, the --refresh-keys option suddenly stopped working.
>
> This is really weird: the issue seems to have magically disappeared
> today.
> I haven't done anything special: I just shut the box down, went to
> sleep, then woke up, booted the box and retried to refresh some keys.
> No other package upgrade was performed in the meanwhile.
> Nonetheless, everything seems to work as usual now... 8-|
Because downgrading also didn't work, perhaps a transient problem at the
remote keyserver was at play.
> This bug report may probably be closed, if you agree.
> Sorry for the noise.
No problem.
Thijs
--- End Message ---
