You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I found was that for different architectures, different nixpkgs commits are resolved, resulting in different package versions from nixpkgs being built depending on system. This surprised me.
The latter result contains the correct latest revision for all architectures, so I'm wondering there is a bug in the indexing process that's leading to this? I have seen similar behaviour before but this was the first time that I actually delved deeper to see what was going on.
What happened?
golangci-lint
package was recently updated to build with go 1.23 in NixOS/nixpkgs@2bd2d99. When updating on my MacOS machine, I found that it was still building with older go version so went to https://www.jetify.com/devbox/docs/nixhub/resolve-a-package-version/ to see what was being found in the nixhub index.What I found was that for different architectures, different nixpkgs commits are resolved, resulting in different package versions from nixpkgs being built depending on system. This surprised me.
From https://www.jetify.com/devbox/docs/nixhub/resolve-a-package-version/ searching for
golangci-lint
andlatest
, the revisions are different foraarch64-darwin
(https://github.com/NixOS/nixpkgs/blob/5629520edecb69630a3f4d17d3d33fc96c13f6fe/pkgs/development/tools/golangci-lint/default.nix) and foraarch64-linux
(https://github.com/NixOS/nixpkgs/blob/8b4061fd60ccc3b3f44b73faa7c983eacf7a6f7b/pkgs/development/tools/golangci-lint/default.nix).The latter result contains the correct latest revision for all architectures, so I'm wondering there is a bug in the indexing process that's leading to this? I have seen similar behaviour before but this was the first time that I actually delved deeper to see what was going on.
Steps to reproduce
No response
Command
No response
devbox.json
No response
Devbox version
0.12.0
Nix version
No response
What system does this bug occur on?
macOS (Apple Silicon)
Debug logs
No response
The text was updated successfully, but these errors were encountered: