Repository navigation
chore(flake): nix-fleet 3e108653 — effect inputs must be derivations - #103
Merged
Merged
Conversation
Bumps nix-fleet so the package-updates schedule effect's inputs no longer include the update-packages app program (a plain file). stdenv's package activation sourced that file as a setup hook during the effect env materialization, exec'd the runner with the activation words as package selectors, and failed the whole -env build with 'not registered: -1 <path> 0' — the observed failure of the first scheduled update run. Verified from this tree: the schedule effect's -env derivation builds clean via the same 'nix develop -i <drv>^*' step that failed before.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps nix-fleet to
3e108653so thepackage-updatesschedule effect'sinputsno longer include the update-packages app program (a plain store file). stdenv's package activation sourced that file as a setup hook during the effect env materialization, exec'd the runner with the activation words as package selectors, and failed the whole-envbuild withnot registered: -1 <path> 0— the observed failure of the first scheduled update run.Verified from this tree: the schedule effect's
-envderivation builds clean via the samenix develop -i <drv>^*step that failed before;nix flake checkon nix-fleet at this pin is green.