Hi Matijs,
I totally get your point and agree that this situation is not ideal.
Unfortunately, I don't think the exact dependent package version is something
that we as package managers can or should hard code in this fashion.
Look at the "debian/control" file in the package repo:
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
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:
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
4 matches
Mail list logo
