Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

nesting.clone is broken on non-x86_64 #80806

Closed
rnhmjoj opened this issue Feb 22, 2020 · 0 comments · Fixed by #81241
Closed

nesting.clone is broken on non-x86_64 #80806

rnhmjoj opened this issue Feb 22, 2020 · 0 comments · Fixed by #81241
Labels
0.kind: bug 6.topic: nixos 6.topic: portability General portability concerns, not specific to cross-compilation or a specific platform

Comments

@rnhmjoj
Copy link
Contributor

rnhmjoj commented Feb 22, 2020

Describe the bug
The NixOS option nesting.clone is broken on non-x86_64 systems.
The problem is the /run/current-system/fine-tune/child-1/bin/switch-to-configuration script has shebang pointing to a x86_perl interpreter, regardless of the parent.

To Reproduce
Steps to reproduce the behavior:

  1. $ nix-build -A pkgsi686Linux.nixosTests.nesting

Expected behavior
The script should have a shebang containing the right interpreter for the system.

Additional context
I think this has been broken since the beginning of NixOS.

Maintainer information:

# a list of nixos modules affected by the problem
module:
- nixos/modules/system/activation/top-level.nix
@veprbl veprbl added the 6.topic: portability General portability concerns, not specific to cross-compilation or a specific platform label Feb 23, 2020
thefloweringash added a commit to thefloweringash/nixpkgs that referenced this issue Feb 27, 2020
@thefloweringash
nixos/activation: propagate system to nested configurations
b83164a 
The current behavior lets `system` default to
`builtins.currentSystem`. The system value specified to
`eval-config.nix` has very low precedence, so this should compose
properly.

Fixes NixOS#80806
@thefloweringash thefloweringash mentioned this issue Feb 28, 2020
Merged
10 tasks
rnhmjoj pushed a commit that referenced this issue Mar 13, 2020
@thefloweringash @rnhmjoj
nixos/activation: propagate system to nested configurations
4a8801a 
The current behavior lets `system` default to
`builtins.currentSystem`. The system value specified to
`eval-config.nix` has very low precedence, so this should compose
properly.

Fixes #80806

(cherry picked from commit b83164a)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0.kind: bug 6.topic: nixos 6.topic: portability General portability concerns, not specific to cross-compilation or a specific platform
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

nixos/activation: propagate system to nested configurations thefloweringash/nixpkgs
2 participants
@veprbl @rnhmjoj