In most cases, I guess that code being compiled against ubuntu's libgcrypt is also compiled against some other library in /usr/lib/<arch triplet>/, which allowed this bug to remain unnoticed so far.
In most cases, I guess that code being compiled against ubuntu's libgcrypt is also compiled against some other library in /usr/lib/<arch triplet>/, which allowed this bug to remain unnoticed so far.