From tachalorah at proton.me  Mon Aug  3 08:38:14 2026
From: tachalorah at proton.me (tachalorah at proton.me)
Date: Mon, 03 Aug 2026 06:38:14 +0000
Subject: [PATCH gpgmepp] add missing header
Message-ID: <jvnHJKSzyAv0gA_s5fIH6uBqdSR-3TbTBQtzx--t2uEJSpVLcpy7vXRdfrdwoLkCj7zXgndZrkQEY61xT2Sol8OnW1IxJ9R_Q2EvAHQqFmo=@proton.me>


* src/util: add missing <iterator> for std::back_inserter

Fixes missing std::back_inserter when building with clang++
-D_LIBCPP_REMOVE_TRANSITIVE_INCLUDES.
---
 src/util.cpp | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/util.cpp b/src/util.cpp
index 6cbc9ba..77fac5b 100644
--- a/src/util.cpp
+++ b/src/util.cpp
@@ -28,6 +28,7 @@
 #include "util.h"

 #include <functional>
+#include <iterator>

 #include <cstring>

--
2.54.0


From kloecker at kde.org  Mon Aug  3 17:08:37 2026
From: kloecker at kde.org (Ingo =?UTF-8?B?S2zDtmNrZXI=?=)
Date: Mon, 03 Aug 2026 17:08:37 +0200
Subject: [PATCH gpgmepp] add missing header
In-Reply-To: <jvnHJKSzyAv0gA_s5fIH6uBqdSR-3TbTBQtzx--t2uEJSpVLcpy7vXRdfrdwoLkCj7zXgndZrkQEY61xT2Sol8OnW1IxJ9R_Q2EvAHQqFmo=@proton.me>
References: <jvnHJKSzyAv0gA_s5fIH6uBqdSR-3TbTBQtzx--t2uEJSpVLcpy7vXRdfrdwoLkCj7zXgndZrkQEY61xT2Sol8OnW1IxJ9R_Q2EvAHQqFmo=@proton.me>
Message-ID: <PWIUcoBhR_6HGNU2jMdSQg@kde.org>

On Montag, 3. August 2026 08:38:14 Mitteleurop?ische Sommerzeit tachalorah via 
Gnupg-devel wrote:
> * src/util: add missing <iterator> for std::back_inserter
> 
> Fixes missing std::back_inserter when building with clang++
> -D_LIBCPP_REMOVE_TRANSITIVE_INCLUDES.

Thanks!

Shall I use your proton.me address as commit author? I'm asking because 
mailman rewrote the From header that `git am` uses as commit author and 
there's a small possibility that you used different From and Reply-to 
addresses.

Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 265 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260803/53574876/attachment-0001.sig>

From tachalorah at proton.me  Mon Aug  3 18:00:06 2026
From: tachalorah at proton.me (tachalorah at proton.me)
Date: Mon, 03 Aug 2026 16:00:06 +0000
Subject: [PATCH gpgmepp] add missing header
In-Reply-To: <PWIUcoBhR_6HGNU2jMdSQg@kde.org>
References: <jvnHJKSzyAv0gA_s5fIH6uBqdSR-3TbTBQtzx--t2uEJSpVLcpy7vXRdfrdwoLkCj7zXgndZrkQEY61xT2Sol8OnW1IxJ9R_Q2EvAHQqFmo=@proton.me>
 <PWIUcoBhR_6HGNU2jMdSQg@kde.org>
Message-ID: <a22dPA8u2wBOI_vu9enPt1sKsRi6NUBt9e9R8K0MIOqtVbwP6nOhs_tuJsA5h8hSRn5kkDAMC18dEKBWSx5bRxibjHm1PmQ1eHzIiErEnls=@proton.me>

Hi,

Feel free to use my proton.me address.

On Monday, August 3rd, 2026 at 10:08 PM, Ingo Kl?cker <kloecker at kde.org> wrote:

> On Montag, 3. August 2026 08:38:14 Mitteleurop?ische Sommerzeit tachalorah via 
> Gnupg-devel wrote:
> > * src/util: add missing <iterator> for std::back_inserter
> > 
> > Fixes missing std::back_inserter when building with clang++
> > -D_LIBCPP_REMOVE_TRANSITIVE_INCLUDES.
> 
> Thanks!
> 
> Shall I use your proton.me address as commit author? I'm asking because 
> mailman rewrote the From header that `git am` uses as commit author and 
> there's a small possibility that you used different From and Reply-to 
> addresses.
> 
> Regards,
> Ingo


From wk at gnupg.org  Wed Aug  5 14:30:17 2026
From: wk at gnupg.org (Werner Koch)
Date: Wed, 05 Aug 2026 14:30:17 +0200
Subject: [Announce] GnuPG bug tracker not available due to heavy DDoS
Message-ID: <875x1o3g2u.fsf@jacob.g10code.de>

Hi,

our admin asked me to post this on the status of dev.gnupg.org:

The GnuPG project has been facing increasing AI scraper attacks for
more than a year, but now the situation switched to SYN flood attacks.
We are dealing with the situation, but for the moment our development
server with the bugtracker is not available to the public world.

We are working on a solution which keeps the community involved in
contributing to the project, but for the moment inconvenience cannot
be avoided.

We regret to be forced acting this way, but the AI driven attacks don't
leave much of a choice.


Shalom-Salam,

   Werner


-- 
The pioneers of a warless world are the youth that
refuse military service.             - A. Einstein
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openpgp-digital-signature.asc
Type: application/pgp-signature
Size: 284 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260805/161a51ff/attachment.sig>
-------------- next part --------------
_______________________________________________
Gnupg-announce mailing list
Gnupg-announce at gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-announce

From artem at bigdan.in  Thu Aug  6 19:48:37 2026
From: artem at bigdan.in (Artemii Bigdan)
Date: Thu, 6 Aug 2026 19:48:37 +0200
Subject: [PATCH gnupg] scd: Add Nitrokey 3 to pcsc-shared interference
 detection
In-Reply-To: <87jyqmi64z.fsf@haruna.fsij.org>
References: <84855138-a7c5-494e-8629-1c83727f9d53@bigdan.in>
 <87mrwnnqpe.fsf@haruna.fsij.org>
 <c7d1e251-e884-4a72-b755-6c1c37b6cf83@bigdan.in>
 <87y0fweje2.fsf@haruna.fsij.org>
 <f4525d75-2f88-4519-ba9c-1633965d8740@bigdan.in>
 <874iij35ve.fsf@haruna.fsij.org> <87jyqmi64z.fsf@haruna.fsij.org>
Message-ID: <c96cf9a6-30d7-401e-a7d1-fcd1864416ff@bigdan.in>

Hello,

(1) As far as I'm concerned, any solution is acceptable. I am not a GPG 
maintainer, so I don't have an opinion on whether or not we should 
remove the CARDTYPE_YUBIKEY condition.
If you recall, when I suggested my patch, I conservatively created a new 
CARDTYPE_NK3 so that these changes do not affect YubiKey.
Unfortunately I can't tell you if removing this condition will break 
stuff and I do not have a YubiKey to check.

(2) It's a shame that emulation diverges from the real thing. Maybe we 
should just share a physical Nitrokey stick over USB/IP? Of course, I 
can't use my personal key for obvious security reasons, but maybe Robin 
could host it? That way Nitrokey won't sacrifice a device and won't pay 
for shipping, as I suggested earlier with an R&D device. That seems much 
more wise than my initial suggestion :)

Worst-case scenario - I can buy a second Nitrokey and host it, although 
they are not exactly cheap.

Hope that clarifies,

- Artemii

