Hydra Build of Pihole-FTL reports success, can't recreate locally

Help
1

I am on the nixos-unstable channel for my config, using the latest revision 80bdc1e5ce51 (at time of writing).

pihole-ftl fails to build for me. However, Hydra reports the build as successful: https://hydra.nixos.org/build/323308563.

Local build attempt (on x86_64-linux, although I can recreate this failure on a Raspberry-Pi 5 setup):

nix-repl> pkgs = import <nixpkgs> { }

nix-repl> pkgs.lib.trivial.version    
"26.05pre958232.80bdc1e5ce51"

nix-repl> :bl pkgs.pihole-ftl         
error: Cannot build '/nix/store/iw58d47mpc0mzwczrm7kh7j787xcv19c-pihole-ftl-6.4.1.drv'.
       Reason: builder failed with exit code 1.
       Output paths:
         /nix/store/2i9xdn9hmm84b3sh2gbn80dagf9nrdnz-pihole-ftl-6.4.1
       Last 8 log lines:
       > Running phase: unpackPhase
       > unpacking source archive /nix/store/ccbhm04f500v9qdnx3b991bg5cnfyynm-source
       > source root is source
       > Running phase: patchPhase
       > applying patch /nix/store/qzxrp2x72h6vbfx1rmidyrrr853lf67h-disable-redirect-root.patch
       > patching file src/webserver/webserver.c
       > Hunk #1 FAILED at 720.
       > 1 out of 1 hunk FAILED -- saving rejects to file src/webserver/webserver.c.rej
       For full logs, run:
         nix log /nix/store/iw58d47mpc0mzwczrm7kh7j787xcv19c-pihole-ftl-6.4.1.drv
[0 built (1 failed)]

Additionally, the hash I get for the pihole derivation is different to the one reported by Hydra: https://hydra.nixos.org/build/323308563#tabs-details.

I am not so much looking for a solution (I have a working install of pihole with an older nixpkgs, and a PR fixing this has already been merged into master, so I am happy to wait for it to reach nixos-unstable) as I am curious about what could cause this difference. Any ideas?

2

If you look at the build inputs on hydra it uses a different nixpkgs revision than you do.

2 Likes
3

You are looking at the wrong build. This is the build that applies to the revision you referenced:

This shows the commits that the build applies to.

The one you linked is built from aca4d95fce49, see this for the commits that it applies to.

3 Likes
4

Thank you, that makes more sense. My bad.
I misread this:

image
image526×115 7.24 KB

as implying that it was on 80bd..., but I now see that that was moving from 80... to aca....

1 Like