Page MenuHome GnuPG

thesamesam (sam)
User

Projects

User Details

User Since
Jan 29 2021, 9:30 PM (181 w, 1 d)
Availability
Available

Recent Activity

Mar 23 2024

thesamesam added a comment to T7003: 2.2 gpg-agent doesn't allow KEYINFO when restricted (was: gpgme-1.23.2 test failure (t-json)).

Thanks, that patch works for me.

Mar 23 2024, 12:24 PM · gpgagent, gnupg22, gpgme, Gentoo, Bug Report

Mar 18 2024

thesamesam added a comment to T7031: New pinentry release for Qt 6 support?.

Thank you!

Mar 18 2024, 3:58 PM · KF6, qt, pinentry, Feature Request

Mar 14 2024

thesamesam added a project to T7031: New pinentry release for Qt 6 support?: KF6.
Mar 14 2024, 4:26 AM · KF6, qt, pinentry, Feature Request

Mar 7 2024

thesamesam added a comment to T7031: New pinentry release for Qt 6 support?.

I should say: I can ship a snapshot in Gentoo if that's okay, but I'd prefer not to.

Mar 7 2024, 8:10 PM · KF6, qt, pinentry, Feature Request
thesamesam created T7031: New pinentry release for Qt 6 support?.
Mar 7 2024, 8:08 PM · KF6, qt, pinentry, Feature Request

Mar 4 2024

thesamesam added a comment to T7022: libgcrypt-1.10.3 regression on hppa.

Thank you!

Mar 4 2024, 3:46 AM · libgcrypt, Gentoo, hppa, Bug Report

Feb 29 2024

thesamesam added a comment to T5664: npth-1.6: error: unknown type name ‘pthread_rwlock_t’.

@gniibe Thank you very much! That works.

Feb 29 2024, 7:56 AM · npth, Bug Report
thesamesam added a comment to T7003: 2.2 gpg-agent doesn't allow KEYINFO when restricted (was: gpgme-1.23.2 test failure (t-json)).

No, thank you both for the speedy responses :)

Feb 29 2024, 7:40 AM · gpgagent, gnupg22, gpgme, Gentoo, Bug Report
thesamesam added a comment to T7003: 2.2 gpg-agent doesn't allow KEYINFO when restricted (was: gpgme-1.23.2 test failure (t-json)).

Ah, thanks Werner, I'll keep that in mind.

Feb 29 2024, 3:15 AM · gpgagent, gnupg22, gpgme, Gentoo, Bug Report
thesamesam added a comment to T5664: npth-1.6: error: unknown type name ‘pthread_rwlock_t’.

This seems to have regressed musl support, per https://bugs.gentoo.org/925443.

Feb 29 2024, 3:03 AM · npth, Bug Report

Feb 28 2024

thesamesam added a project to T7003: 2.2 gpg-agent doesn't allow KEYINFO when restricted (was: gpgme-1.23.2 test failure (t-json)): gpgme.
Feb 28 2024, 4:40 AM · gpgagent, gnupg22, gpgme, Gentoo, Bug Report

Feb 27 2024

thesamesam added a project to T7022: libgcrypt-1.10.3 regression on hppa: Gentoo.
Feb 27 2024, 7:17 PM · libgcrypt, Gentoo, hppa, Bug Report
thesamesam updated subscribers of T7022: libgcrypt-1.10.3 regression on hppa.

cc @jukivili @gniibe

Feb 27 2024, 7:16 PM · libgcrypt, Gentoo, hppa, Bug Report

Feb 20 2024

thesamesam added a comment to T7003: 2.2 gpg-agent doesn't allow KEYINFO when restricted (was: gpgme-1.23.2 test failure (t-json)).

It seems to pass for me with gnupg-2.2.41 but fails with gnupg-2.2.42?

Feb 20 2024, 6:51 AM · gpgagent, gnupg22, gpgme, Gentoo, Bug Report
thesamesam created T7003: 2.2 gpg-agent doesn't allow KEYINFO when restricted (was: gpgme-1.23.2 test failure (t-json)).
Feb 20 2024, 6:41 AM · gpgagent, gnupg22, gpgme, Gentoo, Bug Report

Feb 15 2024

thesamesam added a comment to T6997: gnupg-2.4.4 breaks dirmngr fetching keys via hkps:// from behind a proxy.

