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.

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

Perlless activation fails with missing time zone file #321280

Closed
awebeer256 opened this issue Jun 20, 2024 · 7 comments · Fixed by #321794
Closed

Perlless activation fails with missing time zone file #321280

awebeer256 opened this issue Jun 20, 2024 · 7 comments · Fixed by #321794
Labels
0.kind: bug Something is broken 6.topic: nixos Issues or PRs affecting NixOS modules, or package usability issues specific to NixOS

Comments

@awebeer256
Copy link

Describe the bug

If I try to make my system perlless, my system rebuild fails.

Steps To Reproduce

Steps to reproduce the behavior:

  1. Add the following module to your system configuration:
{ modulesPath, ... }:
{
  imports = [ "${modulesPath}/profiles/perlless.nix" ];
}
  1. nixos-rebuild

Expected behavior

The command succeeds.

Screenshots

Commands:

$ doas nixos-rebuild boot
building the system configuration...
error: builder for '/nix/store/<hash>-etc-lowerdir.drv' failed with exit code 1;
       last 1 log lines:
       > cp: cannot stat '/etc/zoneinfo/<region>/<city>': No such file or directory
       For full logs, run 'nix log /nix/store/<hash>-etc-lowerdir.drv'.
error: 1 dependencies of derivation '/nix/store/<hash>-nixos-system-<hostname>-<timestamp>.<hash>.drv' failed to build

$ nix log /nix/store/<hash>-etc-lowerdir.drv
warning: The interpretation of store paths arguments ending in `.drv` recently changed. If this command is now failing try again with '/nix/store/<hash>-etc-lowerdir.drv^*'
cp: cannot stat '/etc/zoneinfo/<region>/<city>': No such file or directory

$ nix log '/nix/store/<hash>-etc-lowerdir.drv^*'
cp: cannot stat '/etc/zoneinfo/<region>/<city>': No such file or directory

$ stat /etc/zoneinfo/<region>/<city>
  File: /etc/zoneinfo/<region>/<city>
  Size: xxxx            Blocks: x          IO Block: xxxx   regular file
Device: x,xx    Inode: xxxxxxx     Links: 1
Access: (0444/-r--r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: <timestamp>
Modify: <timestamp>
Change: <timestamp>
 Birth: <timestamp>

Additional context

nixos-rebuild dry-build succeeds.
I use flakes.

Notify maintainers

Metadata

Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.

[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.9.4, NixOS, 24.05 (Uakari), 24.05.20240612.cc54fb4`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Lix, like Nix) 2.90.0-beta.1`
 - channels(root): `"nixos-23.11"`
 - nixpkgs: `/nix/store/aa0zsahvyqnvzkicsh29jirm9hwv95pg-source`

Add a 👍 reaction to issues you find important.

@awebeer256 awebeer256 added the 0.kind: bug Something is broken label Jun 20, 2024
@eclairevoyant
Copy link
Contributor

Odd, thought #314579 was meant to fix this. Perhaps more digging is needed.

@eclairevoyant eclairevoyant added the 6.topic: nixos Issues or PRs affecting NixOS modules, or package usability issues specific to NixOS label Jun 20, 2024
@ivan770
Copy link
Member

ivan770 commented Jun 22, 2024

What is the revision of nixpkgs that you are trying to build your system with? #314579 is merged without a 24.05 backport.

@eclairevoyant
Copy link
Contributor

Per nix-info they're on 24.05 not unstable, so that makes sense. Is it backportable?

@ivan770
Copy link
Member

ivan770 commented Jun 22, 2024

Is it backportable?

The PR itself is backportable, but I'm not sure if it complies with nixpkgs' backport criteria.

@eclairevoyant
Copy link
Contributor

eclairevoyant commented Jun 22, 2024

Right, that's what I meant to ask - is it a breaking change? (i.e. is it possible for someone to rely on the old behaviour?) or simply a bugfix with low chance of regressions?

@ivan770
Copy link
Member

ivan770 commented Jun 22, 2024

Right, that's what I meant to ask - is it a breaking change? (i.e. is it possible for someone to rely on the old behaviour?) or simply a bugfix with low chance of regressions?

Is it not a breaking change because the system.etc.overlay.enable option is marked as experimental (and also because the behavior before the PR was erroneous in the first place).

@azahi
Copy link
Member

azahi commented Jun 25, 2024

Fixed in #321794.

@azahi azahi closed this as completed Jun 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.kind: bug Something is broken 6.topic: nixos Issues or PRs affecting NixOS modules, or package usability issues specific to NixOS
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants