[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Please test: scrypt 1.3.2.99
On 2025-02-06, Simon Josefsson wrote:
> Graham Percival <gperciva@tarsnap.com> writes:
>
> > I'm a bit puzzled by that... debian/control includes
> > Deepends: ${shlibs:Depends}, ${misc:Depends}
> > for scrypt, libscrypt-kdf1, and libscrypt-kdf-dev. So why does it only
> > only warn about libscrypt-kdf-dev?
>
> I think that libscrypt-kdf-dev package should Depends: libscrypt-kdf1 (=
> ${binary:Version}) instead of ${shlibs:Depends}.
That sounds plausible to me, but I'm far from an expert about debian
packaging.
> Generally, you should
> also add *-dev packages for each of the shared libraries needed (but for
> libscrypt-kdf1 there doesn't appear to be any, though).
It also needs libcrypto (part of the libssl3 package, but probably best
to depend on libssl-dev so we get headers as well)
$ grep "dependency_libs=" libscrypt-kdf.la
dependency_libs=' -lcrypto'
$ ldd .libs/libscrypt-kdf.so
.libs/libscrypt-kdf.so:
libcrypto.so.30 => /lib/libcrypto.so.30 (0x2b929971e000)
libc.so.7 => /lib/libc.so.7 (0x2b9297b7e000)
libthr.so.3 => /lib/libthr.so.3 (0x2b929a36a000)
(libc and libthr are assumed to be present on the system already)
Thanks for the packaging!
Cheers,
- Graham