Per https://dev.gnupg.org/rG04cbc3074aa98660b513a80f623a7e9f0702c7c9#83517, it looks like the fix might be incomplete?

Feb 15 2024, 10:43 PM · gnupg24 (gnupg-2.4.5), gnupg22, Bug Report

Dec 22 2023

gniibe awarded T6892: libgcrypt-1.10.3 build failure on x86 with -Og a Yellow Medal token.
Dec 22 2023, 3:02 AM · libgcrypt, Bug Report

Dec 15 2023

thesamesam created T6892: libgcrypt-1.10.3 build failure on x86 with -Og.
Dec 15 2023, 7:10 AM · libgcrypt, Bug Report

Oct 28 2023

thesamesam added a comment to T6778: gpgme-1.23.1 tests fail with gnupg configured without tofu.

I did this locally:

--- a/lang/python/tests/support.py
+++ b/lang/python/tests/support.py
@@ -46,13 +46,15 @@ def is_gpg_version(version):
Oct 28 2023, 5:19 AM · gpgme, Gentoo, Bug Report
thesamesam created T6778: gpgme-1.23.1 tests fail with gnupg configured without tofu.
Oct 28 2023, 5:06 AM · gpgme, Gentoo, Bug Report

Sep 1 2023

thesamesam added a comment to T6556: gpgtar: Removes existing output file on error.

Thanks. For the record, done at https://lists.gnupg.org/pipermail/gnupg-users/2023-August/066692.html.

Sep 1 2023, 5:15 AM · gnupg22, gnupg24, Restricted Project, gpgtar, Bug Report

Aug 21 2023

thesamesam added a comment to T6673: gpgme-1.22.0 fails to compile tests (when building in source tree).

I'll swap us over to out of source build for this as well. I've been doing it gradually for the gpg suite. Thanks.

Aug 21 2023, 9:23 PM · gpgme, Bug Report
thesamesam added a comment to T6673: gpgme-1.22.0 fails to compile tests (when building in source tree).

Aug 21 2023, 8:30 PM · gpgme, Bug Report
thesamesam created T6673: gpgme-1.22.0 fails to compile tests (when building in source tree).
Aug 21 2023, 8:29 PM · gpgme, Bug Report

Jul 6 2023

thesamesam added a comment to T6579: gnupg-2.4.3 build failure.

Thanks. Wouldn't that require OpenLDAP on every system with gnupg?

Jul 6 2023, 1:58 AM · gnupg24, Gentoo, Bug Report

Jul 4 2023

thesamesam created T6579: gnupg-2.4.3 build failure.
Jul 4 2023, 7:45 PM · gnupg24, Gentoo, Bug Report

Jun 10 2023

thesamesam added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

Ah, I see https://dev.gnupg.org/rG2f872fa68c6576724b9dabee9fb0844266f55d0d applies cleanly. I guess can go with that, although would prefer it if on the 2.4 branch.

Jun 10 2023, 11:00 PM · Emacs, gnupg, Bug Report
thesamesam added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

Is there a commit we could backport downstream to 2.4.x? We've had quite a few reports of this.

Jun 10 2023, 10:56 PM · Emacs, gnupg, Bug Report

Dec 20 2022

thesamesam added a comment to T6313: 2.4.0 does not support in-source-tree builds.

Sorry, one more thing: I should use out of source builds for all gnupg software (libgpg-error, libksba, etc)? It's fine if so, just want to check what the policy is.

Dec 20 2022, 11:28 AM · gnupg24, workaround, Bug Report
thesamesam added a comment to T6313: 2.4.0 does not support in-source-tree builds.

Ah, thanks! I didn't know this was unsupported. I'll change what we're doing.

Dec 20 2022, 11:22 AM · gnupg24, workaround, Bug Report
thesamesam updated the task description for T6313: 2.4.0 does not support in-source-tree builds.
Dec 20 2022, 10:59 AM · gnupg24, workaround, Bug Report
thesamesam created T6313: 2.4.0 does not support in-source-tree builds.
Dec 20 2022, 10:59 AM · gnupg24, workaround, Bug Report

Sep 9 2022

thesamesam closed T6193: Build failure with Clang 15 (pinentry-curses.c, error: call to undeclared function 'addnwstr' ...) as Invalid.

Thanks for your help @gniibe and apologies for wasting your time. It looks like this is an issue with ncurses on musl systems and I'll pursue it there. I have a patch to their configure which works & fixes building pinentry.

