Re: Problems building gpgmepy 2.0 against gnupg 2.5.20

--===============4848199732212598573==
Content-Type: multipart/signed; boundary="nextPart2742235.Ke5KMYTlT1";
 micalg="pgp-sha512"; protocol="application/pgp-signature"

--nextPart2742235.Ke5KMYTlT1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; protected-headers="v1"
From: Meik Michalke <[email protected]>
To: [email protected]
Subject: Re: Problems building gpgmepy 2.0 against gnupg 2.5.20
Date: Wed, 20 May 2026 09:54:19 +0200
Message-ID: <6594772.QpXv3AuLzZ@kasidy>
In-Reply-To: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0

hi funda,

Am Mittwoch, 20. Mai 2026, 07:14:18 CEST schrieb Funda Wang via Gnupg-devel:
> 07:22:46 ValueError: Expected buffer of length 149, got 128

you need to increase the buffer size, see this patch we use in our debian=20
packages:

https://github.com/gpgdeb/gpgmepy/blob/gnupg/stable/debian/patches/0030-inc=
rease-buffer-of-python-test.patch


viele gr=FC=DFe :: m.eik
--nextPart2742235.Ke5KMYTlT1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iJEEABYKADkWIQRs7BjQbc011HqitSUz/RvPXledgwUCag1oqxsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMiwyLDIACgkQM/0bz15XnYOH6wD9FuAqjMHEK/JHiC2S0vEV
K3U3RLZxb1ZKOWT9TqEph9EA/RS0qwHEk+pIrucTkvWh+oqKw0KOTB5z/SgSXd3N
zn4O
=wdnt
-----END PGP SIGNATURE-----

--nextPart2742235.Ke5KMYTlT1--






--===============4848199732212598573==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Gnupg-devel mailing list
[email protected]
https://lists.gnupg.org/mailman/listinfo/gnupg-devel

--===============4848199732212598573==--