Summary: | "No key imported" message upon successful import | ||
---|---|---|---|
Product: | [Applications] kgpg | Reporter: | Tristan Miller <psychonaut> |
Component: | general | Assignee: | Rolf Eike Beer <kde> |
Status: | RESOLVED FIXED | ||
Severity: | minor | ||
Priority: | NOR | ||
Version: | 2.17.0 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | https://commits.kde.org/kgpg/4b0b69868513f101c401c04d04c06a30d5a6c713 | Version Fixed In: | 17.08.3 |
Attachments: | Screenshot showing misleading dialog |
Description
Tristan Miller
2016-09-17 14:23:19 UTC
Created attachment 101145 [details]
Screenshot showing misleading dialog
Forgot to mention that I'm using KGpg 2.17.0 on KDE 4.14.18 with GnuPG 2.0.24 and libgcrypt 1.6.1. Git commit 4b0b69868513f101c401c04d04c06a30d5a6c713 by Rolf Eike Beer. Committed on 18/10/2017 at 17:04. Pushed by dakon into branch 'Applications/17.08'. fix message after importing keys The message was telling that no key was imported if the last column of the IMPORT_RES line was 0, which gives the keys that were not imported or the skipped v3 keys depending on the version of GnuPG. Change the logic to what is was meant to show: say nothing was imported if _all_ fields are 0. FIXED-IN:17.08.3 M +6 -9 transactions/kgpgimport.cpp https://commits.kde.org/kgpg/4b0b69868513f101c401c04d04c06a30d5a6c713 |