Sep 9 2022, 3:21 AM · clang, Gentoo, pinentry, Bug Report
thesamesam added a comment to T6193: Build failure with Clang 15 (pinentry-curses.c, error: call to undeclared function 'addnwstr' ...).

I've reported it on bug-ncurses@ to get some insight: https://marc.info/?l=ncurses-bug&m=166268018624805&w=2.

Sep 9 2022, 1:43 AM · clang, Gentoo, pinentry, Bug Report
thesamesam added a comment to T6193: Build failure with Clang 15 (pinentry-curses.c, error: call to undeclared function 'addnwstr' ...).

Mysteriously, I get nothing:

$ pkg-config --cflags nurses
Sep 9 2022, 1:01 AM · clang, Gentoo, pinentry, Bug Report

Sep 8 2022

thesamesam added projects to T6193: Build failure with Clang 15 (pinentry-curses.c, error: call to undeclared function 'addnwstr' ...): Gentoo, clang.
Sep 8 2022, 1:40 AM · clang, Gentoo, pinentry, Bug Report
thesamesam set External Link to https://bugs.gentoo.org/869128 on T6193: Build failure with Clang 15 (pinentry-curses.c, error: call to undeclared function 'addnwstr' ...).
Sep 8 2022, 1:19 AM · clang, Gentoo, pinentry, Bug Report
thesamesam added a comment to T6193: Build failure with Clang 15 (pinentry-curses.c, error: call to undeclared function 'addnwstr' ...).

It looks like there was a problem similar to this a while ago: https://dev.gnupg.org/T2320 where it turned out for unicode ncurses builds, a specific header had to be included, but that workaround seems to have been removed from pinentry since.

Sep 8 2022, 1:17 AM · clang, Gentoo, pinentry, Bug Report
thesamesam created T6193: Build failure with Clang 15 (pinentry-curses.c, error: call to undeclared function 'addnwstr' ...).
Sep 8 2022, 1:17 AM · clang, Gentoo, pinentry, Bug Report

Aug 25 2022

thesamesam added a comment to T6160: pinentry Emacs support assumes socket location at ${TMPDIR}/emacs${UID}, fails to connect (need to respect XDG_RUNTIME_DIR).

That's a fair point, cheers!

Aug 25 2022, 9:49 AM · Feature Request, pinentry, Emacs
thesamesam added a comment to T6161: pinentry doesn't allow disabling various library linkages (libX11, KF5WaylandClient, Qt5X11Extras).

I'm not sure I understand. If you don't want pinentries depending on libX11, then simply disable those pinentries with --disable-pinentry-qt5, etc. For Wayland it may make sense to allow disabling it.

Aug 25 2022, 9:43 AM · pinentry, Feature Request
thesamesam created T6161: pinentry doesn't allow disabling various library linkages (libX11, KF5WaylandClient, Qt5X11Extras).
Aug 25 2022, 9:02 AM · pinentry, Feature Request
thesamesam updated the task description for T6160: pinentry Emacs support assumes socket location at ${TMPDIR}/emacs${UID}, fails to connect (need to respect XDG_RUNTIME_DIR).
Aug 25 2022, 8:54 AM · Feature Request, pinentry, Emacs
thesamesam changed External Link from https://bugs.gentoo.org/794649 to https://debbugs.gnu.org/33847 on T6160: pinentry Emacs support assumes socket location at ${TMPDIR}/emacs${UID}, fails to connect (need to respect XDG_RUNTIME_DIR).
Aug 25 2022, 8:54 AM · Feature Request, pinentry, Emacs
thesamesam changed External Link from https://bugs.gentoo.org/794649) to https://bugs.gentoo.org/794649 on T6160: pinentry Emacs support assumes socket location at ${TMPDIR}/emacs${UID}, fails to connect (need to respect XDG_RUNTIME_DIR).
Aug 25 2022, 8:53 AM · Feature Request, pinentry, Emacs
thesamesam set External Link to https://bugs.gentoo.org/794649) on T6160: pinentry Emacs support assumes socket location at ${TMPDIR}/emacs${UID}, fails to connect (need to respect XDG_RUNTIME_DIR).
Aug 25 2022, 8:53 AM · Feature Request, pinentry, Emacs
thesamesam created T6160: pinentry Emacs support assumes socket location at ${TMPDIR}/emacs${UID}, fails to connect (need to respect XDG_RUNTIME_DIR).
Aug 25 2022, 8:53 AM · Feature Request, pinentry, Emacs

