KDE 3.3 /SuSE 8.2 and Signing emails
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I upgraded to kde 3.3 yesterday in my production system SuSE 8.2. (using apt, and using --reinstall flag). All gone well. It looks very nice. Thanks KDE team!. The only problem I got is that I couln't sign my mail with kmail anymore. I spent some hours trying to solve the problem without success. Finally, I guess it could be the gpg code (it had 1.2.2-rc1). I backported the SuSE 9.1 rpm file (with version 1.2.4) and after few fixes it runned and installed OK. Then the kmail problem signing email is SOLVED !!!. Any other 8.2 user has suffered the same problem with GPG when upgrading to KDE 3.3?. I'm not sure about it is a general problem. If the answer is yes then I will release the backported gpg rpm to my 8.2 repository (suser-gbv). Guillermo - -- Guillermo Ballester Valor gbv@oxixares.com Ogijares, Granada SPAIN Linux user #117181. See http://counter.li.org/ Public GPG KEY http://www.oxixares.com/~gbv/pubgpg.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBKvsSOA2UfsyErNQRAo7PAJ9lQZ8hfnB7zE9b3Xg8vATj65KWNgCfeE9i ewwhZ4TVQwDxjlygRAF3a7s= =IAzp -----END PGP SIGNATURE-----
Hi
I upgraded to kde 3.3 yesterday in my production system SuSE 8.2. (using apt, and using --reinstall flag). All gone well. It looks very nice. Thanks KDE team!.
I'm afraid I don't have any info on this, but was curious why you used apt for upgrading rather than rpms (or even compiling from source)? I have 8.2 on a couple of machines. Thanks, Steve
On Thursday 02 September 2004 10:04, Steve Dowe - Cubus wrote:
curious why you used apt for upgrading rather than rpms
In this respect, apt is a front-end for rpm? . . . apt will install, by checking the dependencies, downloading all that's necessary, and, finally executing rpm -Uvh * -- best wishes ____________ sent on Linux ____________
participants (3)
-
Guillermo Ballester Valor -
pinto -
Steve Dowe - Cubus