In reply to @hexa:lossy.network

TWIN: Dependency validation for Python Package will be restored after the next staging cycle on master. We expect a few breakages here and there, but clear error messages will be provided!

For missing propagatedBuildInputs you'll see

Checking runtime dependencies for pysml-0.1.1-py3-none-any.whl
  - aiohttp not installed

and for violated version constraints

Checking runtime dependencies for sphinx_prompt-1.6.0-py3-none-any.whl
  - sphinx==7.0.0 not satisfied by version 7.2.6

Use pythonRelaxDepsHook to relax version constraints on dependencies, or bump dependencies as needed!

TWIN: This week, sparked from a discussion to prompt the removal of scripted initrd networking where a call for feedback has been made in https://discourse.nixos.org/t/seeking-feedback-on-the-removal-of-scripted-initrd-networking-in-nixos/39457, we discussed with contributors in #dev:nixos.org at message https://matrix.to/#/!kjdutkOsheZdjqYmqp:nixos.org/$6e30z5pwbKIKXLTHs1eZwWkddMNrXgyoYc5NEIsW5zA?via=nixos.org&via=matrix.org&via=nixos.dev

A summary is that we notice that we don't have formal policies for deprecations in nixpkgs, we do not want to discuss tools or implementations of such things as we know plenty of them: RFC127 (unimplemented), NixOS module systems, lib.warn and more. We would like to focus and steer things towards a policy, we described our state of knowledge in https://pad.lassul.us/nixos-deprecation-cycle-theory.

Once we collect enough, we will move to a proposal in a PR and enact such a policy with the approval of contributors.

TWIN: This week, sparked from a discussion in the contribution channel https://matrix.to/#/!kjdutkOsheZdjqYmqp:nixos.org/$TyVnavWN3waTSaNOm0dT8V0q9Xmef0x1Tin-roaD_hU?via=nixos.org&via=matrix.org&via=nixos.dev about Musl https://musl.libc.org/, an alternative libc to glibc and its support in Nixpkgs.

I proposed as a takeaway https://matrix.to/#/!kjdutkOsheZdjqYmqp:nixos.org/$7lx9_zRf1xXuKv812u7ouhHLr0psuT3R-i7NEPvdQm8?via=nixos.org&via=matrix.org&via=nixos.dev that it would be interesting to see more CI checks in the form of passthru.tests.* on various relevant packages to https://spectrum-os.org/ which is a Nix-derivative operating system using Musl.

In addition to that, if troubles arise while supporting a package due to Musl tests, the group of folks in @NixOS/static could intervene and provide guidance on how to proceed.

Note that static builds in Nixpkgs are offered via static musl builds, this could be done using glibc but this infrastructure for static builds does not exist in nixpkgs. Moreover, according to the appendix in RFC 046 (https://github.com/NixOS/rfcs/blob/master/rfcs/0046-platform-support-tiers.md), x86_64-linux + musl + gcc is a tier 3 platform. Static musl is a tier 4 platform on x86_64-linux.

If you want to see this change, please chime in the discussion and offer your help to the people working on musl in nixpkgs.