Cannot update LibreWolf

Hi,

I’m struggling to update librewolf. There are actually two problems:

  1. I can see librewolf is already built on hydra, but nh os switch -u keeps trying to build it locally.
  2. I tried building it locally on a laptop (i7, 24gb of ram) and on build server (epyc + 32gb of ram for this single machine) and it always fails with error: could not compile gkrust (lib).

What am I doing wrong?

1 Like

I’ve also encountered this issue. Until the issue is fixed, you can switch the package to use the stable channel. That’s what I’ve done.

1 Like

Thanks! I’ll do that :slight_smile: I extended memory on builder vm to 48GB and now it’s stuck on linker. lld is using allmost all 48gb of ram and 5% CPU - build is running for 4 hours now :smiley: unbelievable :wink:

Just because one package has finished building on Hydra doesn’t mean all of the necessary packages to advance the channel have been built. So you’ll still have to wait on nixos-unstable.

Follow https://nixpkgs-tracker.ocfox.me/?pr=480923 (corresponding to librewolf-unwrapped: 147.0-1 -> 147.0.1-3 by yzhou216 · Pull Request #480923 · NixOS/nixpkgs · GitHub) for updates.

2 Likes

Thanks @waffle8946 ! This is pretty complex :slight_smile:

So just to have a closure: after reading this comment about absolutely insane build requirements I gave up and pinned Librewolf to nixpkgs commit from before the update:

# flake.nix
{
  description = "The cathedral of home configuration";

  inputs = {
  (...)
    nixpkgs-librewolf.url = "github:nixos/nixpkgs/e4bae1bd10c9c57b2cf517953ab70060a828ee6f";
  };

(...)

# nix home manager
{ pkgs, nixpkgs-librewolf, ... }:
{
  programs.librewolf = {
    enable = true;
    package = nixpkgs-librewolf.legacyPackages.${pkgs.system}.librewolf;
(...)

I’m on stable 25.11 and librewolf is (for whatever reason) building locally too? I can see the Hydra build and the port to stable completed a few days ago. Any clues? Not a huge fan of just pinning my browser like the solution states is working.

You need to update your channel.

Updating my flake is what caused the build. I can try again in a moment though.

EDIT: nope, still tries to build locally.

Here’s nixpkgs in my flake.lock.

    "nixpkgs": {
      "locked": {
        "lastModified": 1769318308,
        "narHash": "sha256-Mjx6p96Pkefks3+aA+72lu1xVehb6mv2yTUUqmSet6Q=",
        "owner": "nixos",
        "repo": "nixpkgs",
        "rev": "1cd347bf3355fce6c64ab37d3967b4a2cb4b878c",
        "type": "github"
      },
      "original": {
        "owner": "nixos",
        "ref": "nixos-25.11",
        "repo": "nixpkgs",
        "type": "github"
      }
    },

Then I assume you have some overlay or mass-rebuild option like cudaSupport enabled.

Never mind - it looks like hydra is running behind on this one: https://hydra.nixos.org/build/320178054 I have no idea why the channel advanced, that makes zero sense tbh.

1 Like

Is there any way to get a notification when a Hydra build finishes without me having to write a script?

It also looks like it failed its first build.

It hasn’t failed on stable in months. Never got hydra notifs to work, so you might have to check manually or script it.

Aw man, guess I’ll just check in every so often unless I need something to procrastinate with.

The build has finished for anyone following this thread waiting.

3 Likes