Nixpkgs: Cannot Install google-chrome (404).

[AshtonKem]

Issue description

I cannot upgrade my older installation of NixOs from the 16.09 channel to 17.03. I am getting 404 errors around google-chrome. Here is the error that I get:

building path(s) ‘/nix/store/j9gg9jq5kwkgf2iwxd43sg706kr619c2-google-chrome-stable_57.0.2987.110-1_amd64.deb’

trying https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_57.0.2987.110-1_amd64.deb
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404 

trying http://95.31.35.30/chrome/pool/main/g/google-chrome-stable/google-chrome-stable_57.0.2987.110-1_amd64.deb
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404 Not Found

trying http://mirror.pcbeta.com/google/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_57.0.2987.110-1_amd64.deb
Warning: Transient problem: timeout Will retry in 1 seconds. 3 retries left.
Warning: Transient problem: timeout Will retry in 2 seconds. 2 retries left.
Warning: Transient problem: timeout Will retry in 4 seconds. 1 retries left.
curl: (6) Couldn't resolve host 'mirror.pcbeta.com'

trying http://repo.fdzh.org/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_57.0.2987.110-1_amd64.deb
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   185  100   185    0     0    578      0 --:--:-- --:--:-- --:--:--   579
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
curl: (22) The requested URL returned error: 404 
error: cannot download google-chrome-stable_57.0.2987.110-1_amd64.deb from any mirror
builder for ‘/nix/store/ma09gjhvhjl6036mldfn6wpfhq1dqxjf-google-chrome-stable_57.0.2987.110-1_amd64.deb.drv’ failed with exit code 1
cannot build derivation ‘/nix/store/0w5ymgwxc61xnk59w2ir8yd7vbj89g0k-google-chrome-57.0.2987.110.drv’: 1 dependencies couldn't be built
building path(s) ‘/nix/store/cxpbg5kr91q1lrjvh7zlfwm8m6yxjk37-kernel-modules-shrunk’
cannot build derivation ‘/nix/store/4i4rjb076lxlgbdgg1ccrq3niriccq21-system-path.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/9cgbfk6habfmpk663qbg4g1plmq7pk3i-nixos-system-nixos-16.09.1942.28dc5c7d22.drv’: 1 dependencies couldn't be built
error: build of ‘/nix/store/9cgbfk6habfmpk663qbg4g1plmq7pk3i-nixos-system-nixos-16.09.1942.28dc5c7d22.drv’ failed

Steps to reproduce

Add google-chrome to the systemPackages

Technical details

• System: (NixOS: nixos-version, Ubuntu/Fedora: lsb_release -a, ...)
  16.09.1903.c80a791 (Flounder)
• Nix version: (run nix-env --version)
  nix-env (Nix) 1.11.8
• Nixpkgs version: (run nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion)
  "16.09.1942.28dc5c7d22"
• Sandboxing enabled: (run grep build-use-sandbox /etc/nix/nix.conf)
  build-use-sandbox = false

[pbogdan]

Is your 17.03 channel up to date? Chrome stable should on 57.0.2987.133 in 17.03 - https://github.com/NixOS/nixpkgs/blob/release-17.03/pkgs/applications/networking/browsers/chromium/upstream-info.nix#L16 and perhaps 57.0.2987.110 .deb is already gone.

[DCPRevere]

@AshtonKem can you try running sudo nix-channel --update and then sudo nixos-rebuild switch? This worked for me.

[chris-martin]

Chrome still does not build on 17.03.

curl: (22) The requested URL returned error: 404
error: cannot download google-chrome-stable_58.0.3029.110-1_amd64.deb from any mirror

It seems fine on unstable, though.

[mogorman]

having same problem even though i found the file elsewhere and did a nix-store --add google-chrome-stable_58.0.3029.110-1_amd64.deb

[ixxie]

I can confirm that moving from 17.03 to unstable fixed this issue.

