alsa-ucm-conf: 1.2.12 → 1.2.13-unstable-2025-03-21; validate in alsa-lib #392058
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Switch
alsa-ucm-conf
to rolling release.Updates to the UCM configuration files are released in tandem with the ALSA library every half year or so.
The UCM configuration files however receive frequent updates with new profiles for additional hardware and I believe that users would benefit from making these available in nixpkgs independently of the ALSA lib release cycle.
The configuration files are validated automatically by upstream after review and so I don’t expect this to break very often.
Just to make sure, I added validation of the UCM configuration to
alsa-lib
, as part ofinstallCheckPhase
.Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.