On 2012-11-16 Martijn van Brummelen <mart...@brumit.nl> wrote: [...] > How about contacting upstream? I can try > that, or perhaps you already had contact with Werner Koch?
Hello Martijn, I have hasked Werner about it. http://permalink.gmane.org/gmane.comp.encryption.gpg.libgcrypt.devel/2623 Werner said this about the patch: | Okay, if that works, fine. It might break other things; I don't know. | There are enough selftests to hopefully detect such a break (in | particular in FIPS mode). The issue should be solved in 1.6: | Although we can't solve all the problems we will be able to solve the | thread initialization problem. Libgcrypt 1.6 will ignore the thread | callbacks and assume pthread. Semaphores are then used for locking | and provide a way to do thread-safe initialization. The hopefully minor | drawback is that one needs to link against librt. > I tried the 1.5.0-beta1 but that did not solve the problem. I think 1.5.0-beta1 << 1.5.0. cu andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
