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

Build failure: feishin #376166

Open
3 tasks done
bobberb opened this issue Jan 23, 2025 · 4 comments · May be fixed by #377468
Open
3 tasks done

Build failure: feishin #376166

bobberb opened this issue Jan 23, 2025 · 4 comments · May be fixed by #377468
Labels
0.kind: build failure A package fails to build

Comments

@bobberb
Copy link

bobberb commented Jan 23, 2025

Nixpkgs version

  • Stable (24.11)

Steps to reproduce

  1. Attempt to build feishin while on latest commit nixos-24.11 flake
  2. Failure
    "Electron 31.7.7 Marked as insecure, refusing to evaluate"

Can Hydra reproduce this build failure?

No, Hydra cannot reproduce this build failure.

Link to Hydra build job

No response

Relevant log output

#nix run nixpkgs/47addd76727f42d351590c905d9d1905ca895b82#feishin


       error: Package ‘electron-31.7.7’ in /nix/store/5kvd3cn4cld24l2cs07m4hw3hwlqq104-source/pkgs/development/tools/electron/binary/generic.nix:37 is marked as insecure, refusing to evaluate.

Additional context

Pulled latest nixos-24.11 commit at time of writing

'github:NixOS/nixpkgs/47addd76727f42d351590c905d9d1905ca895b82' (2025-01-22)

Electron 31.7.7 insecure.

System metadata

  • system: "x86_64-linux"
  • host os: Linux 6.12.2-zen1, NixOS, 24.11 (Vicuna), 24.11.20250115.e24b4c0
  • multi-user?: yes
  • sandbox: yes
  • version: nix-env (Lix, like Nix) 2.91.1 System type: x86_64-linux Additional system types: i686-linux, x86_64-v1-linux, x86_64-v2-linux, x86_64-v3-linux, x86_64-v4-linux Features: gc, signed-caches System configuration file: /etc/nix/nix.conf User configuration files: /home/user/.config/nix/nix.conf:/nix/store/jv8c6l3r7lvyxnlhf8h1jl1zhx2rn3mw-plasma-workspace-6.2.5/etc/xdg/nix/nix.conf:/nix/store/ci41jxiphqw02kh5371ddbys917d5b67-kglobalacceld-6.2.5/etc/xdg/nix/nix.conf:/nix/store/qjs0vfgjq2yyvs7papbisg1lr7h6wpx5-baloo-6.8.0/etc/xdg/nix/nix.conf:/home/user/.config/kdedefaults/nix/nix.conf:/nix/store/jv8c6l3r7lvyxnlhf8h1jl1zhx2rn3mw-plasma-workspace-6.2.5/etc/xdg/nix/nix.conf:/nix/store/ci41jxiphqw02kh5371ddbys917d5b67-kglobalacceld-6.2.5/etc/xdg/nix/nix.conf:/nix/store/qjs0vfgjq2yyvs7papbisg1lr7h6wpx5-baloo-6.8.0/etc/xdg/nix/nix.conf:/nix/store/jv8c6l3r7lvyxnlhf8h1jl1zhx2rn3mw-plasma-workspace-6.2.5/etc/xdg/nix/nix.conf:/nix/store/ci41jxiphqw02kh5371ddbys917d5b67-kglobalacceld-6.2.5/etc/xdg/nix/nix.conf:/nix/store/qjs0vfgjq2yyvs7papbisg1lr7h6wpx5-baloo-6.8.0/etc/xdg/nix/nix.conf:/home/user/.config/kdedefaults/nix/nix.conf:/etc/xdg/nix/nix.conf:/home/user/.local/share/flatpak/exports/etc/xdg/nix/nix.conf:/var/lib/flatpak/exports/etc/xdg/nix/nix.conf:/home/user/.nix-profile/etc/xdg/nix/nix.conf:/nix/profile/etc/xdg/nix/nix.conf:/home/user/.local/state/nix/profile/etc/xdg/nix/nix.conf:/etc/profiles/per-user/user/etc/xdg/nix/nix.conf:/nix/var/nix/profiles/default/etc/xdg/nix/nix.conf:/run/current-system/sw/etc/xdg/nix/nix.conf Store directory: /nix/store State directory: /nix/var/nix Data directory: /nix/store/h7aaq5877bh62is6ca6bn5dr8bzmcqrs-lix-2.91.1/share
  • channels(root): "nixos-23.11"
  • channels(user): ""
  • nixpkgs: /nix/store/awsvw44jla0idziiks2zwgzslfd2dczn-source

Notify maintainers


Note for maintainers: Please tag this issue in your pull request description. (i.e. Resolves #ISSUE.)

I assert that this issue is relevant for Nixpkgs

Is this issue important to you?

Add a 👍 reaction to issues you find important.

@bobberb
Copy link
Author

bobberb commented Jan 24, 2025

@aucub how does this stuff get merged on a stable branch without someone alerting to a package not building?

@bobberb
Copy link
Author

bobberb commented Jan 24, 2025 via email

@emilylange
Copy link
Member

@bobberb if you happen to have time, would you mind sharing your view on this?

I always thought the eval error one gets when pulling in a package that is marked as insecure is extremely clear.

But that may just be me, given my involvement.

Did you see the eval error that I mentioned in #370758?

Especially the following section:

You can install it anyway by allowing this package, using the following methods:

Do you have suggestions on how this could be improved?

Thanks :)

@bobberb
Copy link
Author

bobberb commented Jan 24, 2025 via email

@DoctorDalek1963 DoctorDalek1963 linked a pull request Jan 28, 2025 that will close this issue
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.kind: build failure A package fails to build
Projects
None yet
2 participants