Conversation
|
Result of 2 packages marked as broken and skipped:
18 packages built:
|
Both python312Packages.jupyter-repo2docker and python312Packages.jupyter-repo2docker.dist are broken (in machine) even when trying to build based on master branch, so it is not broken because of my changes? |
|
Note that there is #278607 that has been opened earlier this year. |
I should close this pr then? |
| docker_25 = callPackage dockerGen rec { | ||
| version = "25.0.3"; | ||
| cliRev = "v${version}"; | ||
| cliHash = "sha256-u1quVGTx/p8BDyRn33vYyyuE5BOhWMnGQ5uVX0PZ5mg="; |
There was a problem hiding this comment.
It also seemed wrong, but the version did change when doing docker --version and it built successfully
There was a problem hiding this comment.
@aikooo7 yeah because the version is set by the build itself. If you change a random character from the hashes and re-run the build, you'll see a failure (and the new hashes as well).
|
Closing in favor of the now merged #278607 |
Description of changes
Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Closes #288001
Add a 👍 reaction to pull requests you find important.