Hi Santiago, On Fri, May 23, 2025 at 12:36:11PM +0200, Santiago Vila wrote: > The summary is to add both "perl-xs-dev" and "libcrypt-dev" to build-depends?
No. It is the perl extension headers that #include <crypt.h>. Therefore, some perl package that provides perl-xs-dev will carry the dependency on libcrypt-dev in forky and by depending on perl-xs-dev you ensure that libcrypt-dev will be available when it is used. So you only need to depend on perl-xs-dev here. > (I guess that when you say "dependency" above you really mean > "build-dependency"). Yes, it's a build dependency. > Now, for the perl-xs-dev part: I believe virtual packages should not be added > plainly > to build-depends, because tools like sbuild do not understand them. Has this > changed recently, or maybe I should use "libperl-dev | perl-xs-dev" instead? sbuild does understand virtual packages. When we added perl-xs-dev, we envisioned turning it into a real package to facilitate perl transitions. The use of the virtual perl-xs-dev tends to practically break cross building during perl transitions. However, perl transitions tend to be so short that we never turned it real. > [ There are several other things to fix for trixie, so I'd like to include > this one in the next upload ] The additional perl-xs-dev dependency is safe for inclusion in trixie. Helmut
