From falko.strenzke at mtg.de  Wed Oct 11 13:34:50 2023
From: falko.strenzke at mtg.de (Falko Strenzke)
Date: Wed, 11 Oct 2023 13:34:50 +0200
Subject: =?UTF-8?Q?Building_GnuPG_=E2=80=93_libassuan_version?=
Message-ID: <822b2396-bc79-435c-afce-cf5f8159b09b@mtg.de>

I just tried to build the current master branch of 
https://dev.gnupg.org/source/gnupg.git

When trying to build it, I receive the error

*** You need libassuan to build this program.
*** This library is for example available at
*** https://gnupg.org/ftp/gcrypt/libassuan/
*** (at least version 3.0.0 (API 3) is required).


This is my configure command:

./configure --prefix=/opt/gnupg-2.4.3 --sysconfdir=/opt/gnupg-2.4.3/etc 
--with-libgcrypt-prefix=/opt/libgcrypt 
--with-libgpg-error-prefix=/opt/libgpg-error 
--with-npth-prefix=/opt/npth --with-libassuan-prefix=/opt/libassuan3.0-base

I built libassuan 3.0-base from the tag 
https://github.com/gpg/libassuan/tree/libassuan-3.0-base and installed 
it at the dir shown above. However, I see that even 
https://github.com/gpg/libassuan/tree/libassuan-3.0-base is identifying 
itself as version "2.5.6-beta1" via its config binary. So I wonder how I 
can have working version of libassuan for current GnuPG master.

- Falko

-- 

*MTG AG*
Dr. Falko Strenzke
Executive System Architect

Phone: +49 6151 8000 24
E-Mail: falko.strenzke at mtg.de
Web: mtg.de <https://www.mtg.de>


------------------------------------------------------------------------

MTG AG - Dolivostr. 11 - 64293 Darmstadt, Germany
Commercial register: HRB 8901
Register Court: Amtsgericht Darmstadt
Management Board: J?rgen Ruf (CEO), Tamer Kemer?z
Chairman of the Supervisory Board: Dr. Thomas Milde

This email may contain confidential and/or privileged information. If 
you are not the correct recipient or have received this email in error,
please inform the sender immediately and delete this email. Unauthorised 
copying or distribution of this email is not permitted.

Data protection information: Privacy policy 
<https://www.mtg.de/en/privacy-policy>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20231011/bf5d2ea4/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4813 bytes
Desc: Kryptografische S/MIME-Signatur
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20231011/bf5d2ea4/attachment-0001.bin>

From jasoncarrete5 at gmail.com  Sun Oct 29 07:12:50 2023
From: jasoncarrete5 at gmail.com (Jason Carrete)
Date: Sun, 29 Oct 2023 02:12:50 -0400
Subject: Jason Carrete DCO
Message-ID: <2e0cf1ef-76dd-4035-9ff9-2e872a8a766c@gmail.com>

GnuPG Developer's Certificate of Origin. Version 1.0
=====================================================

By making a contribution to the GnuPG project, I certify that:

(a) The contribution was created in whole or in part by me and I
have the right to submit it under the free software license
indicated in the file; or

(b) The contribution is based upon previous work that, to the
best of my knowledge, is covered under an appropriate free
software license and I have the right under that license to
submit that work with modifications, whether created in whole
or in part by me, under the same free software license
(unless I am permitted to submit under a different license),
as indicated in the file; or

(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.

(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including
all personal information I submit with it, including my
sign-off) is maintained indefinitely and may be redistributed
consistent with this project or the free software license(s)
involved.

Signed-off-by: Jason Carrete <jasoncarrete5 at gmail.com>

My PGP key can be found at https://jasonrc.com/keys/jasonc.asc or 
https://keys.openpgp.org/vks/v1/by-fingerprint/221971E5C5BAA7B3251FCD1DC90EAC363644139A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: OpenPGP digital signature
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20231029/cb8ac2b1/attachment.sig>

From dan.git at brilhante.top  Tue Oct 31 22:26:39 2023
From: dan.git at brilhante.top (Daniel Cerqueira)
Date: Tue, 31 Oct 2023 21:26:39 +0000
Subject: Portuguese po translation
Message-ID: <87ttq6jxf4.fsf@brilhante.top>

Hi all. Happy Halloween!

I am doing the translation of GnuPG into European Portuguese.

I have some questions:

1. There are a lot of branches version. The GnuPG of my package manager
is following the 2.2.x version's. But the current version on gnupg.org
is 2.4.x . There are also 2.5-base and 2.6-base. My question is: which
git branch should I use for my translation?

2. When done, to where do I send the git patch?

3. Last time I sent a git patch to an address, my email provider blocked
me sending the email, because my email provider flagged it as suspicious
of being SPAM. I probably will have to send the patch on a tar archive,
or send the patch as an OpenPGP encrypted email. Is this ok? Which of
the two options is best? (first, I will try to send it unencrypted)

Hope you are all good and are safe. Thank you for making GnuPG.