Re: [Pyme-help] Re: PyME: Segmentation Faults

[Robin B. <Ro...@fr...>]

Hello!

On Do, 2005-04-21 at 09:09 -0400, Igor Belyi wrote:
> My guess is that you either run into incompatibility between the versio=
n=20
> of GPGME PyMe was compiled with and the GPGME you are using at run-time=
=20
> or between GPGME and different version of GnuPG.
>=20
> PyMe 0.6.2 was compiled with GPGME 1.0.2 which comes from GnuPG 1.4.0=20
> but is supposed to be compatible upwards. I've run my tests so far only=
=20
> with libgpgme11 and gnupg as come prepackaged in unstable distribution=20
> of Debian.
>=20
We tried several other setups during the last days and got the following
results. We used the "signverify.py" example from the pyme-0.6.2-tarball
as a reference. We didn't change anything but the "user" variable at the
top of the script to an existing user in the keyring.

#1: ibook g4, ubuntu 5.04 stable.
  I tried the prepackaged gpg, libgpgme, swig packages and built a pyme
package from the tarball. Everything works as expected. Especially
"result.signatures.summary" is !=3D zero for a valid signature.
#2: p4 laptop, debian unstable:
  Everything from the distribution, pyme debian package from the
sourceforge-website. "result.signatures.summary" is always 0, even for a
valid signature.
#3: p3, debian testing:
  see #2.

We tried to rebuild everything from source (gpg 1.4.1, gpgme 1.0.2, pyme
0.6.2 and from cvs) on systems #1 and #2 but it didn't change a thing.
System #1 was always giving the right answers, the others didn't. We
even tried different swig-version but it still didn't improve the
situation. Do you have an idea what to try next? What kind of system do
you use?

Best regards,
Robin
--=20
Robin Brandt

freiheit.com technologies gmbh
Stra=C3=9Fenbahnring 22 / 20251 Hamburg, Germany
fon       +49 (0)40 / 890584-0
fax       +49 (0)40 / 890584-20

7150 C3F9 F126 9BDE 5526  95D2 3C6D 40C9 BE2F 0AF6

B=C3=BCcher kaufen und Freie Software f=C3=B6rdern | http://bookzilla.de/