Control: tag -1 + moreinfo
Hi Paul,
intrigeri:
>>> - Don't bloat the logs with fingerprints of keys that could not
>>> be found (Closes: #900388). Also, hide spurious
>>> "dirmngr:Network:/usr/bin/dirmngr:1:1:" output.
>> This doesn't seem to have fixed the problem for me after a reboot.
> Ouch, too bad. Reopened.
I'm sorry I have no idea what's going on:
- I cannot reproduce this locally even though I have plenty of keys in my
keyring that are not on the keyservers.
- I've copied one of your sample errors
('gpg: key "0123456789ABCDEF0123456789ABCDEF01234567" not found: Not found'),
passed it through the regexp and it successfully filters it out.
Could you please:
- apply the attached patch
- kill + start parcimonie
- send me the relevant bits of the Journal (ideally, redirecting its
output to a file and signing that file, to ensure the text is not
mangled in transit)
Thanks in advance.
Cheers,
--
intrigeri
diff --git a/lib/App/Parcimonie/Daemon.pm b/lib/App/Parcimonie/Daemon.pm
index 2a5f1b1..918b811 100644
--- a/lib/App/Parcimonie/Daemon.pm
+++ b/lib/App/Parcimonie/Daemon.pm
@@ -363,6 +363,7 @@ sub tryRecvKey {
# gpg: keyserver receive failed: No data
# gpg: key "0123456789ABCDEF0123456789ABCDEF01234567" not found: Not found
# ... followed by " at /path/to/App/Parcimonie/Daemon.pm line 350"
+ warn $self->encoding->encode("before filtering: " . $filtered_gpg_error);
$filtered_gpg_error =~ s{
^gpg:\s+
(?:
@@ -378,7 +379,7 @@ sub tryRecvKey {
)?
[\n]*
}{}xmsg;
- warn $self->encoding->encode($filtered_gpg_error)
+ warn $self->encoding->encode("after filtering: " . $filtered_gpg_error)
if length($filtered_gpg_error);
}
}
