Hi Daniel,
Indeed, I am running Debian stable on my server with just netatalk and
some of its dependencies from testing, so my setup is a bit unconventional.
This is in fact the case because Netatalk was dropped from Debian 12,
and I didn't want to keep running the old version which has a security
issue.
However, I think installing netatalk from any Debian version should
still pull in the correct version of libgcrypt. Isn't that something
that can be addressed in the netatalk package? I can imagine later
versions of netatalk would need still newer versions of libgcrypt. The
current dependency specification would fail to pull those in.
Kind regards,
Matijs van Zuijlen
On 01/12/2023 00:42, Daniel Markstedt wrote:
Hi Matijs,
This is not something we can address in the netatalk package itself, since
you're using an Unstable netatalk package with a Stable Debian version.
(Netatalk was dropped from Debian 12 Bookworm.)
See this upstream discussion for more details:
https://github.com/Netatalk/netatalk/discussions/574
Best regards,
Daniel
On Thursday, November 30th, 2023 at 11:05 PM, Matijs van Zuijlen
wrote:
Dear maintainer,
This problem still exists. I installed netatalk from testing on a Debian
server running stable, and libgcrypt was not updated at the same time
because the dependency in the netatalk package specifies '>= 1.10.0',
which matches the stable version 1.10.1, while testing's netatalk
actually needs libgcrypt 1.10.2. This lead to a flood of errors in the
logs. Updating the libgcrypt package to the testing version (1.10.2)
fixed that problem.
As far as I can tell, the solution would be for the netatalk package to
depend on (at least?) the libgcrypt version it was compiled with.
--
Kind regards,
Matijs van Zuijlen
--
pkg-netatalk-devel mailing list
pkg-netatalk-de...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-netatalk-devel