On 23.07.2026 8:15, NIIBE Yutaka wrote:
> Hello,
>
> For merging your work, I think that there are two things:
>
> (1) PC/SC shared option and change of maybe_switch_app
>
> IIUC, you suggest to modify the maybe_switch_app function so that it can
> call fnc.reselect method when PC/SC shared is enabled and device is
> Yubikey/Nitrokey.
>
> (2) Nitrokey specific things
>
> That is: detecting Nitrokey and scdaemon's behavior tweaks when it's
> Nitrokey.
>
>
> For (1), let me confirm with no consideration of Nitrokey, firstly.
> The changes are like following.
>
> ==========================
> diff --git a/scd/app.c b/scd/app.c
> index 63eb84190..6f74e8c42 100644
> --- a/scd/app.c
> +++ b/scd/app.c
> @@ -1792,12 +1792,15 @@ maybe_switch_app (ctrl_t ctrl, card_t card, const char *keyref)
>     if (!card->app)
>       return gpg_error (GPG_ERR_CARD_NOT_INITIALIZED);
>   
> -  if (card->maybe_check_aid && card->app->fnc.reselect
> +  if ((card->maybe_check_aid
> +       || (opt.pcsc_shared && card->cardtype == CARDTYPE_YUBIKEY))
> +      && card->app->fnc.reselect
>         && check_external_interference (card->app, ctrl))
>       {
>         if (DBG_APP)
> -        log_debug ("slot %d, app %s: forced re-select due to direct APDU use\n",
> -                   card->slot, xstrapptype (card->app));
> +        log_debug ("slot %d, app %s: forced re-select due to %s\n",
> +                   card->slot, xstrapptype (card->app),
> +                   card->maybe_check_aid? "direct APDU use" : "pcsc-shared");
>         err = card->app->fnc.reselect (card->app, ctrl);
>         if (err)
>           log_error ("slot %d, app %s: forced re-select failed: %s - ignored\n",
> ==========================
>
> I wonder if the condition
>
> 	card->cardtype == CARDTYPE_YUBIKEY
>
> is really needed or not.  If it's not strictly required, I'd prefer to
> change without this condition.  (Or else, we will need to add Nitrokey
> condition here.)
>
> If it is OK with no-cardtype condition, I will push the change firstly.
> Then, focus on (2).
>
>
> I struggle with (2), using USBIP emulation (found it's not exact
> emulation, at least ATR is different).  Tentative work is in
> https://dev.gnupg.org/T8331


From robin at nitrokey.com  Thu Aug  6 21:37:52 2026
From: robin at nitrokey.com (Robin Krahl)
Date: Thu, 6 Aug 2026 21:37:52 +0200
Subject: [PATCH gnupg] scd: Add Nitrokey 3 to pcsc-shared interference
 detection
In-Reply-To: <c96cf9a6-30d7-401e-a7d1-fcd1864416ff@bigdan.in>
References: <84855138-a7c5-494e-8629-1c83727f9d53@bigdan.in>
 <87mrwnnqpe.fsf@haruna.fsij.org>
 <c7d1e251-e884-4a72-b755-6c1c37b6cf83@bigdan.in>
 <87y0fweje2.fsf@haruna.fsij.org>
 <f4525d75-2f88-4519-ba9c-1633965d8740@bigdan.in>
 <874iij35ve.fsf@haruna.fsij.org> <87jyqmi64z.fsf@haruna.fsij.org>
 <c96cf9a6-30d7-401e-a7d1-fcd1864416ff@bigdan.in>
Message-ID: <anTg04kETOoVZZ_b@nitropc>

>(2) It's a shame that emulation diverges from the real thing. Maybe we 
>should just share a physical Nitrokey stick over USB/IP? Of course, I 
>can't use my personal key for obvious security reasons, but maybe 
>Robin could host it?

I?ll check if we can do that. 
But I?m not sure if that really makes sense because you would never be able to power-cycle the device.  
Anyway, the offer to provide a Nitrokey still stands.  
I think this would also be a much easier solution than usbip.

Best,
Robin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260806/be7e1b25/attachment.sig>

From fundawang at yeah.net  Fri Aug  7 17:06:00 2026
From: fundawang at yeah.net (Funda Wang)
Date: Fri, 7 Aug 2026 23:06:00 +0800 (CST)
Subject: [gpgmepy] swig 4.5 removes python2 support
Message-ID: <5824192e.1704.19fdcc27966.Coremail.fundawang@yeah.net>

Hi,

As swig 4.5 has removed python 2.x support, gpgmepy failed to test:

2026-08-07 12:19:17 make  all-am
2026-08-07 12:19:17 make[1]: Entering directory '/home/lkp/rpmbuild/BUILD/gpgmepy-2.0.0/tests'
2026-08-07 12:19:17 make[1]: Nothing to be done for 'all-am'.
2026-08-07 12:19:17 make[1]: Leaving directory '/home/lkp/rpmbuild/BUILD/gpgmepy-2.0.0/tests'
2026-08-07 12:19:17 GNUPGHOME=/home/lkp/rpmbuild/BUILD/gpgmepy-2.0.0/tests LC_ALL=C GPG_AGENT_INFO= top_srcdir=.. srcdir=. /usr/bin/python3.11 ./run-tests.py \
2026-08-07 12:19:17   --interpreters="/usr/bin/python3" --srcdir=. --python-libdir=/home/lkp/rpmbuild/BUILDROOT/python-gpgme-2.0.0-3.oe1.aarch64/usr/lib64/python3.11/site-packages \
2026-08-07 12:19:17   initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py t-edit.py t-keylist.py t-keylist-from-data.py t-wait.py t-encrypt-large.py t-file-name.py t-idiomatic.py t-protocol-assuan.py t-quick-key-creation.py t-quick-subkey-creation.py t-quick-key-manipulation.py t-quick-key-signing.py final.py
2026-08-07 12:19:17 Traceback (most recent call last):
2026-08-07 12:19:17   File "/home/lkp/rpmbuild/BUILD/gpgmepy-2.0.0/tests/./initial.py", line 24, in <module>
2026-08-07 12:19:17     import gpg
2026-08-07 12:19:17   File "/home/lkp/rpmbuild/BUILDROOT/python-gpgme-2.0.0-3.oe1.aarch64/usr/lib64/python3.11/site-packages/gpg/__init__.py", line 123, in <module>
2026-08-07 12:19:17     from . import core
2026-08-07 12:19:17   File "/home/lkp/rpmbuild/BUILDROOT/python-gpgme-2.0.0-3.oe1.aarch64/usr/lib64/python3.11/site-packages/gpg/core.py", line 10, in <module>
2026-08-07 12:19:17     from . import gpgme
2026-08-07 12:19:17   File "/home/lkp/rpmbuild/BUILDROOT/python-gpgme-2.0.0-3.oe1.aarch64/usr/lib64/python3.11/site-packages/gpg/gpgme.py", line 10, in <module>
2026-08-07 12:19:17     from . import _gpgme
2026-08-07 12:19:17 ImportError: /home/lkp/rpmbuild/BUILDROOT/python-gpgme-2.0.0-3.oe1.aarch64/usr/lib64/python3.11/site-packages/gpg/_gpgme.cpython-311-aarch64-linux-gnu.so: undefined symbol: PyInt_AsLong

This is caused by all the references to PY_MAJOR_VERSION be removed also. swig 4.5 only support generating code for python >= 3.5 now.

May we should just remove all PY_MAJOR_VERSION in gpgme.i Any comments?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260807/04645af1/attachment.html>

From fundawang at yeah.net  Fri Aug  7 17:47:23 2026
From: fundawang at yeah.net (Funda Wang)
Date: Fri, 7 Aug 2026 23:47:23 +0800 (CST)
Subject: [gpgmepy] swig 4.5 removes python2 support
In-Reply-To: <5824192e.1704.19fdcc27966.Coremail.fundawang@yeah.net>
References: <5824192e.1704.19fdcc27966.Coremail.fundawang@yeah.net>
Message-ID: <66f986e.1746.19fdce85e50.Coremail.fundawang@yeah.net>



I've proposed a patch. Hope it works correctly, especially for PyString_Check. I don't know it should be Bytes or Unicode
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260807/7c1afc55/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gpgme-port-to-python3-only-codebase.patch
Type: application/octet-stream
Size: 1700 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260807/7c1afc55/attachment-0001.obj>

From koray.fra at gmail.com  Sat Aug  8 00:11:35 2026
From: koray.fra at gmail.com (koraynilay)
Date: Sat,  8 Aug 2026 00:11:35 +0200
Subject: [PATCH gnupg 0/3] Fix and improve Italian translation
Message-ID: <20260807221143.1412863-1-koray.fra@gmail.com>

Some patches that improve the Italian translation and fix some problems
I noticed in the algorithm selection of --full-generate-key.

koraynilay (3):
  po: Fix algorithm names in Italian translation
  po: Improve Italian translation
  po: Fix fuzzy Italian translations

 po/it.po | 267 +++++++++++++++++++------------------------------------
 1 file changed, 93 insertions(+), 174 deletions(-)


base-commit: 386c3e63b1cac7f506f974715dbf30c6d40663dd
-- 
2.55.0



From koray.fra at gmail.com  Sat Aug  8 00:11:36 2026
From: koray.fra at gmail.com (koraynilay)
Date: Sat,  8 Aug 2026 00:11:36 +0200
Subject: [PATCH gnupg 1/3] po: Fix algorithm names in Italian translation
In-Reply-To: <20260807221143.1412863-1-koray.fra@gmail.com>
References: <20260807221143.1412863-1-koray.fra@gmail.com>
Message-ID: <20260807221143.1412863-2-koray.fra@gmail.com>

Fix wrong algorithm names in the Italian translation,
especially noticeable in the --full-generate-key menu.

Signed-off-by: koraynilay <koray.fra at gmail.com>
---
 po/it.po | 16 +++++++---------
 1 file changed, 7 insertions(+), 9 deletions(-)

diff --git a/po/it.po b/po/it.po
index 0e33890c7..08aa1cabc 100644
--- a/po/it.po
+++ b/po/it.po
@@ -5,7 +5,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: GNU gnupg 2.3.0\n"
 "Report-Msgid-Bugs-To: translations at gnupg.org\n"
-"PO-Revision-Date: 2021-04-15 10:09+0900\n"
+"PO-Revision-Date: 2026-08-07 23:13+0200\n"
 "Last-Translator: Denis <student at alice.it>\n"
 "Language-Team: \n"
 "Language: it_IT\n"
@@ -13,7 +13,7 @@ msgstr ""
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 "Plural-Forms: nplurals=2; plural=(n != 1);\n"
-"X-Generator: Poedit 2.4.2\n"
+"X-Generator: po.vim\n"
 
 #, c-format
 msgid "failed to acquire the pinentry lock: %s\n"
@@ -4275,7 +4275,7 @@ msgstr " *predefinito*"
 
 #, c-format
 msgid "  (%d) ECC (sign only)\n"
-msgstr "  (%d) DSA (firma solo)\n"
+msgstr "  (%d) ECC (solo firma)\n"
 
 #, c-format
 msgid "  (%d) ECC (set your own capabilities)%s\n"
@@ -4293,15 +4293,13 @@ msgstr "  (%d) Chiave esistente%s\n"
 msgid "  (%d) Existing key from card%s\n"
 msgstr "  (%d) Chiave esistente dalla carta%s\n"
 
-#, fuzzy, c-format
-#| msgid "   (%d) ECC and ECC\n"
+#, c-format
 msgid "  (%d) ECC and Kyber%s\n"
-msgstr "   (%d) ECC ed ECC\n"
+msgstr "  (%d) ECC e Kyber%s\n"
 
-#, fuzzy, c-format
-#| msgid "  (%d) ECC (encrypt only)%s\n"
+#, c-format
 msgid "  (%d) Kyber (encrypt only)%s\n"
-msgstr "  (%d) ECC (solo crittografia)%s\n"
+msgstr "  (%d) Kyber (solo crittografia)%s\n"
 
 msgid "Enter the keygrip: "
 msgstr "Immettere il keygrip: "
-- 
2.55.0



From koray.fra at gmail.com  Sat Aug  8 00:11:38 2026
From: koray.fra at gmail.com (koraynilay)
Date: Sat,  8 Aug 2026 00:11:38 +0200
Subject: [PATCH gnupg 3/3] po: Fix fuzzy Italian translations
In-Reply-To: <20260807221143.1412863-1-koray.fra@gmail.com>
References: <20260807221143.1412863-1-koray.fra@gmail.com>
Message-ID: <20260807221143.1412863-4-koray.fra@gmail.com>

Fix and unmark fuzzy translations for the Italian language.

Signed-off-by: koraynilay <koray.fra at gmail.com>
---
 po/it.po | 239 +++++++++++++++++++------------------------------------
 1 file changed, 80 insertions(+), 159 deletions(-)

diff --git a/po/it.po b/po/it.po
index eb95eb5f8..187e5fe5f 100644
--- a/po/it.po
+++ b/po/it.po
@@ -271,10 +271,9 @@ msgstr "PIN non ripetuto correttamente; Riprova"
 msgid "Please enter the PIN%s%s%s to unlock the card"
 msgstr "Immettere il PIN%s%s%s per sbloccare la scheda"
 
-#, fuzzy, c-format
-#| msgid "error writing to %s: %s\n"
+#, c-format
 msgid "error writing to pipe: %s\n"
-msgstr "errore durante la scrittura in %s: %s\n"
+msgstr "errore durante la scrittura nella pipe: %s\n"
 
 msgid "Enter new passphrase"
 msgstr "Inserisci la nuova passphrase"
@@ -394,10 +393,8 @@ msgstr "|ALGO|usa ALGO per mostrare le impronte digitali ssh"
 msgid "enable putty support"
 msgstr "abilitare il supporto putty"
 
-#, fuzzy
-#| msgid "enable putty support"
 msgid "enable Win32-OpenSSH support"
-msgstr "abilitare il supporto putty"
+msgstr "abilitare il supporto per Win32-OpenSSH"
 
 msgid "Options controlling the security"
 msgstr "Opzioni che controllano la sicurezza"
@@ -521,10 +518,9 @@ msgstr ""
 msgid "a gpg-agent is already running - not starting a new one\n"
 msgstr "un gpg-agent ? gi? in esecuzione - non iniziare uno nuovo\n"
 
-#, fuzzy, c-format
-#| msgid "key %s: removed multiple subkey binding\n"
+#, c-format
 msgid "socket file removed - retrying binding\n"
-msgstr "chiave %s: rimossa l'associazione di pi? sottochiavi\n"
+msgstr "file socket rimosso - riprovo l'associazione\n"
 
 #, c-format
 msgid "error getting nonce for the socket\n"
@@ -759,22 +755,16 @@ msgstr "Modifica passphrase"
 msgid "I'll change it later"
 msgstr "Lo cambier? pi? tardi"
 
-#, fuzzy, c-format
-#| msgid "receiving line failed: %s\n"
+#, c-format
 msgid "Unprotecting key failed: %s\n"
-msgstr "linea di ricezione non riuscita: %s\n"
+msgstr "Deprotezione chiave fallita: %s\n"
 
 msgid "Please insert the card with serial number"
 msgstr "Inserire la scheda con il numero di serie"
 
-#, fuzzy, c-format
-#| msgid ""
-#| "An ssh process requested the use of key%%0A  %s%%0A  (%s)%%0ADo you want "
-#| "to allow this?"
+#, c-format
 msgid "Requested the use of key%%0A  %s%%0A  %s%%0ADo you want to allow this?"
-msgstr ""
-"Un processo ssh ha richiesto l'utilizzo della chiave%%0A  %s%%0A  (%s)%%0ASi "
-"desidera consentire questa operazione?"
+msgstr "Chiave%%0A  %s%%0A  %s%%0Arichiesta. Consentire l'operazione?"
 
 #, c-format
 msgid ""
@@ -1691,15 +1681,12 @@ msgstr "I comandi di amministrazione non sono consentiti\n"
 msgid "Invalid command  (try \"help\")\n"
 msgstr "Comando non valido  (prova \"help\")\n"
 
-#, fuzzy, c-format
-#| msgid "key operation not possible: %s\n"
+#, c-format
 msgid "modifying the recipients is not possible: %s\n"
-msgstr "operazione chiave non possibile: %s\n"
+msgstr "modifica dei destinatari non possibile: %s\n"
 
-#, fuzzy
-#| msgid "decryption failed: %s\n"
 msgid "decryption failed"
-msgstr "decifratura fallita: %s\n"
+msgstr "decifratura fallita"
 
 #, c-format
 msgid "--output doesn't work for this command\n"
@@ -1849,24 +1836,21 @@ msgstr ""
 "AVVISO: l'algoritmo di compressione %s (%d) viola le preferenze dei "
 "destinatari\n"
 
-#, fuzzy, c-format
-#| msgid "Number of recipients"
+#, c-format
 msgid "number of removed recipients: %u\n"
-msgstr "Numero di destinatari"
+msgstr "numero di destinatari rimossi: %u\n"
 
 #, c-format
 msgid "option '%s' may not be used in %s mode\n"
 msgstr "l'opzione '%s' non pu? essere utilizzata in modalit? %s\n"
 
-#, fuzzy, c-format
-#| msgid "can't encrypt to '%s'\n"
+#, c-format
 msgid "already encrypted to %08lX\n"
-msgstr "impossibile crittografare in '%s'\n"
+msgstr "gi? crittografato per %08lX\n"
 
-#, fuzzy, c-format
-#| msgid "%s.%s encrypted data\n"
+#, c-format
 msgid "%s encrypted data\n"
-msgstr "%s.%s dati crittografati della commissione\n"
+msgstr "%s dati crittografati\n"
 
 #, c-format
 msgid "encrypted with unknown algorithm %d\n"
@@ -1898,18 +1882,14 @@ msgstr "rimuovere parti inutilizzabili dalla chiave durante l'esportazione"
 msgid "remove as much as possible from key during export"
 msgstr "rimuovere il pi? possibile dalla chiave durante l'esportazione"
 
-#, fuzzy
-#| msgid "generate a revocation certificate"
 msgid "export only revocation certificates"
-msgstr "genera un certificato di revoca"
+msgstr "esporta solo i certificati di revoca"
 
 msgid "use the GnuPG key backup format"
 msgstr "utilizzare il formato di backup della chiave GnuPG"
 
-#, fuzzy
-#| msgid "exporting secret keys not allowed\n"
 msgid "export secret keys using the GnuPG format"
-msgstr "esportazione di chiavi segrete non consentita\n"
+msgstr "esporta chiavi segrete nel formato GnuPG"
 
 msgid " - skipped"
 msgstr " - saltato"
@@ -2054,10 +2034,8 @@ msgstr "firmare rapidamente un tasto"
 msgid "quickly sign a key locally"
 msgstr "firmare rapidamente una chiave localmente"
 
-#, fuzzy
-#| msgid "sign selected user IDs with a trust signature"
 msgid "quickly sign a key with a trust signature"
-msgstr "firmare gli ID utente selezionati con una firma di trust"
+msgstr "firma velocemente una chiave usando una firma di trust"
 
 msgid "quickly revoke a key signature"
 msgstr "revocare rapidamente una firma chiave"
@@ -2347,10 +2325,8 @@ msgstr "mostra ID utente revocati e scaduti negli elenchi di chiavi"
 msgid "show revoked and expired subkeys in key listings"
 msgstr "mostra sottochiavi revocate e scadute negli elenchi di chiavi"
 
-#, fuzzy
-#| msgid "show expiration dates during signature listings"
 msgid "show signatures with invalid algorithms during signature listings"
-msgstr "mostra date di scadenza durante le inserzioni delle firme"
+msgstr "mostra firme con algoritmi non validi negli elenchi di firme"
 
 msgid "show the keyring name in key listings"
 msgstr "mostrare il nome del keyring negli elenchi delle chiavi"
@@ -2358,20 +2334,14 @@ msgstr "mostrare il nome del keyring negli elenchi delle chiavi"
 msgid "show expiration dates during signature listings"
 msgstr "mostra date di scadenza durante le inserzioni delle firme"
 
-#, fuzzy
-#| msgid "list preferences (expert)"
 msgid "show preferences"
-msgstr "elenca le preferenze (per esperti)"
+msgstr "visualizza preferenze"
 
-#, fuzzy
-#| msgid "change the ownertrust"
 msgid "show ownertrust"
-msgstr "cambia il valore di fiducia"
+msgstr "visualizza il valore di fiducia"
 
-#, fuzzy
-#| msgid "Unknown critical signature notation: "
 msgid "show trust signature information"
-msgstr "Notazione della firma critica sconosciuta: "
+msgstr "visualizza informazioni sulla firma di trust"
 
 #, c-format
 msgid "unknown TOFU policy '%s'\n"
@@ -2501,10 +2471,9 @@ msgstr "elenco di individuazione automatica delle chiavi non valido\n"
 msgid "invalid argument for option \"%.50s\"\n"
 msgstr "argomento non valido per l'opzione \"%.50s\"\n"
 
-#, fuzzy, c-format
-#| msgid "error parsing key specification '%s': %s\n"
+#, c-format
 msgid "error parsing value for option '%s': %s\n"
-msgstr "errore durante l'analisi della specifica della chiave '%s': %s\n"
+msgstr "errore durante l'analisi del valore dell'opzione '%s': %s\n"
 
 #, c-format
 msgid "WARNING: program may create a core file!\n"
@@ -2776,10 +2745,8 @@ msgstr "ripristinare le chiavi all'importazione"
 msgid "update even unchanged keys"
 msgstr ""
 
-#, fuzzy
-#| msgid "list secret keys"
 msgid "do not import secret keys"
-msgstr "elenca le chiavi segrete"
+msgstr "non importare chiavi segrete"
 
 #, c-format
 msgid "skipping block of type %d\n"
@@ -3046,15 +3013,13 @@ msgstr "L'user ID non ? pi? valido"
 msgid "reason for revocation: "
 msgstr "ragione della revoca: "
 
-#, fuzzy, c-format
-#| msgid "key %s: can't locate original keyblock: %s\n"
+#, c-format
 msgid "key %s: can't locate keyblock: %s\n"
-msgstr "chiave %s: impossibile individuare il blocco di chiave originale: %s\n"
+msgstr "chiave %s: impossibile individuare il blocco di chiavi: %s\n"
 
-#, fuzzy, c-format
-#| msgid "key %s: can't read original keyblock: %s\n"
+#, c-format
 msgid "key %s: can't read keyblock: %s\n"
-msgstr "chiave %s: impossibile leggere il keyblock originale: %s\n"
+msgstr "chiave %s: impossibile leggere il blocco di chiavi: %s\n"
 
 #, c-format
 msgid "key %s: no public key - can't apply revocation certificate\n"
@@ -3526,10 +3491,8 @@ msgstr "eliminare le sottochiavi selezionate"
 msgid "add a revocation key"
 msgstr "aggiungi una chiave di revoca"
 
-#, fuzzy
-#| msgid "Data decryption succeeded"
 msgid "add an additional decryption subkey"
-msgstr "Decrittografia dei dati riuscita"
+msgstr "aggiungi un'ulteriore sottochiave di decriptazione"
 
 msgid "delete signatures from the selected user IDs"
 msgstr "eliminare le firme dagli ID utente selezionati"
@@ -3598,12 +3561,10 @@ msgstr "? disponibile una chiave segreta.\n"
 msgid "Secret subkeys are available.\n"
 msgstr "Sono disponibili sottochiavi segrete.\n"
 
-#, fuzzy
-#| msgid "Note: Only the secret part of the shown subkey will be deleted.\n"
 msgid ""
 "Note: the local copy of the secret key will only be deleted with \"save\".\n"
 msgstr ""
-"Nota: verr? eliminata solo la parte segreta della sottochiave visualizzata.\n"
+"Nota: la copia locale della chiave segreta verr? cancellata solo con \"save\".\n"
 
 msgid "Need the secret key to do this.\n"
 msgstr "Per fare questo serve la chiave segreta.\n"
@@ -3715,10 +3676,9 @@ msgstr "Salvare le modifiche? (y/N) "
 msgid "Quit without saving? (y/N) "
 msgstr "Uscire senza salvare? (y/N) "
 
-#, fuzzy, c-format
-#| msgid "deleting secret %s failed: %s\n"
+#, c-format
 msgid "deleting copy of secret key failed: %s\n"
-msgstr "eliminazione del segreto %s non riuscita: %s\n"
+msgstr "eliminazione della copia della chiave segreta non riuscita: %s\n"
 
 #, c-format
 msgid "Key not changed so no update needed.\n"
@@ -3736,10 +3696,9 @@ msgstr "revoca dell'ID utente non riuscita: %s\n"
 msgid "setting the primary user ID failed: %s\n"
 msgstr "impostazione dell'ID utente primario non riuscita: %s\n"
 
-#, fuzzy, c-format
-#| msgid "checking the trust list failed: %s\n"
+#, c-format
 msgid "setting the ownertrust to '%s' failed: %s\n"
-msgstr "controllo dell'elenco di attendibilit? non riuscito: %s\n"
+msgstr "impostazione della fiducia del proprietario '%s' fallita: %s\n"
 
 #, c-format
 msgid "\"%s\" is not a fingerprint\n"
@@ -3759,10 +3718,9 @@ msgstr "Nessun ID utente corrispondente."
 msgid "Nothing to sign.\n"
 msgstr "Niente da firmare.\n"
 
-#, fuzzy, c-format
-#| msgid "revoking the key signature failed: %s\n"
+#, c-format
 msgid "creating key signature failed: %s\n"
-msgstr "revoca della firma della chiave non riuscita: %s\n"
+msgstr "creazione della firma della chiave fallita: %s\n"
 
 #, c-format
 msgid "Not signed by you.\n"
@@ -3869,10 +3827,9 @@ msgstr "AVVISO: la sottochiave di crittografia scade a breve.\n"
 msgid "You may want to change its expiration date too.\n"
 msgstr "Si consiglia di modificare anche la sua data di scadenza.\n"
 
-#, fuzzy, c-format
-#| msgid "WARNING: Your encryption subkey expires soon.\n"
+#, c-format
 msgid "WARNING: No valid encryption subkey left over.\n"
-msgstr "AVVISO: la sottochiave di crittografia scade a breve.\n"
+msgstr "AVVISO: Nessuna sottochiave di cifratura valida rimasta.\n"
 
 msgid ""
 "WARNING: This is a PGP2-style key.  Adding a photo ID may cause some "
@@ -3889,10 +3846,8 @@ msgid "You may not add a photo ID to a PGP2-style key.\n"
 msgstr ""
 "Non ? possibile aggiungere un ID fotografico a una chiave in stile PGP2.\n"
 
-#, fuzzy
-#| msgid "Such a user ID already exists on this key!\n"
 msgid "Such a user ID already exists on this key!"
-msgstr "Tale ID utente esiste gi? in questa chiave!\n"
+msgstr "Tale ID utente esiste gi? in questa chiave!"
 
 msgid "Delete this good signature? (y/N/q)"
 msgstr "Cancellare questa firma corretta? (s/N/q)"
@@ -3980,15 +3935,13 @@ msgstr ""
 msgid "Enter the fingerprint of the additional decryption subkey: "
 msgstr ""
 
-#, fuzzy, c-format
-#| msgid "(unless you specify the key by fingerprint)\n"
+#, c-format
 msgid "Did you specify the fingerprint of a subkey?\n"
-msgstr "(a meno che la chiave sia specificata con il fingerprint)\n"
+msgstr "Hai specificato l'impronta di una sottochiave?\n"
 
-#, fuzzy, c-format
-#| msgid "Subkey %s is already revoked.\n"
+#, c-format
 msgid "key \"%s\" is already on this keyblock\n"
-msgstr "La sottochiave %s ? gi? stata revocata.\n"
+msgstr "la chiave \"%s\" ? gi? in questo blocco di chiavi\n"
 
 msgid ""
 "Are you sure you want to change the expiration time for multiple subkeys? (y/"
@@ -4341,10 +4294,9 @@ msgstr "La dimensione richiesta della chiave ? %u bit\n"
 msgid "Please select which elliptic curve you want:\n"
 msgstr "Selezionare la curva ellittica desiderata:\n"
 
-#, fuzzy, c-format
-#| msgid "Please select what kind of key you want:\n"
+#, c-format
 msgid "Please select the %s variant you want:\n"
-msgstr "Per favore scegli che tipo di chiave vuoi:\n"
+msgstr "Per favore scegli la variante %s che vuoi:\n"
 
 msgid ""
 "Please specify how long the key should be valid.\n"
@@ -4599,10 +4551,9 @@ msgstr ""
 "consiglia di utilizzare\n"
 "il comando \"--edit-key\" per generare una sottochiave a questo scopo.\n"
 
-#, fuzzy, c-format
-#| msgid "WARNING: This key has been revoked by its owner!\n"
+#, c-format
 msgid "Note: The key has been created with one or more ADSK!\n"
-msgstr "ATTENZIONE: questa chiave ? stata revocata dal suo proprietario!\n"
+msgstr "Nota: La chiave ? stata creata con una o pi? ADSK!\n"
 
 #, c-format
 msgid ""
@@ -4779,10 +4730,9 @@ msgstr "protocollo keyserver non valido (noi %d!=intestazione %d!)\n"
 msgid "\"%s\" not a key ID: skipping\n"
 msgstr "\"%s\" non ? un ID chiave:\n"
 
-#, fuzzy, c-format
-#| msgid "\"%s\" is not a fingerprint\n"
+#, c-format
 msgid "\"%s\" not a fingerprint: skipping\n"
-msgstr "\"%s\" non ? un'impronta digitale\n"
+msgstr "\"%s\" non ? un'impronta digitale: ignoro\n"
 
 #, c-format
 msgid "refreshing %d key from %s\n"
@@ -5144,10 +5094,8 @@ msgstr "non compresso|nessuno"
 msgid "this message may not be usable by %s\n"
 msgstr "questo messaggio pu? non essere utilizzabile da %s\n"
 
-#, fuzzy
-#| msgid "enable key"
 msgid "enabled"
-msgstr "chiave di abilitazione"
+msgstr "abilitata"
 
 #, c-format
 msgid "ambiguous option '%s'\n"
@@ -5166,10 +5114,9 @@ msgstr ""
 msgid "unknown weak digest '%s'\n"
 msgstr "digest debole sconosciuto '%s'\n"
 
-#, fuzzy, c-format
-#| msgid "Note: old default options file '%s' ignored\n"
+#, c-format
 msgid "Note: partial file '%s' removed\n"
-msgstr "Nota: il vecchio file di opzioni predefinito '%s' ? stato ignorato\n"
+msgstr "Nota: file parziale '%s' rimosso\n"
 
 #, c-format
 msgid "File '%s' exists. "
@@ -5211,10 +5158,8 @@ msgstr "Notazione della firma critica sconosciuta: "
 msgid "subpacket of type %d has critical bit set\n"
 msgstr "il sottopacchetto di tipo %d ha un bit critico impostato\n"
 
-#, fuzzy
-#| msgid "Please enter the new passphrase"
 msgid "Please enter the passphrase for decryption."
-msgstr "Inserisci la nuova passphrase"
+msgstr "Inserisci la passphrase per la decifrazione."
 
 msgid "Enter passphrase\n"
 msgstr "Inserisci la passphrase\n"
@@ -5247,10 +5192,8 @@ msgstr ""
 msgid "Do you really want to permanently delete the OpenPGP secret key:"
 msgstr "Si desidera eliminare definitivamente la chiave segreta OpenPGP:"
 
-#, fuzzy
-#| msgid "Please enter the passphrase to export the OpenPGP secret key:"
 msgid "Please enter the passphrase to export the secret key with keygrip:"
-msgstr "Immettere la passphrase per esportare la chiave segreta OpenPGP:"
+msgstr "Immettere la passphrase per esportare la chiave segreta con keygrip:"
 
 #, c-format
 msgid ""
@@ -5661,10 +5604,9 @@ msgstr ""
 msgid "okay, we are the anonymous recipient.\n"
 msgstr "bene, siamo il destinatario anonimo.\n"
 
-#, fuzzy, c-format
-#| msgid "WARNING: signing subkey %s is not cross-certified\n"
+#, c-format
 msgid "WARNING: session key is not quantum-resistant\n"
-msgstr "AVVISO: la sottochiave di firma %s non ? certificata incrociata\n"
+msgstr "AVVISO: la chiave di sessione non ? resistente ad attacchi post-quantum\n"
 
 #, c-format
 msgid "old encoding of the DEK is not supported\n"
@@ -5684,10 +5626,9 @@ msgstr ""
 msgid "Note: secret key %s expired at %s\n"
 msgstr "Nota: chiave segreta %s scaduta alle %s\n"
 
-#, fuzzy, c-format
-#| msgid "certificate should not have been used for encryption\n"
+#, c-format
 msgid "Note: ADSK key has been used for decryption"
-msgstr "certificato non avrebbe dovuto essere utilizzato per la crittografia\n"
+msgstr "Nota: la chiave ADSK ? stata usata per la decifratura"
 
 #, c-format
 msgid "Note: key has been revoked"
@@ -5925,12 +5866,9 @@ msgstr ""
 "presupponendo una firma non valida dalla chiave %s a causa di un bit critico "
 "sconosciuto\n"
 
-#, fuzzy, c-format
-#| msgid "key %s: no public key - can't apply revocation certificate\n"
+#, c-format
 msgid "key %s: no public key - can't check revocation signature.\n"
-msgstr ""
-"chiave %s: nessuna chiave pubblica - impossibile applicare il certificato di "
-"revoca\n"
+msgstr "chiave %s: nessuna chiave pubblica - impossibile controllare la firma di revoca.\n"
 
 #, c-format
 msgid "key %s: no subkey for subkey revocation signature\n"
@@ -6550,15 +6488,13 @@ msgid_plural " (%d validity counts cleared)\n"
 msgstr[0] " (%d conteggio di validit? cancellato)\n"
 msgstr[1] " (%d conteggi di validit? cancellati)\n"
 
-#, fuzzy, c-format
-#| msgid "no ultimately trusted keys found\n"
+#, c-format
 msgid "Note: ultimately trusted key %s not found\n"
-msgstr "non ? stata trovata alcuna chiave definitivamente affidabile\n"
+msgstr "Nota: la chiave definitivamente affidabile %s non ? stata trovata\n"
 
-#, fuzzy, c-format
-#| msgid "no ultimately trusted keys found\n"
+#, c-format
 msgid "Note: ultimately trusted key %s expired\n"
-msgstr "non ? stata trovata alcuna chiave definitivamente affidabile\n"
+msgstr "Nota: la chiave definitivamente affidabile %s ? scaduta\n"
 
 #, c-format
 msgid "no ultimately trusted keys found\n"
@@ -6893,10 +6829,8 @@ msgstr "l'accesso ai comandi di amministrazione non ? configurato\n"
 msgid "||Please enter the PIN"
 msgstr "||Inserisci il PIN"
 
-#, fuzzy
-#| msgid "||Please enter the Reset Code for the card"
 msgid "|R|Please enter the Reset Code for the card"
-msgstr "||Inserisci il Codice reset per la carta"
+msgstr "|R|Inserisci il Codice reset per la carta"
 
 #, c-format
 msgid "Reset Code is too short; minimum length is %d\n"
@@ -7478,10 +7412,8 @@ msgstr " (opzionale; terminare con una riga vuota):\n"
 msgid "Enter URIs"
 msgstr "Immettere gli URI"
 
-#, fuzzy
-#| msgid "Enter the notation: "
 msgid "Enter extensions"
-msgstr "Immettere la notazione: "
+msgstr "Immettere le estensioni"
 
 msgid "Create self-signed certificate? (y/N) "
 msgstr "Creare un certificato autofirmato? (y/N) "
@@ -7653,10 +7585,9 @@ msgstr "Nota: impossibile eseguire la crittografia in '%s': %s\n"
 msgid "unknown validation model '%s'\n"
 msgstr "modello di convalida sconosciuto '%s'\n"
 
-#, fuzzy, c-format
-#| msgid "cipher algorithm %d%s is unknown or disabled\n"
+#, c-format
 msgid "given cipher algorithm '%s' is unknown - using '%s'\n"
-msgstr "l'algoritmo di cifratura %d%s ? sconosciuto o disattivato\n"
+msgstr "l'algoritmo di cifratura dato '%s' ? sconosciuto - uso '%s'\n"
 
 #, c-format
 msgid "importing common certificates '%s'\n"
@@ -7666,10 +7597,9 @@ msgstr "importazione di certificati comuni '%s'\n"
 msgid "can't sign using '%s': %s\n"
 msgstr "impossibile firmare utilizzando '%s': %s\n"
 
-#, fuzzy, c-format
-#| msgid "can't open fd %d: %s\n"
+#, c-format
 msgid "can't open outputfile: %s\n"
-msgstr "impossibile aprire fd %d: %s\n"
+msgstr "impossibile aprire il file di output: %s\n"
 
 #, c-format
 msgid "invalid command (there is no implicit command)\n"
@@ -7730,10 +7660,9 @@ msgstr "problema durante la ri-ricerca del certificato: %s\n"
 msgid "Error - "
 msgstr "Errore - "
 
-#, fuzzy, c-format
-#| msgid "error writing to stdout: %s\n"
+#, c-format
 msgid "error writing to output: %s\n"
-msgstr "errore durante la scrittura in stdout: %s\n"
+msgstr "errore durante la scrittura in output: %s\n"
 
 #, c-format
 msgid "invalid formatted fingerprint in '%s', line %d\n"
@@ -8331,10 +8260,8 @@ msgstr "crl_cache_insert tramite autorit? emittente non riuscita: %s\n"
 msgid "reader to file mapping table full - waiting\n"
 msgstr "lettore alla tabella di mapping file piena - in attesa\n"
 
-#, fuzzy
-#| msgid "CRL access not possible due to Tor mode\n"
 msgid "CRL access not possible due to Tor mode"
-msgstr "Accesso CRL non possibile a causa della modalit? Tor\n"
+msgstr "Accesso CRL non possibile a causa della modalit? Tor"
 
 #, c-format
 msgid "CRL access not possible due to disabled %s\n"
@@ -8507,10 +8434,8 @@ msgstr "|URL|reindirizza tutte le richieste HTTP all'URL"
 msgid "use system's HTTP proxy setting"
 msgstr "utilizzare l'impostazione proxy HTTP del sistema"
 
-#, fuzzy
-#| msgid "Configuration for HTTP servers"
 msgid "Configuration for OpenPGP servers"
-msgstr "Configurazione per i server HTTP"
+msgstr "Configurazione per i server OpenPGP"
 
 msgid "|URL|use keyserver at URL"
 msgstr "| URL: utilizzare keyserver all'URL"
@@ -8518,10 +8443,8 @@ msgstr "| URL: utilizzare keyserver all'URL"
 msgid "|FILE|use the CA certificates in FILE for HKP over TLS"
 msgstr "|FILE|utilizzare i certificati CA in FILE per HKP su TLS"
 
-#, fuzzy
-#| msgid "Configuration for HTTP servers"
 msgid "Configuration for X.509 servers"
-msgstr "Configurazione per i server HTTP"
+msgstr "Configurazione per i server X.509"
 
 msgid "inhibit the use of LDAP"
 msgstr "inibire l'uso di LDAP"
@@ -8759,10 +8682,8 @@ msgstr "errore durante la lettura dal risponditore: %s\n"
 msgid "response from server too large; limit is %d bytes\n"
 msgstr "risposta dal server troppo grande; limite ? %d byte\n"
 
-#, fuzzy
-#| msgid "OCSP request not possible due to Tor mode\n"
 msgid "OCSP request not possible due to Tor mode"
-msgstr "Richiesta OCSP non possibile a causa della modalit? Tor\n"
+msgstr "Richiesta OCSP non possibile a causa della modalit? Tor"
 
 #, c-format
 msgid "OCSP request not possible due to disabled HTTP\n"
-- 
2.55.0



From koray.fra at gmail.com  Sat Aug  8 00:11:37 2026
From: koray.fra at gmail.com (koraynilay)
Date: Sat,  8 Aug 2026 00:11:37 +0200
Subject: [PATCH gnupg 2/3] po: Improve Italian translation
In-Reply-To: <20260807221143.1412863-1-koray.fra@gmail.com>
References: <20260807221143.1412863-1-koray.fra@gmail.com>
Message-ID: <20260807221143.1412863-3-koray.fra@gmail.com>

Improve the translation of the --full-generate-key
menu text so they are more correct.

Signed-off-by: koraynilay <koray.fra at gmail.com>
---
 po/it.po | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/po/it.po b/po/it.po
index 08aa1cabc..eb95eb5f8 100644
--- a/po/it.po
+++ b/po/it.po
@@ -5,7 +5,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: GNU gnupg 2.3.0\n"
 "Report-Msgid-Bugs-To: translations at gnupg.org\n"
-"PO-Revision-Date: 2026-08-07 23:13+0200\n"
+"PO-Revision-Date: 2026-08-07 23:37+0200\n"
 "Last-Translator: Denis <student at alice.it>\n"
 "Language-Team: \n"
 "Language: it_IT\n"
@@ -4244,15 +4244,15 @@ msgstr "   (%d) DSA ed Elgamal%s\n"
 
 #, c-format
 msgid "   (%d) DSA (sign only)%s\n"
-msgstr "   (%d) DSA (solo segno)%s\n"
+msgstr "   (%d) DSA (solo firma)%s\n"
 
 #, c-format
 msgid "   (%d) RSA (sign only)%s\n"
-msgstr "   (%d) RSA (solo segno)%s\n"
+msgstr "   (%d) RSA (solo firma)%s\n"
 
 #, c-format
 msgid "   (%d) Elgamal (encrypt only)%s\n"
-msgstr "   (%d) Elgamal (solo crittografa)%s\n"
+msgstr "   (%d) Elgamal (solo crittografia)%s\n"
 
 #, c-format
 msgid "   (%d) RSA (encrypt only)%s\n"
@@ -4260,11 +4260,11 @@ msgstr "   (%d) RSA (solo crittografia)%s\n"
 
 #, c-format
 msgid "   (%d) DSA (set your own capabilities)%s\n"
-msgstr "   (%d) DSA (impostare le proprie funzionalit?)%s\n"
+msgstr "   (%d) DSA (personalizza le funzionalit?)%s\n"
 
 #, c-format
 msgid "   (%d) RSA (set your own capabilities)%s\n"
-msgstr "   (%d) RSA (impostare le proprie funzionalit?)%s\n"
+msgstr "   (%d) RSA (personalizza le funzionalit?)%s\n"
 
 #, c-format
 msgid "   (%d) ECC (sign and encrypt)%s\n"
@@ -4279,7 +4279,7 @@ msgstr "  (%d) ECC (solo firma)\n"
 
 #, c-format
 msgid "  (%d) ECC (set your own capabilities)%s\n"
-msgstr "  (%d) ECC (impostare le proprie funzionalit?)%s\n"
+msgstr "  (%d) ECC (personalizza le funzionalit?)%s\n"
 
 #, c-format
 msgid "  (%d) ECC (encrypt only)%s\n"
-- 
2.55.0



From wk at gnupg.org  Thu Aug 13 17:32:34 2026
From: wk at gnupg.org (Werner Koch)
Date: Thu, 13 Aug 2026 17:32:34 +0200
Subject: Mailman migration test 2026-08-13T15:32
Message-ID: <87tsoyvxwt.fsf@jacob.g10code.de>

Hi!

I am sorry for the trouble but we had to migrate the Mailman
installation to a newer machine and had to migrate from Python2 to
Python3.


Shalom-Salam,

   Werner


-- 
The pioneers of a warless world are the youth that
refuse military service.             - A. Einstein
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openpgp-digital-signature.asc
Type: application/pgp-signature
Size: 284 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260813/127cd6ad/attachment.sig>

From rjh at sixdemonbag.org  Thu Aug 13 22:07:36 2026
From: rjh at sixdemonbag.org (Robert J. Hansen)
Date: Thu, 13 Aug 2026 16:07:36 -0400
Subject: Mailman migration test 2026-08-13T15:32
In-Reply-To: <87tsoyvxwt.fsf@jacob.g10code.de>
References: <87tsoyvxwt.fsf@jacob.g10code.de>
Message-ID: <1c00ae44-66b6-4ea5-b964-bc45f3f940fa@sixdemonbag.org>

> I am sorry for the trouble but we had to migrate the Mailman
> installation to a newer machine and had to migrate from Python2 to
> Python3.
If you need a confirmation members are receiving and can respond to the
new Mailman, let this be it. :)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260813/262a2259/attachment.sig>

From koray.fra at gmail.com  Thu Aug 13 22:33:22 2026
From: koray.fra at gmail.com (koraynilay)
Date: Thu, 13 Aug 2026 22:33:22 +0200
Subject: Mailman migration test 2026-08-13T15:32
In-Reply-To: <1c00ae44-66b6-4ea5-b964-bc45f3f940fa@sixdemonbag.org>
References: <87tsoyvxwt.fsf@jacob.g10code.de>
 <1c00ae44-66b6-4ea5-b964-bc45f3f940fa@sixdemonbag.org>
Message-ID: <DKO3PA54HR8G.17RGET9M46X52@gmail.com>

On Thu Aug 13, 2026 at 10:07 PM CEST, Robert J. Hansen wrote:
>> I am sorry for the trouble but we had to migrate the Mailman
>> installation to a newer machine and had to migrate from Python2 to
>> Python3.
> If you need a confirmation members are receiving and can respond to the
> new Mailman, let this be it. :)

Can confirm, https://lists.gnupg.org/mailman/listinfo/gnupg-devel says
connection refused for me tho, not sure if that's expected.

Best,
koraynilay
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260813/3b5dbd71/attachment.sig>

From wk at gnupg.org  Fri Aug 14 10:17:26 2026
From: wk at gnupg.org (Werner Koch)
Date: Fri, 14 Aug 2026 10:17:26 +0200
Subject: Mailman migration test 2026-08-13T15:32
In-Reply-To: <DKO3PA54HR8G.17RGET9M46X52@gmail.com> (koraynilay's message of
	"Thu, 13 Aug 2026 22:33:22 +0200")
References: <87tsoyvxwt.fsf@jacob.g10code.de>
	<1c00ae44-66b6-4ea5-b964-bc45f3f940fa@sixdemonbag.org>
	<DKO3PA54HR8G.17RGET9M46X52@gmail.com>
Message-ID: <87cxvlw1yh.fsf@jacob.g10code.de>

On Thu, 13 Aug 2026 22:33, koraynilay said:

> Can confirm, https://lists.gnupg.org/mailman/listinfo/gnupg-devel says
> connection refused for me tho, not sure if that's expected.

The same rules as for dev.gnupg.org apply: We had to blacklist most
countries to avoid overloads by AI scrapers and even starnge SYN flood
attacks.  That is unfortunate but the current state of the internet for
non-huge sites.  :-(

The mailing lists have been moved to the deve.gnupg.org box because that
one already has a mail setup and sens lots of mails - thus the mailing
lists fit well here.


Shalom-Salam,

   Werner

-- 
The pioneers of a warless world are the youth that
refuse military service.             - A. Einstein
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openpgp-digital-signature.asc
Type: application/pgp-signature
Size: 284 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260814/c2a139cb/attachment.sig>

From koray.fra at gmail.com  Fri Aug 14 16:02:51 2026
From: koray.fra at gmail.com (koraynilay)
Date: Fri, 14 Aug 2026 16:02:51 +0200
Subject: Mailman migration test 2026-08-13T15:32
In-Reply-To: <87cxvlw1yh.fsf@jacob.g10code.de>
References: <87tsoyvxwt.fsf@jacob.g10code.de>
 <1c00ae44-66b6-4ea5-b964-bc45f3f940fa@sixdemonbag.org>
 <DKO3PA54HR8G.17RGET9M46X52@gmail.com> <87cxvlw1yh.fsf@jacob.g10code.de>
Message-ID: <DKOQ0TWYD90Y.1Z83R1QNV80QN@gmail.com>

On Fri Aug 14, 2026 at 10:17 AM CEST, Werner Koch wrote:
> On Thu, 13 Aug 2026 22:33, koraynilay said:
>
>> Can confirm, https://lists.gnupg.org/mailman/listinfo/gnupg-devel says
>> connection refused for me tho, not sure if that's expected.
>
> The same rules as for dev.gnupg.org apply: We had to blacklist most
> countries to avoid overloads by AI scrapers and even starnge SYN flood
> attacks.  That is unfortunate but the current state of the internet for
> non-huge sites.  :-(
>
> The mailing lists have been moved to the deve.gnupg.org box because that
> one already has a mail setup and sens lots of mails - thus the mailing
> lists fit well here.

Ah ok, yeah sad world we live in :(
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260814/9b7ee676/attachment.sig>

From ametzler at bebt.de  Mon Aug 17 18:09:22 2026
From: ametzler at bebt.de (Andreas Metzler)
Date: Mon, 17 Aug 2026 18:09:22 +0200
Subject: [Announce] GnuPG bug tracker not available due to heavy DDoS
In-Reply-To: 
 <875x1o3g2u.fsf__28728.4893145383$1785933523$gmane$org@jacob.g10code.de>
References: 
 <875x1o3g2u.fsf__28728.4893145383$1785933523$gmane$org@jacob.g10code.de>
Message-ID: <aoMyMk4GNHbfOtyb@argenau.bebt.de>

On 2026-08-05 Werner Koch via Gnupg-devel <gnupg-devel at gnupg.org> wrote:
> our admin asked me to post this on the status of dev.gnupg.org:

> The GnuPG project has been facing increasing AI scraper attacks for
> more than a year, but now the situation switched to SYN flood attacks.
> We are dealing with the situation, but for the moment our development
> server with the bugtracker is not available to the public world.

> We are working on a solution which keeps the community involved in
> contributing to the project, but for the moment inconvenience cannot
> be avoided.

> We regret to be forced acting this way, but the AI driven attacks don't
> leave much of a choice.
[...]

Hello,

thanks for heads-up.

I had been tracking the GIT repos on dev.gnupg.org which also stopped
working /reliably/ a couple of weeks ago.

ametzler@:libgpg-error$ git pull
fatal: unable to access 'https://dev.gnupg.org/source/libgpg-error.git/': Failed to connect to dev.gnupg.org:443 after 93 ms: Could not connect to server

Are the mirrored repos on https://github.com/gpg blessed, i.e. can I
rely on them being kept up to date?

cu Andreas
-- 
"You people are noisy," Nia said.
I made the gesture of agreement.

From kloecker at kde.org  Mon Aug 17 18:33:45 2026
From: kloecker at kde.org (Ingo =?UTF-8?B?S2zDtmNrZXI=?=)
Date: Mon, 17 Aug 2026 18:33:45 +0200
Subject: [Announce] GnuPG bug tracker not available due to heavy DDoS
In-Reply-To: <aoMyMk4GNHbfOtyb@argenau.bebt.de>
References: 
 <875x1o3g2u.fsf__28728.4893145383$1785933523$gmane$org@jacob.g10code.de>
 <aoMyMk4GNHbfOtyb@argenau.bebt.de>
Message-ID: <JlGwC8xvRhKtS-76WQXIJA@kde.org>

On Montag, 17. August 2026 18:09:22 Mitteleuropäische Sommerzeit Andreas 
Metzler wrote:
> I had been tracking the GIT repos on dev.gnupg.org which also stopped
> working /reliably/ a couple of weeks ago.
> 
> ametzler@:libgpg-error$ git pull
> fatal: unable to access 'https://dev.gnupg.org/source/libgpg-error.git/':
> Failed to connect to dev.gnupg.org:443 after 93 ms: Could not connect to
> server
> 
> Are the mirrored repos on https://github.com/gpg blessed, i.e. can I
> rely on them being kept up to date?

Unless you require HTTPS you should be able to use
git://git.gnupg.org/...

Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 265 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260817/c2fdccfc/attachment.sig>

From dkg at fifthhorseman.net  Mon Aug 17 21:12:52 2026
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Mon, 17 Aug 2026 15:12:52 -0400
Subject: [BUG] pinentry-{gnome3, gtk-2} should set
 g_log_writer_default_set_use_stderr(true)
In-Reply-To: 
 <CAFh6oAwX7_nvXc1PwDayx-s3TzxGG_bnEYSPzMg5dUHCa63n3g@mail.gmail.com>
References: 
 <CAFh6oAwX7_nvXc1PwDayx-s3TzxGG_bnEYSPzMg5dUHCa63n3g@mail.gmail.com>
Message-ID: <87o6f0tvbf.fsf@fifthhorseman.net>

Hi Kernc--

On Fri 2026-07-17 15:52:24 +0200, Kernc via Gnupg-devel wrote:
> pinentry-gnome3 and pinentry-gtk-2's debug messages are printed to
> stdout, interfering with gpg-agent/pinentry stdout-stream-oriented
> IPC.

Your analysis looks correct to me.

> IMHO, both pinentry-gnome3 and pinentry-gtk-2 should issue
> `g_log_writer_default_set_use_stderr(true)` [1] somewhere early in
> their `main()`. While the default glib behavior seems aptly
> nonsensical, the function docs do warn:
>
>> By default, log messages of levels G_LOG_LEVEL_INFO and G_LOG_LEVEL_DEBUG are sent to stdout, and other log messages are sent to stderr. This is problematic for applications that intend to reserve stdout for structured output such as JSON or XML.

I think your proposal for a fix is reasonable, given the default glib
behavior.

Thanks for noticing this.  Please share patches if you've got them!

       --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 324 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260817/4d591645/attachment.sig>

From kerncece at gmail.com  Tue Aug 18 04:22:52 2026
From: kerncece at gmail.com (Kernc)
Date: Tue, 18 Aug 2026 04:22:52 +0200
Subject: [PATCH] gnome3: Redirect GLib logging messages to stderr
In-Reply-To: <87o6f0tvbf.fsf@fifthhorseman.net>
References: 
 <CAFh6oAwX7_nvXc1PwDayx-s3TzxGG_bnEYSPzMg5dUHCa63n3g@mail.gmail.com>
 <87o6f0tvbf.fsf@fifthhorseman.net>
Message-ID: 
 <CAFh6oAyA0jzmBJYJ6CRDkG3OYUpuGO4S=GkQvK_ETddcy11XDA@mail.gmail.com>

By default, GLib/Gcr/libsecret outputs debug/info logging messages
to stdout, but we use that as the Assuan channel, and outputting to
it anything but the expected verbs breaks pinentry pipelines
in confusing ways.

It is unknown whether a similar patch is needed for gtk-2
or other flavors via the 'CLEARPASSPHRASE' command,
nor if G_MESSAGES_DEBUG needs unsetting from the environment.

An old user reports Gtk-warnings even with pinentry-qt,
but their issue needs more verification.

https://web.archive.org/web/20260629091849/https://dev.gnupg.org/T4144.html

Care must be placed in who inherits our Assuan fds
and what they do with them.

GnuPG-bug-id: 4144
GnuPG-bug-id: 2243
GnuPG-bug-id: 2397
Signed-off-by: Kernc <kerncece at gmail.com>
---
 gnome3/pinentry-gnome3.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/gnome3/pinentry-gnome3.c b/gnome3/pinentry-gnome3.c
index 7f21d6f..3692f49 100644
--- a/gnome3/pinentry-gnome3.c
+++ b/gnome3/pinentry-gnome3.c
@@ -518,6 +518,13 @@ main (int argc, char *argv[])
 {
   pinentry_init (PGMNAME);

+/* Prevent logging messages escaping to stdout (our Assuan channel). */
+#if GLIB_CHECK_VERSION (2, 68, 0)
+  g_log_writer_default_set_use_stderr (TRUE);
+#else
+  g_unsetenv ("G_MESSAGES_DEBUG");
+#endif
+
 #ifdef FALLBACK_CURSES
   if (!getenv ("DBUS_SESSION_BUS_ADDRESS"))
     {
-- 
2.47.3
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260818/36b2133a/attachment.html>

From ametzler at bebt.de  Tue Aug 18 18:47:52 2026
From: ametzler at bebt.de (Andreas Metzler)
Date: Tue, 18 Aug 2026 18:47:52 +0200
Subject: [Announce] GnuPG bug tracker not available due to heavy DDoS
In-Reply-To: <JlGwC8xvRhKtS-76WQXIJA@kde.org>
References: 
 <875x1o3g2u.fsf__28728.4893145383$1785933523$gmane$org@jacob.g10code.de>
 <aoMyMk4GNHbfOtyb@argenau.bebt.de>
 <JlGwC8xvRhKtS-76WQXIJA@kde.org>
Message-ID: <aoSMuLi9Xe50y6Lv@argenau.bebt.de>

On 2026-08-17 Ingo Klöcker <kloecker at kde.org> wrote:
> On Montag, 17. August 2026 18:09:22 Mitteleuropäische Sommerzeit Andreas 
> Metzler wrote:
> > I had been tracking the GIT repos on dev.gnupg.org which also stopped
> > working /reliably/ a couple of weeks ago.
[...]
> Unless you require HTTPS you should be able to use
> git://git.gnupg.org/...

Indeed that works. - Thank you!

cu Andreas

From dkg at fifthhorseman.net  Tue Aug 18 20:02:27 2026
From: dkg at fifthhorseman.net (Daniel Kahn Gillmor)
Date: Tue, 18 Aug 2026 14:02:27 -0400
Subject: [PATCH] gnome3: Redirect GLib logging messages to stderr
In-Reply-To: 
 <CAFh6oAyA0jzmBJYJ6CRDkG3OYUpuGO4S=GkQvK_ETddcy11XDA@mail.gmail.com>
References: 
 <CAFh6oAwX7_nvXc1PwDayx-s3TzxGG_bnEYSPzMg5dUHCa63n3g@mail.gmail.com>
 <87o6f0tvbf.fsf@fifthhorseman.net>
 <CAFh6oAyA0jzmBJYJ6CRDkG3OYUpuGO4S=GkQvK_ETddcy11XDA@mail.gmail.com>
Message-ID: <87cxvftih8.fsf@fifthhorseman.net>

Thanks, kernc.

fwiw, i've applied this patch to pinentry in debian unstable.  I hope
upstream will consider it.

Regards,

         --dkg

On Tue 2026-08-18 04:22:52 +0200, Kernc wrote:
> By default, GLib/Gcr/libsecret outputs debug/info logging messages
> to stdout, but we use that as the Assuan channel, and outputting to
> it anything but the expected verbs breaks pinentry pipelines
> in confusing ways.
>
> It is unknown whether a similar patch is needed for gtk-2
> or other flavors via the 'CLEARPASSPHRASE' command,
> nor if G_MESSAGES_DEBUG needs unsetting from the environment.
>
> An old user reports Gtk-warnings even with pinentry-qt,
> but their issue needs more verification.
>
> https://web.archive.org/web/20260629091849/https://dev.gnupg.org/T4144.html
>
> Care must be placed in who inherits our Assuan fds
> and what they do with them.
>
> GnuPG-bug-id: 4144
> GnuPG-bug-id: 2243
> GnuPG-bug-id: 2397
> Signed-off-by: Kernc <kerncece at gmail.com>
> ---
>  gnome3/pinentry-gnome3.c | 7 +++++++
>  1 file changed, 7 insertions(+)
>
> diff --git a/gnome3/pinentry-gnome3.c b/gnome3/pinentry-gnome3.c
> index 7f21d6f..3692f49 100644
> --- a/gnome3/pinentry-gnome3.c
> +++ b/gnome3/pinentry-gnome3.c
> @@ -518,6 +518,13 @@ main (int argc, char *argv[])
>  {
>    pinentry_init (PGMNAME);
>
> +/* Prevent logging messages escaping to stdout (our Assuan channel). */
> +#if GLIB_CHECK_VERSION (2, 68, 0)
> +  g_log_writer_default_set_use_stderr (TRUE);
> +#else
> +  g_unsetenv ("G_MESSAGES_DEBUG");
> +#endif
> +
>  #ifdef FALLBACK_CURSES
>    if (!getenv ("DBUS_SESSION_BUS_ADDRESS"))
>      {
> -- 
> 2.47.3
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 324 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260818/824fb8e3/attachment.sig>

From simon at josefsson.org  Sun Aug 23 13:24:34 2026
From: simon at josefsson.org (Simon Josefsson)
Date: Sun, 23 Aug 2026 13:24:34 +0200
Subject: Make it possible to build production GnuPG's from git tags
Message-ID: <87ik51m64t.fsf@josefsson.org>

Hi

There is a discussion in the Guix community about building GnuPG
directly from git tags:

https://codeberg.org/guix/guix/issues/10622

What do you think about making it possible to build GnuPG's intended for
production use from git tags?

I see two things that would help, besides the necessary autoconf
source-code tweaking:

1) Declaring some public git server (or mirror) as officially supported,
one that doesn't fall over due to AI scrapers.

-and/or-

2) Publishing 'git-archive' tarballs, which could be used as long-term
archival copies of the git repository in case it goes away.  They would
contain the exact same content as git tag but without the .git
sub-directory.  Typically created like this:

   git archive --prefix=gnupg-v2.5.21/ -o gnupg-v2.5.21-src.tar.gz v2.5.21

or programmatically something like:

   git archive --prefix=gnupg-$(git describe)/ -o gnupg-$(git describe)-src.tar.gz $(git describe)

which also works for non-releases.  This is the same as various forges
publishes as their "download git" tarball links, modulo leading path and
naming differences.  Of course, GPG signing them would be useful.

I'm doing 2) for several GNU tools, published as foo-v1.2.3-src.tar.gz
tarballs.  Some notes:
https://blog.josefsson.org/2024/04/01/towards-reproducible-minimal-source-code-tarballs-please-welcome-src-tar-gz/

/Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1287 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260823/c4431650/attachment-0001.sig>

From glaubitz at physik.fu-berlin.de  Mon Aug 24 11:10:43 2026
From: glaubitz at physik.fu-berlin.de (John Paul Adrian Glaubitz)
Date: Mon, 24 Aug 2026 11:10:43 +0200
Subject: libgpg-error t-printf test fails on powerpc and ppc64
Message-ID: 
 <44ef69787a3367ce448dc6cb00142adee3d860a6.camel@physik.fu-berlin.de>

Hi,

the t-printf test fails on both powerpc and ppc64 (both big-endian):

t-printf: format "%.100Lf" with LDBL_MAX unexpectly did not fail
FAIL: t-printf

powerpc: https://buildd.debian.org/status/fetch.php?pkg=libgpg-error&arch=powerpc&ver=1.61-3&stamp=1787306766&raw=0
ppc64: https://buildd.debian.org/status/fetch.php?pkg=libgpg-error&arch=ppc64&ver=1.61-3&stamp=1787560268&raw=0

I think this might related to this gnulib issue:

- https://github.com/linuxppc/issues/issues/494
- https://lists.gnu.org/archive/html/bug-gnulib/2025-07/msg00021.html

Could someone look into this, please?

I tried opening a bug report, but it's currently locked out due to AI scraping.

If anyone needs a machine for testing, there is cfarm121 in the GCC Compile Farm

https://gcc.gnu.org/wiki/CompileFarm

which runs Debian unstable on ppc64 (big-endian) which I am the administrator of.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

From gniibe at fsij.org  Tue Aug 25 05:01:05 2026
From: gniibe at fsij.org (NIIBE Yutaka)
Date: Tue, 25 Aug 2026 12:01:05 +0900
Subject: libgpg-error t-printf test fails on powerpc and ppc64
In-Reply-To: 
 <44ef69787a3367ce448dc6cb00142adee3d860a6.camel@physik.fu-berlin.de>
References: 
 <44ef69787a3367ce448dc6cb00142adee3d860a6.camel@physik.fu-berlin.de>
Message-ID: <87mruax5se.fsf@haruna.fsij.org>

Hello,

John Paul Adrian Glaubitz <glaubitz at physik.fu-berlin.de> wrote:
> the t-printf test fails on both powerpc and ppc64 (both big-endian):
>
> t-printf: format "%.100Lf" with LDBL_MAX unexpectly did not fail
> FAIL: t-printf

This issue was reported to gnupg-users.

    https://lists.gnupg.org/pipermail/gnupg-users/2026-July/068440.html

I pushed a fix (to libgpg-error master) before my vacation:

	9cc750a816554e46d3e1496533f927b17ef3fcef

Today, I tested on perotto.debian.net and confirmed that:

	t-printf: IBM double-double - skipping LDBL_MAX test

The test is skipped correctly.

Thus, please wait for the next release of 1.62, or apply the commit
locally.
-- 

From ametzler at bebt.de  Tue Aug 25 18:37:06 2026
From: ametzler at bebt.de (Andreas Metzler)
Date: Tue, 25 Aug 2026 18:37:06 +0200
Subject: [patch] Fix gpgmepy build error against swig 4.5.0
Message-ID: <ao3Essgxlb0kDwL1@argenau.bebt.de>

Hello,

gpgmepy 2.0 fails to build with 4.5.0 with:
creating python3.13-gpg/temp.linux-amd64-cpython-313/python3.13-gpg
x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -Wcast-align -Wshadow -Wstrict-prototypes -Wno-format-y2k -Wno-missing-field-initializers -Wno-sign-compare -Wno-format-zero-length -Wno-format-truncation -Wno-sizeof-pointer-div -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Ipython3.13-gpg -I/<<PKGBUILDDIR>>/build -I/usr/include/python3.13 -c python3.13-gpg/gpgme_wrap.c -o python3.13-gpg/temp.linux-amd64-cpython-313/python3.13-gpg/gpgme_wrap.o
python3.13-gpg/gpgme_wrap.c: In function ‘_wrap_gpgme_data_seek’:
python3.13-gpg/gpgme_wrap.c:4085:14: error: implicit declaration of function ‘PyInt_Check’; did you mean ‘PySet_Check’? [-Wimplicit-function-declaration]
 4085 |     else if (PyInt_Check(swig_obj[1]))
      |              ^~~~~~~~~~~
      |              PySet_Check
[...]

(Originally reported in https://bugs.debian.org/1145351 )

Please find attached a suggested patch by Rafael Laboissière.

cu Andreas
-- 
"You people are noisy," Nia said.
I made the gesture of agreement.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0030-build-with-swig-4.5.0.patch
Type: text/x-diff
Size: 1847 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260825/1d98f7f9/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260825/1d98f7f9/attachment.sig>

From gniibe at fsij.org  Wed Aug 26 04:16:52 2026
From: gniibe at fsij.org (NIIBE Yutaka)
Date: Wed, 26 Aug 2026 11:16:52 +0900
Subject: libgpg-error t-printf test fails on powerpc and ppc64
In-Reply-To: <87mruax5se.fsf@haruna.fsij.org>
References: 
 <44ef69787a3367ce448dc6cb00142adee3d860a6.camel@physik.fu-berlin.de>
 <87mruax5se.fsf@haruna.fsij.org>
Message-ID: <87o6epy6az.fsf@haruna.fsij.org>

Hello, again,

NIIBE Yutaka <gniibe at fsij.org> wrote:
> I pushed a fix (to libgpg-error master) before my vacation:
>
> 	9cc750a816554e46d3e1496533f927b17ef3fcef
>
> Today, I tested on perotto.debian.net and confirmed that:
>
> 	t-printf: IBM double-double - skipping LDBL_MAX test
>
> The test is skipped correctly.

I realized that my change was not good.  It only cares about 64-bit
machine (reported in July), but it is also relevant to 32-bit machine
(as you reported).

I pushed another commit to cover powerpc (32-bit):

	747eb8798bed752ede9b4cec03507e64bf6a497a

(Well, we could only test by LDBL_MANT_DIG == 106.  But I don't want to
encourage such a situation for an architecture in the future.  We will
need to change again when such a situation will occur.)
-- 

From glaubitz at physik.fu-berlin.de  Wed Aug 26 07:17:15 2026
From: glaubitz at physik.fu-berlin.de (John Paul Adrian Glaubitz)
Date: Wed, 26 Aug 2026 07:17:15 +0200
Subject: libgpg-error t-printf test fails on powerpc and ppc64
In-Reply-To: <87o6epy6az.fsf@haruna.fsij.org>
References: 
	<44ef69787a3367ce448dc6cb00142adee3d860a6.camel@physik.fu-berlin.de>
	 <87mruax5se.fsf@haruna.fsij.org> <87o6epy6az.fsf@haruna.fsij.org>
Message-ID: 
 <9013c0a5cbf74fcd5ae0c9bc17340d92763d0af0.camel@physik.fu-berlin.de>

Hi Yutaka,

On Wed, 2026-08-26 at 11:16 +0900, NIIBE Yutaka wrote:
> I realized that my change was not good.  It only cares about 64-bit
> machine (reported in July), but it is also relevant to 32-bit machine
> (as you reported).
> 
> I pushed another commit to cover powerpc (32-bit):
> 
> 	747eb8798bed752ede9b4cec03507e64bf6a497a
> 
> (Well, we could only test by LDBL_MANT_DIG == 106.  But I don't want to
> encourage such a situation for an architecture in the future.  We will
> need to change again when such a situation will occur.)

Thanks a lot for the original fix and the follow-up fix, appreciate the
very quick action! Hope I can invite you for cold beverage next year
when I'm back in Japan. ;-)

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913