Pjotr Prins <[email protected]> skribis: > I am running client and server in exactly the same checked out guix > repository. Server: > > ./pre-inst-env guix publish -u guix-publisher > publishing /gnu/store on 0.0.0.0, port 8080 > > Client on the same server > > ./pre-inst-env guix package -i hello --dry-run
If ‘guix publish’ and ‘guix package’ run on the same machine, then nothing will happen: ‘guix publish’ serves what’s in /gnu/store, and ‘guix package’ will resort to substitutes only when something’s missing from /gnu/store, in which case ‘guix publish’ won’t have it either. > Now from a different remote machine using my substitute caching server > > ./pre-inst-env guix package -i hello > --substitute-urls="http://guix.myserver.org"; --dry-run > > keeps on wanting to build the thing from scratch. Did you authorize the singing key of that server? > Query from main server: > > GET /nix-cache-info > GET /xgm6wxkja6llvkz8jck95i6cmh3c93yh.narinfo > GET /w6im8ck36hpjyh9zjmz9mr2vkppfhzid.narinfo > GET /9wq9z5jq3g691f836lhi0633g26lfl8n.narinfo > > Query from remote > > GET /nix-cache-info > GET /x2lhjhbxd5dqmis350gkc352v9z1pr8r.narinfo > GET /jkxa2ga4x0gqvx6x790anpwhnm7d278w.narinfo > GET /ic8sabq35jisj5wmi860d85i09qghq1x.narinfo > > which suggests the files it wants to fetch are not the same, though the > starting point > (the checked out guix dir) should be exactly the same. The last commit is the > same. The set of narinfos queried is a function of what’s in the local /gnu/store (clients only ask about things not already on disk) so it’s normal that the requests differ. HTH! Ludo’.
