FS#29122 - [kdepim-kleopatra] needs gnupg to be gnupg 2 (from testing)

Attached to Project: Arch Linux
Opened by Johannes Dewender (JonnyJD) - Monday, 26 March 2012, 14:40 GMT
Last edited by Andrea Scarpino (BaSh) - Monday, 26 March 2012, 17:20 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
for example refreshing PGP-keys uses /usr/sbin/gpg and fails
$ gpg2 --refresh-keys
gpg: /home/jonnyjd/.gnupg/gpg.conf:8: argument not expected
gpg: /home/jonnyjd/.gnupg/gpg.conf:9: invalid option

The result:
Kmail and Co. don't find my gpg keys anymore and I am not able to sign and encrypt, but more importantly: I can't decrypt or check signatures either.

$ gpg2 --refresh-keys
works fine.

I noticed that gpg in core is 1.4, while gpg in testing is 2.0.


So the basic problem is (again):
kdepim-kleopatra in extra is built against testing.




Additional info:
* package version(s)
extra/kdepim-kleopatra 4.8.1-3
core/gnupg 1.4.12-1
core/gnupg2 2.0.18-1

Testing gnupg 2.0.18-2 (not installed at my end)
I am using 64bit Arch, but this doesn't seem to be relevant. 32 bit gnupg is also 1.4 in core.

* config and/or log files etc.


Steps to reproduce:
open kleopatra
-> Extras -> refresh OpenPGP
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Monday, 26 March 2012, 17:20 GMT
Reason for closing:  Not a bug
Additional comments about closing:  see comments
Comment by Johannes Dewender (JonnyJD) - Monday, 26 March 2012, 14:57 GMT
my gpg.conf has at lines 7 to 9:
7 use-agent
8 debug-level basic
9 log-file socket:///home/jonnyjd/.gnupg/log-socket

Yes, removing line 8 and 9 is a workaround.
However, the point is, that gpg 2 is expected as /usr/bin/gpg.

I just started using kleopatra again after months and just installed it. I can't say for how long this problem exists.
Comment by Johannes Dewender (JonnyJD) - Monday, 26 March 2012, 15:35 GMT
Thinking this over: I am not really certain kleopatra did use gpg2 ever. I have my gpg.conf already for a long time and I also did use kleopatra before. However, I am not sure if this exact config ever ran with kleopatra. It did work for signing mails/git tags ..., decrypting files, encrypting files, but maybe all of that without kleopatra.

It's just that it stopped working as soon as I installed the current kleopatra.

So maybe gnupg beeing in testing as 2.0 is just coincidence. In this case, it isn't really not that urgent..
Comment by Gaetan Bisson (vesath) - Monday, 26 March 2012, 15:41 GMT
I have no clue what you are talking about. Could you try to sum up your problems clearly in one line or two?
Comment by Johannes Dewender (JonnyJD) - Monday, 26 March 2012, 15:53 GMT
Steps to reproduce:
open kleopatra
-> Extras -> refresh OpenPGP

This fails because it won't accept my gpg2 gpg.conf, because kleopatra uses /usr/bin/gpg, which is version 1.4 in core, but 2.0 in testing.
Comment by Gaetan Bisson (vesath) - Monday, 26 March 2012, 16:17 GMT
kdepim-kleopatra was built before I put gnupg-2.0.18 in [testing]. So what is the problem here?
Comment by Johannes Dewender (JonnyJD) - Monday, 26 March 2012, 16:40 GMT
Oh, okay. Then my proposed fix for kleopatra would have been to use gpg2, rather than gpg, but since both will be the same soon, I just have to cope with kleopatra using gpg version 1 for now.

I suspected a small building error, not that kleopatra (in kde 4.8) was still using gpg version 1 in general.

Thanks for your quick answer and sorry for any inconvenience.

This can be closed then.

Loading...