The dev shell's interpreter is the one `pkgmgr update --all` installs every repository in the catalogue with, so it has to satisfy their floors rather than only this project's. portfolio declares requires-python >=3.12, which 3.11 does not resolve; the package block moves along with the shell because the comment there promises they are the same version. ldap-schema-manager pulls python-ldap, which compiles against lber.h and ldap.h from OpenLDAP plus the SASL headers and locates them through pkg-config. None of the three were in buildInputs, so that repository failed in the compiler rather than in the resolver. Both are failures of the same sweep, and both are environment rather than code. Verified: a full `pkgmgr update --all` sweep in the arch image against this flake, with 0 installation failures. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
3.9 KiB
3.9 KiB