Closed #968 via #969.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/968#event-2857373584___
Rpm-maint mailing list
Yes, that works too.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/968#issuecomment-561739087___
Rpm-maint mailing list
libgcrypt 1.8.5. Rebuilding now...
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/968#issuecomment-561708225___
Rpm-maint
What libgcrypt version are you using?
The gcrypt code seems to indicate that GCRYCTL_SET_THREAD_CBS is nowadays a
dummy call that just calls gcrypt's global_init() function. So does
```
gcry_control (GCRYCTL_INITIALIZATION_FINISHED, 0);
```
also work for you?
--
You are receiving this because
Looks like this patch solves the problem for me:
```
diff --git a/rpmio/digest_libgcrypt.c b/rpmio/digest_libgcrypt.c
index b31fda569..3ec2082cf 100644
--- a/rpmio/digest_libgcrypt.c
+++ b/rpmio/digest_libgcrypt.c
@@ -19,8 +19,10 @@ struct DIGEST_CTX_s {
/ init
A colleague who knows more than me pointed out that this implies the use of
libgcrypt in RPM (or libgcrypt itself) is not thread-safe, as the libgomp
references show it is writing packages in parallel.
--
You are receiving this because you are subscribed to this thread.
Reply to this email
With 4.15.1 using NSS I can build packages, but with libgcrypt RPM crashes:
```
#0 0x7fd087a2414a in dataLength (type=type@entry=8,
p=p@entry=0x7fd07ec22c08, count=0,
count@entry=1, onDisk=onDisk@entry=0, pend=pend@entry=0x0) at
../../git/lib/header.c:462
#1 0x7fd087a247fb in
