Open johantiden opened 10 months ago
potential workaround possible now: separately add a flake input for nixpkgs-unfree
Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.
* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.
Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.
I have just run into this issue with the olm package, for which it's probably going to be common to want to add an exception for, at least for a while. I am really surprised that there's no way to configure ignores for this with home-manager, I just followed the instructions printed out and was very surprised when it didn't "just work".
Is this not possible via https://nix-community.github.io/home-manager/options.xhtml#opt-nixpkgs.config?
@chvp The suggestion verbatim does not seem to work. Example with the current olm situation.
{ config, pkgs, ... }:
{
home.packages = with pkgs; [
kdePackages.neochat
# ...
];
nixpkgs.config.permittedInsecurePackages = [
"olm-3.2.16"
];
}
Confusingly, nixpkgs.config.allowUnfreePredicate
declared as so:
nixpkgs.config.allowUnfreePredicate = pkg:
builtins.elem (lib.getName pkg) [
"obsidian"
"vivaldi"
"aspell-dict-en-science"
];
Works fine, so the config is being generated and followed. But using the documentation I can't discover where the final configuration lives.
Description
Adding packages via
home.packages
can result in build failure due to being marked as insecure in the upstream.Let's use
pkgs.pulsar
as an example, which has been marked insecure in the unstable branch.The
home-manager build
now fails withOption
a)
works withhome-manager build
but is not very nice because I'd have to add that every time I want to rebuild (or god forbid add it permanently to my env).The other options don't work at all with
home-manager build
.It would be a nicer experience if