Jun 15 2022

thesamesam added a comment to T5976: libgcrypt build failure on HPPA 1.1 (./.libs/libgcrypt.so: undefined reference to `__udiv_qrnnd').

Thanks! Interestingly didn't seem to work with 1.9.x but it does with 1.10x. Maybe I made some error when testing.

Jun 15 2022, 8:12 PM · backport, hppa, libgcrypt, Gentoo, Bug Report

May 14 2022

thesamesam added a comment to T5976: libgcrypt build failure on HPPA 1.1 (./.libs/libgcrypt.so: undefined reference to `__udiv_qrnnd').

Okay, confirmed: I was just wrong and the build failure was only ever with --disable-asm (i.e. the log in this bug is the only relevant one). Patch works.

May 14 2022, 3:54 AM · backport, hppa, libgcrypt, Gentoo, Bug Report

May 13 2022

thesamesam added a watcher for hppa: thesamesam.
May 13 2022, 8:16 AM
thesamesam added a comment to T5976: libgcrypt build failure on HPPA 1.1 (./.libs/libgcrypt.so: undefined reference to `__udiv_qrnnd').

Thank you for your fast reply. My apologies - I should have thought to do that (share log with asm enabled)! But now I'm confused. I think the failure was only ever with asm disabled. I will check with somebody else tomorrow just to make sure though.

May 13 2022, 4:55 AM · backport, hppa, libgcrypt, Gentoo, Bug Report
thesamesam updated the task description for T5976: libgcrypt build failure on HPPA 1.1 (./.libs/libgcrypt.so: undefined reference to `__udiv_qrnnd').
May 13 2022, 12:03 AM · backport, hppa, libgcrypt, Gentoo, Bug Report
thesamesam renamed T5976: libgcrypt build failure on HPPA 1.1 (./.libs/libgcrypt.so: undefined reference to `__udiv_qrnnd') from libgcrypt build failure on HPPA 1.1 () to libgcrypt build failure on HPPA 1.1 (./.libs/libgcrypt.so: undefined reference to `__udiv_qrnnd').
May 13 2022, 12:03 AM · backport, hppa, libgcrypt, Gentoo, Bug Report

May 12 2022

thesamesam added a comment to T5976: libgcrypt build failure on HPPA 1.1 (./.libs/libgcrypt.so: undefined reference to `__udiv_qrnnd').

Full build.log:

. Happy to get more information if you tell us what's needed. Hardware access can be given over SSH too.

May 12 2022, 11:46 PM · backport, hppa, libgcrypt, Gentoo, Bug Report
thesamesam created T5976: libgcrypt build failure on HPPA 1.1 (./.libs/libgcrypt.so: undefined reference to `__udiv_qrnnd').
May 12 2022, 11:45 PM · backport, hppa, libgcrypt, Gentoo, Bug Report

Apr 27 2022

werner awarded T5948: Flaky test (<keyboxd>tests/openpgp/use-exact-key.scm) failure with gnupg 2.3.5, 2.3.6 a Cup of Joe token.
Apr 27 2022, 8:34 AM · gnupg (gpg23), Bug Report

Apr 25 2022

thesamesam added a comment to T5948: Flaky test (<keyboxd>tests/openpgp/use-exact-key.scm) failure with gnupg 2.3.5, 2.3.6.

After re-running myself a few times, I managed to hit it again. In tests/openpgp/report.xml, I see:

[...]
<testsuite name="&lt;keyboxd&gt;tests/openpgp/use-exact-key.scm" time="0" package="&lt;keyboxd&gt;tests/openpgp" id="0" timestamp="2022-04-25T16:18:27" hostname="unknown" tests="1" failures="0" errors="0" >
<properties/>
<testcase name="use-exact-key.scm" classname="&lt;keyboxd&gt;tests.openpgp" time="0" >
<failure message="Unknown error." />
</testcase>
<system-out>
Importing public key.
Checking that the most recent, valid signing subkey is used by default
    &gt; 8BC90111 3E880CFF F5F77B83 45117079 1EA97479 &lt;
Checking that we can select a specific signing key
    &gt; 8BC90111 F5F77B83 1EA97479 &lt;
</system-out>
<system-err>
</system-err>
[...]
Apr 25 2022, 6:20 PM · gnupg (gpg23), Bug Report
thesamesam created T5948: Flaky test (<keyboxd>tests/openpgp/use-exact-key.scm) failure with gnupg 2.3.5, 2.3.6.
Apr 25 2022, 6:14 PM · gnupg (gpg23), Bug Report

Feb 17 2022

thesamesam added a comment to T5834: C++ ABI breakage in gpgme-1.17.0?.

Yeah, please do issue a new release as soon as possible if you can, as otherwise downstream we're in an awkward position where we have to rebuild everything without a SONAME bump, then do it again once the release is out.

Feb 17 2022, 12:33 AM · Bug Report

Feb 15 2022

thesamesam added a comment to T5834: C++ ABI breakage in gpgme-1.17.0?.

I assumed that changes to internal classes wouldn't break the ABI, but apparently the symbols were still exported. I'll keep this in mind for the next release.

FWIW, the internal class in question was completely rewritten. Since the damage has been done already, I'll close this report. We won't readd symbols to dead code. Sorry, for the inconvenience.

Feb 15 2022, 5:02 PM · Bug Report
thesamesam added a watcher for Release Info: thesamesam.
Feb 15 2022, 3:39 AM

Feb 14 2022

thesamesam set External Link to https://bugs.kde.org/show_bug.cgi?id=449891 on T5834: C++ ABI breakage in gpgme-1.17.0?.
Feb 14 2022, 10:14 PM · Bug Report
thesamesam created T5834: C++ ABI breakage in gpgme-1.17.0?.
Feb 14 2022, 10:13 PM · Bug Report

Jan 22 2022

thesamesam created T5796: libgcrypt-1.9.4 build failure on ARM without NEON.
Jan 22 2022, 5:02 AM · arm, libgcrypt, Gentoo, Bug Report

Jan 17 2022

thesamesam updated subscribers of T5785: libgcrypt-1.9.4 build failure on ppc64le.

On behalf of @gyakovlev (pending approval for his account):

[03:05:23]  <@gyakovlev>  AC_DEFINE(HAVE_COMPATIBLE_CC_PPC_ALTIVEC,1,
[03:05:23]  <@gyakovlev>         [Defined if underlying compiler supports PowerPC AltiVec/VSX/crypto intrinsics])
[03:05:34]  <@gyakovlev> they should definitely check for __POWER8_VECTOR__ 1
[03:05:44]  <@gyakovlev> it's not plain altivec
[03:06:52]  <@gyakovlev> that power check should check for __POWER8_VECTOR__
[03:06:52]  <@gyakovlev> not only for what they check already.
[03:08:59]  <@gyakovlev> it probably should be checked after __powerpc64__ or instead of it.
Jan 17 2022, 4:09 AM · Gentoo, Bug Report
thesamesam added a project to T5785: libgcrypt-1.9.4 build failure on ppc64le: Gentoo.
Jan 17 2022, 3:34 AM · Gentoo, Bug Report
thesamesam added a comment to T5785: libgcrypt-1.9.4 build failure on ppc64le.

Looks like it's triggered if e.g. -mcpu=power9 isn't in CFLAGS.

Jan 17 2022, 3:34 AM · Gentoo, Bug Report
thesamesam added a comment to T5785: libgcrypt-1.9.4 build failure on ppc64le.

Build log here:

Jan 17 2022, 3:32 AM · Gentoo, Bug Report
thesamesam created T5785: libgcrypt-1.9.4 build failure on ppc64le.
Jan 17 2022, 3:31 AM · Gentoo, Bug Report

Oct 29 2021

thesamesam added a watcher for MacOS: thesamesam.
Oct 29 2021, 8:04 PM
thesamesam added a member for Gentoo: thesamesam.
Oct 29 2021, 7:59 PM

Jan 30 2021

thesamesam added a comment to T5277: libgcrypt 1.9.1 fails to build with --disable-asm.

@jukivili Thanks for the reply! We've reverted that commit downstream in Gentoo as a temporary workaround, as due to some complications, our release systems needed to build without asm (for now) to ensure portability. Rest assured, this is not the default, and is discouraged for regular users.

Jan 30 2021, 12:17 PM · MacOS, libgcrypt, Bug Report