Any way to use Firefox Nightly from firefox-overlay?

[mpontus]

I was trying to install Firefox Nightly from firefox-overlay and set it up in my system configuration using home-manager installed as NixOS module:

My configuration.nix contains following lines:

nixpkgs.overlays = [
    (import (builtins.fetchTarball https://github.com/mozilla/nixpkgs-mozilla/archive/master.tar.gz))
];
programs.firefox.enable = true;
programs.firefox.package = pkgs.latest.firefox-nightly-bin;

But when I run nixos-rebuild switch I get the following error:

building Nix...
building the system configuration...
error: attribute 'gtk3' missing

       at /nix/store/35zha94qrwqhr5cjkdag97dr8la3vavn-nixos/nixos/pkgs/applications/networking/browsers/firefox/wrapper.nix:185:23:

          184|       nativeBuildInputs = [ makeWrapper lndir jq ];
          185|       buildInputs = [ browser.gtk3 ];
             |                       ^
          186|
(use '--show-trace' to show detailed location information)

To which I found this answer: #2530 (comment), suggesting to provide the unwrapped version of the package instead.

So I'm assuming that the overlay also provides a wrapped version of a nightly build. Is it something that can only be solved by nixpkgs-mozilla maintainers and if so how should I formulate the request?

[figgyc]

You should be able to use pkgs.latest.firefox-nightly-bin.unwrapped. The wrapper provides the unwrapped package as a passthru attribute so even though the overlay does not expose a separate attribute like nixpkgs does, you should still be able to use it. I haven't tested this but I think it should work from reading the overlay source code.

[stale]

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 you are the original author of the issue

• 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 not the original author of the 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.

Memorandum on closing issues

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.