[PierreR]

Same problem for me (also using 17.03 stable) ... Very annoying as I did not expect such a failure on the stable branch.

Of course I can switch to the unstable channel but that's not really an option for me because I am using a config that install that package on many machines in an automate way. In any way applying such change across would be a pain.

[ocharles]

Could we please get this ported from unstable to 17.03? It's quite frustrating that we haven't had a working Google Chrome for three months on the recommended branch!

[ixxie]

@ocharles - you can port it yourself. I have both the unstable and stable channels on my system root:

$ sudo nix-channel --list
nixos https://nixos.org/channels/nixos-17.03
nixos-unstable https://nixos.org/channels/nixos-unstable

and the following in my configuration.nix:

nixpkgs.config = 
{
    # Allow proprietary packages
    allowUnfree = true;

    # Create an alias for the unstable channel
    packageOverrides = pkgs: 
    {
        unstable = import <nixos-unstable> 
            { 
                # pass the nixpkgs config to the unstable alias
                # to ensure `allowUnfree = true;` is propagated:
                config = config.nixpkgs.config; 
            };
    };
};

which allows you to switch particular packages to the unstable channel:

environment = 
{
    systemPackages = 
        with pkgs; 
        [
            ddate
            devilspie2
            evince
            unstable.google-chrome
            ...
            zsh
    ]; 
};

[ocharles]

While that works, we really need to get this into stable.

On Wed, Aug 16, 2017 at 7:15 PM, Matan Shenhav [e-mail]
wrote:

@ocharles https://github.com/ocharles - you can port it yourself. I
have the following in my configuration.nix:

nixpkgs.config =
{
# Allow proprietary packages
allowUnfree = true;

# Create an alias for the unstable channel
packageOverrides = pkgs:
{
    unstable = import <nixos-unstable>
        {
            config = config.nixpkgs.config;
        };
};

};

Which allows you to switch particular packages to the unstable channel:

environment =
{
systemPackages =
with pkgs;
[
ddate
devilspie2
evince
unstable.google-chrome
...
zsh
];
};

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/issues/25880#issuecomment-322855573,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABRjlk1TpX8Q7WcplCiTfRpy4YVUDo2ks5sYzHRgaJpZM4NeqKB
.

[PierreR]

Still not fixed in stable but hopefully it is a matter of days now.

I concur with @ocharles These kind of issues on the stable branch are really a pain on the end user side.

By the way, would firefox be a better choice as a stable browser on nixos-stable ?

[instantepiphany]

I am having the same issue.

I am very thankful that I get to use NixOS on my machines, so with that in mind, could one of the lead developers update us on what is happening?

If I understand correctly, stable 17.03 references chrome versions that are out of date, and so aren't mirrored anywhere.

I thought for a minute that they should be mirrored on Hydra, but Hydra only caches projects it has built, which means it won't cache Chrome as Chrome is non-free, correct?

Is this something that someone with less nixpkgs packaging experience could help update? I have added a few Vim plugins and written a few local packages for basic compiled programs, but don't have nixpkgs experience other than that (apart from using it to manage my personal system).

[PierreR]

As a side note, whoever fix this could take the opportunity to add himself as a maintainer: https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/networking/browsers/google-chrome/default.nix#L141
(I doubt the sole member of the set is still around)

@instantepiphany Thanks for your input

[chris-martin]

Can this issue be closed since google-chrome is working in 17.09, or is there something that needs to be future-proofed to prevent this from happening again?

[ocharles]

Well 17.09 isn't even out, so I don't think it can be closed yet. I'm still rather unhappy with the situation, but maybe the solution is to scratch the itch and become a maintainer for this.

[yegortimoshenko]

See https://github.com/NixOS/nixpkgs/issues/27811#issuecomment-353750050.

Also I think we should close issues immediately as they are fixed in master, otherwise it's impossible to track what has been fixed and what still needs fixing.