On 2024-05-10 Andreas Metzler wrote:
[...]
> However that was quite painful. codesearch.debian.net lists 78 packages
> matching libgcrypt-config. I suspect the majority will be using the
> macros from libgcrypt.m4 and therefore already use gpgrt-config but
> I also suspect that about a quarter of
On 2024-05-09 Alex Henrie wrote:
> This packaging bug is a big problem for Proton's Wine fork, which
> needs both /usr/lib/i386-linux-gnu/libgcrypt.so and
> /usr/lib/x86_64-linux-gnu/libgcrypt.so to be available at build time.
> Currently, Proton built for Debian can only support ECDH in 32-bit
>
This packaging bug is a big problem for Proton's Wine fork, which
needs both /usr/lib/i386-linux-gnu/libgcrypt.so and
/usr/lib/x86_64-linux-gnu/libgcrypt.so to be available at build time.
Currently, Proton built for Debian can only support ECDH in 32-bit
games or 64-bit games, but not both. See
htt
Until this is fixed by the Debian GnuTLS Maintainers, I use a
workaround for cross development:
- Unpack the .debs for native architecture (here: amd64) and
the archtectures for cross building (here: armel and armhf)
- Add "Multi-Arch: same" to the control file of each package
- Remove the e
Package: libgcrypt20-dev
Version: 1.6.3-2
Followup-For: Bug #714589
Dear Maintainer,
This bug is still present in the new libgcrypt20-dev package. Here are the
issues I noticed:
* dumpsexp and hmac256 binaries.
A possible solution would be to move them to a separate Multi-Arch: foreign
Package: libgcrypt11-dev
Version: 1.5.0-5
I would like to request that mult-arch be supported by libgcrypt11-dev.
6 matches
Mail list logo
