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: openra depends on insecure dotnet-runtime-wrapped-6.0.36 #360335

Open
l0b0 opened this issue Nov 30, 2024 · 4 comments
Open

Build failure: openra depends on insecure dotnet-runtime-wrapped-6.0.36 #360335

l0b0 opened this issue Nov 30, 2024 · 4 comments
Labels
0.kind: build failure A package fails to build

Comments

@l0b0
Copy link
Contributor

l0b0 commented Nov 30, 2024

Steps To Reproduce

Steps to reproduce the behavior:

  1. build openra

Build log

Build Log
❯ git checkout 0ea5454f75c7027e3e1492369e40ed5e9294f094
❯ nix-build -A openra
error:
       … while calling the 'derivationStrict' builtin
         at <nix/derivation-internal.nix>:34:12:
           33|
           34|   strict = derivationStrict drvAttrs;
             |            ^
           35|

       … while evaluating derivation 'openra-release-20231010'
         whose name attribute is located at /home/victor/nixpkgs/pkgs/stdenv/generic/make-derivation.nix:336:7

       … while evaluating attribute 'dotnet-runtime' of derivation 'openra-release-20231010'
         at /home/victor/nixpkgs/pkgs/games/openra/build-engine.nix:21:3:
           20|   dotnet-sdk = dotnetCorePackages.sdk_6_0;
           21|   dotnet-runtime = dotnetCorePackages.runtime_6_0;
             |   ^
           22|

       (stack trace truncated; use '--show-trace' to show the full, detailed trace)

       error: Package ‘dotnet-runtime-wrapped-6.0.36’ in /home/victor/nixpkgs/pkgs/development/compilers/dotnet/build-dotnet.nix:212 is marked as insecure, refusing to evaluate.


       Known issues:
        - Dotnet SDK 6.0.36 is EOL, please use 8.0 (LTS) or 9.0 (Current)

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

       a) To temporarily allow all insecure packages, you can use an environment
          variable for a single invocation of the nix tools:

            $ export NIXPKGS_ALLOW_INSECURE=1

          Note: When using `nix shell`, `nix build`, `nix develop`, etc with a flake,
                then pass `--impure` in order to allow use of environment variables.

       b) for `nixos-rebuild` you can add ‘dotnet-runtime-wrapped-6.0.36’ to
          `nixpkgs.config.permittedInsecurePackages` in the configuration.nix,
          like so:

            {
              nixpkgs.config.permittedInsecurePackages = [
                "dotnet-runtime-wrapped-6.0.36"
              ];
            }

       c) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
          ‘dotnet-runtime-wrapped-6.0.36’ to `permittedInsecurePackages` in
          ~/.config/nixpkgs/config.nix, like so:

            {
              permittedInsecurePackages = [
                "dotnet-runtime-wrapped-6.0.36"
              ];
            }

Additional context

See also #360336.

Metadata

  • system: "x86_64-linux"
  • host os: Linux 6.6.63, NixOS, 25.05 (Warbler), 25.05beta712559.4633a7c72337
  • multi-user?: yes
  • sandbox: yes
  • version: nix-env (Nix) 2.24.10
  • channels(root): "home-manager, nixos, nixos-hardware, nixos-stable-24.05"
  • nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Notify maintainers

@mdarocha


Note for maintainers: Please tag this issue in your PR.


Add a 👍 reaction to issues you find important.

@gepbird
Copy link
Contributor

gepbird commented Dec 2, 2024

.NET 8 support is being worked on upstream: OpenRA/OpenRA#21577

Until then you probably want to follow the instructions from the build log and allow the insecure dotnet-6 package:

nixpkgs.config.permittedInsecurePackages = [
    "aspnetcore-runtime-6.0.36"
    "aspnetcore-runtime-wrapped-6.0.36"
    "dotnet-sdk-6.0.428"
    "dotnet-sdk-wrapped-6.0.428"
  ];

@PunkPun
Copy link

PunkPun commented Dec 29, 2024

dependencies were updated upstream

@DocBrown101
Copy link

dependencies were updated upstream

Unfortunately no, it was only divided up!

@DocBrown101
Copy link

Dependencies have now been updated in upstream!

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
Development

No branches or pull requests

4 participants